IBM Support

PK84457: BBOO0160E FUNCTION SEND() FAILED WITH RV=3140, RC=0, RSN=00000000, [EDC5000I NO ERROR OCCURRED. (ERRNO2=0X05230138)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When running WebSphere Application Server, an RMI/IIOP call from
    a WebSphere Application Server client server to the target
    server might result in an error like below.
    
    Trace: 2009/03/24 14:21:18.369 01 t=BBCB70 c=UNK key=S2 (0300A00
       Description: Detailed Session Information
       Description: Send Message
       Session Type: REMOTE_SESSION
       sent to: hostname=aaa.bbb.ccc port=xxxxx
       Buffer:  data_address=44c39cc0, data_length=3050
    ....
    Trace: 2009/03/24 14:28:31.651 01 t=BBCB70 c=UNK key=S2 (030050A
       Description:  ClientIPSession::send_msg entered
    .....
     Trace: 2009/03/24 14:28:31.653 01 t=BBCB70 c=UNK key=S2 (000000
       Description: Log Boss/390 Error
       from filename: ./bbocsess.cpp
       at line: 5953
       error message: BBOO0160E Function send() failed with RV=3140,
    RC=0, RSN=00000000, [EDC5000I No error occurred.
    (errno2=0x05230138) ]hostname/ip: aaa.bbb.ccc
    .....
     Trace: 2009/03/24 14:28:31.665 01 t=BBCB70 c=11.25D key=S2 (000
       Description: Log Boss/390 Error
       from filename: ./bboocomm.cpp
       at line: 5749
       error message: BBOO0044E Internal communications error:
       REASON=C9C20C5E.
    ...
     Trace: 2009/03/24 14:28:31.675 01 t=BBCB70 c=11.25D key=S2 (030
       Description: uninitializeClientIPSession entered.
     Trace: 2009/03/24 14:28:31.675 01 t=BBCB70 c=11.25D key=S2 (030
       Description:
     Client Session Uninitialization
       session_token: 0
       session_type: REMOTE SESSION
       connected to: hostname=aaa.bbb.ccc port=xxxxx
    
    Note: The problem symptom is highly intermittent.
    
    2010/03/15: additional symptoms have been reported.
    If a 6.0.2 server exhibiting the symptoms in this APAR send
    IIOP requests to another WebSphere server running 6.1, the 6.1
    controller region could terminate with the following message:
    BBOO0035W TERMINATING THE CURRENT PROCESS, REASON=C9C21A4D,
    followed seconds later with SDC3 REASON=000C0006.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.0.1 for z/OS                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Controller address space suffers        *
    *                      BBOO0160E, BBOO0044E and C9C20C5E       *
    *                      errors.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WebSphere Application Server for z/OS controller address
    space suffers the following errors while attempting to send a
    GIOP message over TCP/IP to another server:
    
    BBOO0160E Function send() failed with RV=3140, RC=0,
    RSN=00000000, [EDC5000I No error occurred. (errno2=0x05230138)]
    
    BBOO0044E Internal communications error: REASON=C9C20C5E
    
    The send() fails with a non-zero return value (RV) that
    matches the message length of a GIOP message sent by another
    thread that is also sending GIOP messages to the same target
    server as the failing thread.  The failure occurs because a
    timing window exists where one thread could send() its own
    GIOP message but receive the return value from the send() of
    the other thread's GIOP message.  The other thread's return
    value is not expected by the first thread; therefore the first
    thread fails its request.
    

Problem conclusion

  • The timing window was closed such that two threads can no
    longer interfere with each other's send() return values.
    
    APAR PK84457 is currently targeted for inclusion in
    Service Level (Fix Pack) 6.0.2.37 of WebSphere
    Application Server V6.0 for z/OS.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK84457

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    601

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-09

  • Closed date

    2009-05-18

  • Last modified date

    2010-03-15

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R601 PSY UK49499

       UP09/08/29 P F908

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022