IBM Support

PM31933: DEADLOCK IN SERVICE INTEGRATION BUS CLIENT CAUSES APPARENT HANG

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A deadlock in the Service Integration Bus client can cause the
    client threads to hang.  A javacore will show two threads
    deadlocked, at least one of them will have the following top
    stack:
    
    Thread-1:
    at com/ibm/ws/sib/jfapchannel/impl/octracker/ConnectionData
    Group.isEmpty(ConnectionDataGroup.java:736(Compiled Code))
    
    <an example of stacks above this is:>
    at com/ibm/ws/sib/jfapchannel/impl/octracker/OutboundConnection
    Tracker.closeConversation(OutboundConnectionTracker.java:
    396(Compiled Code))
    at com/ibm/ws/sib/jfapchannel/impl/OutboundConnection.close
    Notification(OutboundConnection.java:240(Compiled Code))
    at com/ibm/ws/sib/jfapchannel/impl/ConversationImpl.fastClose
    (ConversationImpl.java:418(Compiled Code))
    at com/ibm/ws/sib/comms/client/ConnectionProxy._close
    (ConnectionProxy.java:4265(Compiled Code))
    ...
    
    An example of the other thread involved in the deadlock is:
    
    Thread-2:
    at com/ibm/ws/sib/jfapchannel/impl/octracker/Connection
    DataGroup.connect(ConnectionDataGroup.java:402(Compiled
    Code))
    at com/ibm/ws/sib/jfapchannel/impl/octracker/Outbound
    ConnectionTracker.connect(OutboundConnectionTracker.
    java:482(Compiled Code))
    at com/ibm/ws/sib/jfapchannel/impl/ClientConnectionManager
    Impl.connect(ClientConnectionManagerImpl.java:159(Compiled
    Code))
    at com/ibm/ws/sib/comms/client/ClientSideConnection.connect
    (ClientSideConnection.java:197(Compiled Code))
    at com/ibm/ws/sib/trm/client/TrmSICoreConnectionFactoryImpl.
    remoteAttach(TrmSICoreConnectionFactoryImpl.java:525
    (Compiled Code))
    
    Once the deadlock is hit, no other thread can create a new
    connection to the Bus, and a restart of the JVM hosting the
    client is required.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server        *
    *                  version 7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deadlock in Service Integration Bus     *
    *                      Client causes hang.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A deviation from the locking hierarchy employed by the
    JFapChannel code used as part of the Service Integration Bus
    client caused the deadlock.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM31933

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-02-04

  • Closed date

    2011-02-22

  • Last modified date

    2011-02-22

  • 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

    620800101

Applicable component levels

  • R300 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021