IBM Support

PM79328: SECOND DEFINED ACTIVATION SPECIFICATION WILL PAUSE WHEN THE FIRST ACTIVATION SPECIFICATION SENDS A POISON MESSAGE

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
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.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.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

  • An application has two activation specifications (ActSpec1 and
    ActSpec2) defined for load balancing.  ActSpec1 uses QMgr1 and
    ActSpec2 uses QMgr2.
    
    If ActSpec1 sends a poison message to the backout queue,
    ActSpec2 will pause.  A message similar to the following may be
    written to the SystemOut.log file...
    
    [11/20/12 16:15:17:433 EST] 00000060 SibMessage   W  [:]
    CWWMQ0007W:  The message endpoint
    ibmTest#ibmTest.jar#TestListenerMDB has been paused by the
    system.  Message delivery failed to the endpoint more than 0
    times.  The last attempted delivery failed with the following
    error: javax.resource.ResourceException: afterDelivery failure
    at
    com.ibm.ejs.container.MessageEndpointHandler.afterDelivery(Messa
    geEndpointHandler.java:1454)
    at
    com.ibm.ejs.container.MessageEndpointHandler.invokeMessageEndpoi
    ntMethod(MessageEndpointHandler.java:806)
    at
    com.ibm.ejs.container.MessageEndpointHandler.invoke(MessageEndpo
    intHandler.java:767)
    at $Proxy29.afterDelivery(Unknown Source)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  This issue affects users of WebSphere MQ    *
    *                  Activation Specifications with multiple     *
    *                  message-driven beans in the same            *
    *                  application.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect message-driven bean stopped.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a message-driven bean endpoint needs to be stopped due to
    errors, the logic used to identify the messaging endpoint from
    the message-driven bean name may select the wrong endpoint.
    This occurs if there are multiple message-driven beans within
    the same application  whose names differ only by suffix
    characters.
    This causes the wrong message-driven bean endpoint to be
    stopped.
    

Problem conclusion

  • The logic used to select the message-driven bean endpoint has
    been updated to ensure it selects the correct endpoint.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.29, 8.0.0.6 and 8.5.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

    PM79328

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-17

  • Closed date

    2012-12-28

  • Last modified date

    2012-12-28

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM79328

Modified date: 28 December 2012