IBM Support

PM42438: JMS CLIENT CONNECTED TO WEBSPHERE APPLICATION SERVER V7.0.X SERVICE INTEGRATION BUS MESSAGING ENGINE HANGS

Fixes are available

7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 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

  • When an application invokes a close call, due to connectivity
    problems between a JMS client and Websphere Application Server
    v7.0.x Service Integration Bus messaging engine the JMS client
    hangs. The hung thread has the following stack:
    
    at java/lang/Object.wait(Native Method)
    at java/lang/Object.wait(Object.java:167(Compiled Code))
    at com/ibm/ws/util/lock/WriterPriorityReadersWriterLock.start
    Writing(WriterPriorityReadersWriterLock.java:103(Compiled
    Code))
    at com/ibm/ws/sib/comms/client/BrowserSessionProxy.close
    (BrowserSessionProxy.java:193(Compiled Code))
    at com/ibm/ws/sib/comms/client/proxyqueue/impl/ProxyQueue
    ConversationGroupImpl.closeNotification(ProxyQueue
    ConversationGroupImpl.java:422)
    at com/ibm/ws/sib/comms/client/ConnectionProxy._close
    (ConnectionProxy.java:4178)
    at com/ibm/ws/sib/comms/client/ConnectionProxy.close
    (ConnectionProxy.java:4143)
    at com/ibm/ws/sib/api/jmsra/impl/JmsJcaConnectionImpl.
    close(JmsJcaConnectionImpl.java:558)
    at com/ibm/ws/sib/api/jms/impl/JmsConnectionImpl.close
    (JmsConnectionImpl.java:668)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server v7     *
    *                  and v8                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When an application calls JMS           *
    *                      Connection.close() to a messaging       *
    *                      engine in a different JVM, the          *
    *                      thread hangs within the close call.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If the application is attempting to close a JMS Connection
    when a Browser Session or Consumer Session associated with
    that connection is still open then the close call will hang.
    The application must be running within a seperate JVM to the
    messaging engine to experience this hang.
    Obtaining a javacore of the hang will show the following
    thread in a waiting state:
    at java/lang/Object.wait(Native Method)
    at java/lang/Object.wait(Object.java:167(Compiled Code))
    at com/ibm/ws/util/lock/WriterPriorityReadersWriterLock.start
    Writing(WriterPriorityReadersWriterLock.java:103(Compiled
    Code))
    at com/ibm/ws/sib/comms/client/BrowserSessionProxy.close
    (BrowserSessionProxy.java:193(Compiled Code))
    at com/ibm/ws/sib/comms/client/proxyqueue/impl/ProxyQueue
    ConversationGroupImpl.closeNotification(ProxyQueue
    ConversationGroupImpl.java:422)
    at com/ibm/ws/sib/comms/client/ConnectionProxy._close
    (ConnectionProxy.java:4178)
    at com/ibm/ws/sib/comms/client/ConnectionProxy.close
    (ConnectionProxy.java:4143)
    at com/ibm/ws/sib/api/jmsra/impl/JmsJcaConnectionImpl.
    close(JmsJcaConnectionImpl.java:558)
    at com/ibm/ws/sib/api/jms/impl/JmsConnectionImpl.close
    (JmsConnectionImpl.java:668)
    .....
    

Problem conclusion

  • This fix solves the problem and allows a JMS Connection.close
    call to be processed and close any child objects associated
    with the connection.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.21 and 8.0.0.2.  Please refer to the Recommended
    Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM42438

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-27

  • Closed date

    2011-08-26

  • Last modified date

    2011-08-26

  • 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

    WAS SIB & SIBWS

  • Fixed component ID

    620800101

Applicable component levels

  • R300 PSY

       UP

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM42438

Modified date: 26 August 2011