IBM Support

PI59687: SOME JMSEXCEPTIONS RELATED TO QUEUE MANAGER CONNECTION ERRORS ARE MISIDENTIFIED AND CONNECTION CLEANUP DOES NOT OCCUR

Fixes are available

8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A JMSException occured while using a JMS Managed Connection
    caused by an exception on a JTA-XA protocol flow xa_start:
    
    Caused by: javax.transaction.xa.XAException: The method
    'xa_start' has   failed with errorCode '-7'
    
    This condition should have been treated as a connection error
    and invoked connection cleanup but this did not occur.
    Subsequent use of managed connections from the same pool failed
    continuously with no attempt to establish new connections.
    

Local fix

  • Add custom property
    Resources -> JMS -> (Queue/Topic) Connection factories ->
    <connection factory> -> Custom properties
    Select New and create a property:
    Name = check.is.connection.broken
    Value = false
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of       *
    *                  WebSphere MQ JMS                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Some JMSExceptions related to Queue     *
    *                      Manager connection errors are           *
    *                      misidentified and connection cleanup    *
    *                      does not occur.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    APAR PM76316 modified the handling of JMSExceptions so that
    only those exceptions with specific causes were treated as
    indicating connection failures.  The list of causes was
    deficient and omitted javax.transaction.xa.XAException
    with the following errorCodes:
    XAException.XAER_RMERR, XAException.XAER_RMFAIL,
    XAException.XAER_PROTO and XAException.XAER_INVAL.
    When such an exception occurs, it must be assumed that the
    condition indicates that the connection is no longer usable and
    connection cleanup must be performed.
    If the correct connection cleanup is not performed then, since
    the connection is managed, closing the managed connection does
    not close the underlying connection but returns the managed
    connection to the pool from where it is available for re-use.
    Hence, when a JMSException is not correctly identified as a
    failure of the underlying connection, the broken connection
    remains in the underlying pool of managed connections and
    subsequent re-use of the connection will fail.
    

Problem conclusion

  • The messaging component was modified so that a JMSException
    caused by a javax.transaction.xa.XAException with errorCodes
    XAException.XAER_RMERR, XAException.XAER_RMFAIL,
    XAException.XAER_PROTO or XAException.XAER_INVAL is handled as
    a connection failure.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.10 and 9.0.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

  • Custom property check.is.connection.broken can be specified
    on the Connection Factory and set to a value of false
    
    In versions 8.5.5 and later of WebSphere Application Server,
    if this custom property is not specified then the effective
    value is true.  Specifying a value of false will revert the
    handling of JMSExceptions to that before APAR PM76316.
    

Comments

APAR Information

  • APAR number

    PI59687

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-24

  • Closed date

    2016-07-11

  • Last modified date

    2016-07-12

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP

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

Document Information

Modified date:
02 December 2021