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

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

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

Document Information

Modified date:
29 October 2021

Tips

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

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?