IBM Support

PM66933: IN NON-ASF MODE, ANY EXCEPTION RECEIVED BY THE LISTENER PORT CAUSES IT TO STOP AND ROLLBACK ANY OTHER IN FLIGHT TRANSACTIONS

Fixes are available

7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
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.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.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.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

  • Using Listener Ports in non-ASF mode, any exception when the
    listener port is consuming a message to drive an MDB causes
    the listener port to stop and other in flight MDB transactions
    to be rolled back.  The exception is not one that indicates
    that the connection is broken and so does not require that
    transactions are rolled back and stopping of the listener port.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Any exception in non-ASF mode causes    *
    *                      the listener port to stop and rolls     *
    *                      back any in flight transactions.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an exception occurs, there is no checking to determine
    whether the exception means the connection is broken.  Instead
    the managed connection is always invalidated.  This causes
    other threads using the same JMS Connection (other Listener
    Port threads) to get an error and rollback.
    In addition, the exception causes the listener port to stop.
    

Problem conclusion

  • This APAR introduces a new custom property:
    
    NON.ASF.CHECK.CONNECTION.BROKEN
    
    This property can be set to 'true' or 'false'.  The default is
    'false' which leaves the behaviour unchanged.
    
    When set to 'true', this causes two things to happen:
    
    1) When an exception occurs while the listener port is getting
    a message to drive an MDB, the excption reason code is first
    checked to determine whether it indicates the connection is
    broken.  This only works in WMQ is the messaging provider.  If
    the connection is not broken, the managed connection is not
    invalidated.  Reason codes that indicate that a connection is
    broken are:
    
    MQRC_CONNECTION_BROKEN, MQRC_UNEXPECTED_ERROR,
    MQRC_Q_MGR_NOT_AVAILABLE, MQRC_CONNECTION_ERROR,
    MQRC_Q_MGR_QUIESCING, MQRC_Q_MGR_STOPPING,
    MQRC_CHANNEL_STOPPED_BY_USER, MQRC_CONNECTION_STOPPING,
    MQRC_CONNECTION_QUIESCING, MQRC_Q_MGR_NOT_ACTIVE,
    MQRC_CF_STRUC_FAILED
    
    2) When an exception is thrown to the listener port, it is
    first checked to see if the exception indicates the connection
    is broken.  If the connection is not broken, the listner port
    does not stop.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.25, 8.0.0.5 and 8.5.0.1.  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

    PM66933

  • 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-06-15

  • Closed date

    2012-07-26

  • Last modified date

    2012-07-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

    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 #: PM66933

Modified date: 26 July 2012