PH48618: OUTBOUND IIOP LOCATE REQUEST HANGS AND FAILS WITH BBOO0049E LOCAL COMM CALL BBOCLSCS() FAILED WITH RV=-1, RC=1121, RSN=00000000,

APAR status

• Closed as program error.

Error description

• An outbound IIOP locate request driven from a Servant to a
  server that is being recycled (stopping) could hang. The log
  will show the following message around that time
  
  org.omg.CORBA.COMM_FAILURE: Could not establish an IIOP Session:
  null  vmcid: 0xc9c26000  minor code: A16
  The minor code C9C26A16 means that the ORBR is already attached
  to a btcb.
  
  The log might also show:
  BBOO0049E Local comm call bboclscs() failed with RV=-1, RC=1121,
  RSN=00000000, EDC8121I Connection reset. errno2=0x769F0442
  
  This only happens during a timing window when the target server
  is restarting.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  V9.0                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
  *                      hang of outbound IIOP locate request.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An IIOP outbound locate request was driven from the Servant
  Region into the Controller Region.  The IIOP locate request
  received a locate forward response within the Controller Region.
  An existing connection was found for the forward location.  When
  the IIOP locate request was sent over this connection it
  received a
  connection reset (the target server had just terminated).
  While handling an IIOP locate forward reply the native
  ORB_Request,
  representing the IIOP request, was connected to the task-level
  control blocks.  When we attempted to drive the IIOP locate
  request
  to the forwarded location the connection reset caused an attempt
  to
  connect the same ORB_Request to the task and it received a throw
  of
  a SystemException with minor code x'C9C210C9' from routine
  startOfRequestOnTask.  The throw of this SystemException
  disrupted
  the outbound IIOP locate flow and led to a hang of this
  request.
  

Problem conclusion

• Code has been updated to allow a call to startOfRequestOnTask to
  
  not throw a SystemException if the caller is attempting to conne
  
  an ORB_Request that may already be connected to the task.
  
  
  
  
  
  The fix for this APAR is targeted for inclusion in fix pack
  
  9.0.5.14.
  
  For more information, see 'Recommended Updates for WebSphere
  
  Application Server': https://www.ibm.com/support/pages/node/7155
  

Temporary fix

Comments

APAR Information

• 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