IBM Support

PM36297: WEBSPHERE APPLICATION SERVER JVM MAY BE UNRESPONSIVE OR HANG DURING THE ROLLBACK OF MESSAGES FROM MDB TO MQ

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
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
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
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

  • When a message-driven bean (MDB) running in WebSphere
    Application Server gets messages from WebSphere MQ using an
    activation specification configured in the application server, a
    problem may occur during the processing of messages rolling back
    to the queue due to an error condition.  Some of the messages
    may not roll back to the queue until the application server JVM
    is manually killed.  The application server may be unresponsive
    to requests and unable to stop gracefully when this occurs.
    .
    The problem happens because the application server is attempting
    to pause a MQ messaging endpoint which is already being paused.
    This causes a deadlock, as the thread currently pausing is
    waiting for the thread which is waiting to pause to complete.
    .
    A Javacore shows the two threads with the following Java
    callstacks:
    .
    Callstack of first "WMQJCAResourceAdapter : " thread:
    .
     at java/lang/Object.wait(Native Method)
     at java/lang/Object.wait(Object.java:167)
     at
    com/ibm/mq/connector/inbound/ServerSessionImpl.close(ServerSessi
    onImpl.java:268)
     at
    com/ibm/mq/connector/inbound/ServerSessionPoolImpl.close(ServerS
    essionPoolImpl.java:465)
     at
    com/ibm/mq/connector/inbound/MessageEndpointDeployment.stop(Mess
    ageEndpointDeployment.java:429)
     at
    com/ibm/mq/connector/ResourceAdapterImpl.endpointDeactivation(Re
    sourceAdapterImpl.java:520)
     at
    com/ibm/ejs/j2c/ActivationSpecWrapperImpl.deactivateUnderRAClass
    LoaderContext(ActivationSpecWrapperImpl.java:494)
     at
    com/ibm/ejs/j2c/ActivationSpecWrapperImpl.deactivateEndPoint(Act
    ivationSpecWrapperImpl.java:410)
     at
    com/ibm/ejs/j2c/mbeans/MessageEndpointMBeanImpl.pause(MessageEnd
    pointMBeanImpl.java:162)
    ...
    Callstack of second "WMQJCAResourceAdapter : " thread:
    .
     at sun/reflect/NativeMethodAccessorImpl.invoke0(Native Method)
     at
    sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:48(Compiled Code))
     at
    sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:25(Compiled Code))
     at java/lang/reflect/Method.invoke(Method.java:578(Compiled
    Code))
     at sun/reflect/misc/Trampoline.invoke(MethodUtil.java:37)
     at sun/reflect/GeneratedMethodAccessor116.invoke(Bytecode
    PC:40)
     at
    sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:25(Compiled Code))
     at java/lang/reflect/Method.invoke(Method.java:578(Compiled
    Code))
     at sun/reflect/misc/MethodUtil.invoke(MethodUtil.java:244)
     at
    javax/management/modelmbean/RequiredModelMBean.invokeMethod(Requ
    iredModelMBean.java:1086)
     at
    javax/management/modelmbean/RequiredModelMBean.invoke(RequiredMo
    delMBean.java:967)
     at
    com/sun/jmx/interceptor/DefaultMBeanServerInterceptor.invoke(Def
    aultMBeanServerInterceptor.java:836)
     at
    com/sun/jmx/mbeanserver/JmxMBeanServer.invoke(JmxMBeanServer.jav
    a:761)
     at
    com/ibm/ws/management/AdminServiceImpl$1.run(AdminServiceImpl.ja
    va:1332)
     at
    com/ibm/ws/security/util/AccessController.doPrivileged(AccessCon
    troller.java:118(Compiled Code))
     at
    com/ibm/ws/management/AdminServiceImpl.invoke(AdminServiceImpl.j
    ava:1225)
     at
    com/ibm/ws/wmqra/utils/EndpointPauser$1.run(EndpointPauser.java:
    99)
     at
    com/ibm/ws/sib/security/auth/AuthUtilsImpl$5.run(AuthUtilsImpl.j
    ava:1454)
     at
    com/ibm/ws/security/auth/ContextManagerImpl.runAs(ContextManager
    Impl.java:4610)
     at
    com/ibm/ws/security/auth/ContextManagerImpl.runAsSystem(ContextM
    anagerImpl.java:4698)
     at
    com/ibm/ws/sib/security/auth/AuthUtilsImpl.runAsSystem(AuthUtils
    Impl.java:1449)
     at
    com/ibm/ws/wmqra/utils/EndpointPauser.pauseJ2CMessageEndpoint(En
    dpointPauser.java:96)
     at
    com/ibm/ws/wmqra/helper/WASRuntimeHelper.deliveryFailed(WASRunti
    meHelper.java:299)
     at
    com/ibm/mq/connector/inbound/WorkImpl.callDeliveryFailed(WorkImp
    l.java:412)
     at
    com/ibm/mq/connector/inbound/WorkImpl.xaStateChanged(WorkImpl.ja
    va:369)
     at
    com/ibm/mq/connector/xa/XAObservable.update(XAObservable.java:12
    0)
    ...
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using the activation specifications  *
    *                  with MQ                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deadlock whilst attempting to pause     *
    *                      MQ endpoint                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Due to a change in the logic executed when an MQ endpoint is
    paused, the application server may deadlock as it keeps hold
    of an MQ thread which MQ is waiting to end during the pause of
    the messaging endpoint.
    

Problem conclusion

  • The code has been altered to ensure that the application
    server will not keep hold of MQ threads, thereby allowing them
    to complete as normal.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.19.  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

    PM36297

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-04-05

  • Closed date

    2011-05-31

  • Last modified date

    2011-05-31

  • 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 APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM36297

Modified date: 31 May 2011