IBM Support

PH61459: An API requester failed with message BAQH4005E and java.io.IOException: Async IO operation failed Error Return Code: 140.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • An OpenAPI 3 API requester application receives the following:
    BAQ-ZCON-COMPLETION-CODE=8
    BAQ-ZCON-REASON-CODE=4005
    BAQ-ZCON-RETURN-MESSAGE=BAQH4005E: Unable to send request to the
                            z/OS Connect server
    
    And the Host API trace (BAQVERBOSE) shows:
    t-Exit: sendrqst
    (sendRequestData) << hwthrqst{262}
    (sendRequestData) -- Communication error, possible time-out
    (sendRequestData) -- BAQH4005E: Unable to send request to the
                         z/OS Connect server
    
    The following is reported in the z/OS Connect server trace:
    com.ibm.ws.channel.ssl.internal.SSLUtils   3
    Exception caught closing down, java.io.IOException: Async IO
    operation failed (1), reason: Error Return Code: 140
    
    Additional search words:
    msgBAQH4005E BAQH4005E msgBAQH4005 BAQH4005 RC140 HWTHRQST
    106 HWTH_COMMUNICATION_ERROR CC08 RC4005
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/OS Connect OpenAPI 3 z/OS     *
    *                 application API requesters.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: An API requester failed with message    *
    *                      BAQH4005E and java.io.IOException:      *
    *                      Async IO operation failed Error Return  *
    *                      Code: 140.                              *
    ****************************************************************
    The z/OS Connect OpenAPI 3 API requester did not correctly
    manage response data larger than 32KB returned by the z/OS
    Client Web Enablement Toolkit streaming callback service. This
    caused early termination when the API requester received
    multiple transmission responses.
    

Problem conclusion

Temporary fix

Comments

  • The z/OS Connect API requester Host API callable interface has
    been changed to correctly handle response data returned in more
    than one chunk. This allows all the response data to be returned
    to z/OS application API requesters in multiple transmissions.
    
    The fix for this APAR is expected to be delivered by the PTF for
    z/OS Connect V3.0.82.0 (PH61452).
    

APAR Information

  • APAR number

    PH61459

  • Reported component name

    Z/OS CONNECT EE

  • Reported component ID

    5655CE300

  • Reported release

    000

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-05-22

  • Closed date

    2024-06-20

  • Last modified date

    2024-06-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    Z/OS CONNECT EE

  • Fixed component ID

    5655CE300

Applicable component levels

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSVVFY","label":"z\/OS Connect Enterprise Edition"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"000"}]

Document Information

Modified date:
20 June 2024