IBM Support

PK97000: ASYNCHRONOUSEXCEPTION WHILE PROCESSING A WEB MESSAGING REQUEST CAN CAUSE THREAD DEADLOCK

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following deadlock between theads is seen while processing
    Web messaging:
    
    ----------------------------------------------------------------
    "WebContainer : 196" (TID:0x0000000016F7D800,
    sys_thread_t:0x00002AABB82A6C28, state:CW, native
    ID:0x0000000000004648) prio=5
    at java/lang/Object.wait(Native Method)
    at java/lang/Object.wait(Object.java:199(Compiled Code))
    at com/ibm/ws/sib/comms/client/proxyqueue/queue/
          AsynchConsumerQueue.waitUntilEmpty
          (AsynchConsumerQueue.java:532(Compiled Code))
    at com/ibm/ws/sib/comms/client/proxyqueue/impl/
          AsynchConsumerProxyQueueImpl.stopping
          (AsynchConsumerProxyQueueImpl.java:544(Compiled Code))
    at com/ibm/ws/sib/comms/client/ConsumerSession
       Proxy.stop(ConsumerSessionProxy.java:1501(Compiled Code))
    at com/ibm/ws/webmsg/conduit/coreWPM/CoreWPMConduitManager.
          removeAsyncConsumer(CoreWPMConduitManager.java:1489
          (Compiled Code))
    
    ----------------------------------------------------------------
    3XMTHREADINFO      "Asynchronous Consumer : 14"
    (TID:0x00000000151C5600,
     sys_thread_t:0x0000000014D99EB8, state:B, native
    ID:0x00000000000044AE)  prio=5
    at com/ibm/ws/webmsg/conduit/coreWPM/CoreWPMConduitManager
          .close(CoreWPMConduitManager.java:906)
    at com/ibm/ws/webmsg/conduit/coreWPM/CoreWPMConduitManager
          .close(CoreWPMConduitManager.java:889)
    at com/ibm/ws/webmsg/client/bayeux/cfw/protocol/vone/
          CFWClientImpl.shutdown(CFWClientImpl.java:443)
    at com/ibm/ws/webmsg/client/bayeux/cfw/protocol/vone/
          CFWClientImpl.conduitFailed(CFWClientImpl.java:906)
    at com/ibm/ws/webmsg/conduit/coreWPM/CoreWPMConduitManager
         .asynchronousException(CoreWPMConduitManager.java:1661)
    at com/ibm/ws/sib/comms/client/proxyqueue/impl/
         AsynchConsumerProxyQueueImpl.processExceptions
         (AsynchConsumerProxyQueueImpl.java:406)
    at com/ibm/ws/sib/comms/client/proxyqueue/impl/
          AsynchConsumerProxyQueueImpl.deliverException
          (AsynchConsumerProxyQueueImpl.java:362)
    at com/ibm/ws/sib/comms/client/ConsumerSessionProxy.
          deliverAsyncException(ConsumerSessionProxy.java:2331)
    at com/ibm/ws/sib/comms/client/proxyqueue/queue/
          AsynchConsumerQueue.deliverBatch
          (AsynchConsumerQueue.java:462)
    at com/ibm/ws/sib/comms/client/proxyqueue/impl/
          AsynchConsumerProxyQueueImpl.deliverMessage
          (AsynchConsumerProxyQueue Impl.java:747)
    ----------------------------------------------------------------
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using the feature pack for Web 2.0   *
    *                  Web messaging service function configured   *
    *                  with a remote messaging engine under load.  *
    ****************************************************************
    * PROBLEM DESCRIPTION: A service integration bus (SIB)         *
    *                      Exception can cause deadlock when       *
    *                      running Web messaging service function. *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Web container thead deadlock can occur when the Feature Pack
    for Web 2.0 Web messaging service function is configured to
    use remote Messaging Engine (ME).  This deadlock can occur
    under load when an exception occurs in the Messaging code .
    

Problem conclusion

  • The Web messaging service code has been changed to fix the
    deadlock problem.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.31 and 7.0.0.11.  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

    PK97000

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61I

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-09-23

  • Closed date

    2009-12-10

  • Last modified date

    2009-12-10

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP

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

Document Information

Modified date:
10 February 2022