PK58076: POSSIBLE DEADLOCK OF MESSAGING ENGINE THREADS WHEN CLIENT CONNECTIONS FAIL AND FFDCS ARE PRODUCED

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• A deadlock occured when two FFDCs were being produced at the
  same time, due to client applications connected to a messaging
  engine losing their connection.
  

Local fix

• Restart the application server
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the default messaging provider for  *
  *                 WebSphere Application Server V6.0 and V6.1   *
  ****************************************************************
  * PROBLEM DESCRIPTION: A deadlock can occur when two FFDCs     *
  *                      are being created at the same time,     *
  *                      due to multiple network connections     *
  *                      to a service integration bus ending     *
  *                      unexpectedly.                           *
  *                                                              *
  *                      The deadlock occurs in:                 *
  *                      com.ibm.ws.sib.jfapchannel              *
  *                                         .impl.Connection     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  ****************************************************************
  
  Two threads within the messaging engine began the
  process of collecting diagnostics for an FFDC, due
  to network connections failing.
  A deadlock occurred due to incorrect locking of
  internal data structures.
  

Problem conclusion

• This APAR resolves the issue.
  

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

  PLAT MSG COM

• Fixed component ID

  620600101

Applicable component levels

• R200 PSY

     UP