PK73713: MESSAGES SENT TO EXCEPTION DESTINATION DURING SERVER SHUTDOWN INCORRECTLY WHEN MSSAGES WERE NOT ACTUALLY DELIVERED TO CONSUMER

Fixes are available

APAR status

Closed as program error.

Error description

During server shutdown the ejbcontainer was moving the endpoint
into deactivating state. This was before the ME or MDB were told
to stop. Messages were still sent to the RA but throw an
exception because we couldn't create an endpoint. The window
between the endpoint going into deactivating state and us still
trying to deliver messages was large enough for messages to be
rolledback 5 times and so go to the exception destination.

Local fix

The fix is to handle this type of exception and not to increment
the redelivery count if the consumer never saw the message.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for WebSphere Application Server Version    *
*                  6.1 and Version 7                           *
****************************************************************
* PROBLEM DESCRIPTION: During a controlled shutdown of the     *
*                      application server that hosts the       *
*                      message-driven bean, messages can be    *
*                      placed on the exception destination     *
*                      incorrectly. The exception reason       *
*                      field in the messages indicates that    *
*                      the number of times the messages were   *
*                      delivered to the application            *
*                      has exceeded the maximum number of      *
*                      deliveries permitted.                   *
*                      However, the messages were never        *
*                      delivered to the application.           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During server shutdown the ejb container moves the endpoint
into a deactivating state. This can occur before the messaging
engine or Resource Adapter are stopped, and messages continue
to be sent to the Resource Adapter for delivery to the
application. This results in an an exception, within the
service integration bus Resource Adapter, because an endpoint
cannot be created. The handling of this exception
causes the redelivery count of the messages to be incremented
incorrectly.

The time between the endpoint going into deactivating state
and the delivery of messages stopping is sufficient to allow
the exception to occur a number of times for each message.
As a result, the maximum failed deliveries limit is reached
and messages are sent to the exception destination.

Problem conclusion

The Resource Adapter now distinguishes between an failure
that occurs before the onMessage method of the message-driven
bean has been called, and a failure that occurs afterwards.
A failure that occurs before the onMessage method is called
does not increment the redelivery count of the message.

As a result of this fix, messages are no longer reported as
having been delivered to the application when they were not.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.23 and 7.0.0.3.  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
PK73713
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-13
Closed date
2008-12-30
Last modified date
2008-12-30

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
PLAT MSG COM
Fixed component ID
620600101

Applicable component levels

R200 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK73713: MESSAGES SENT TO EXCEPTION DESTINATION DURING SERVER SHUTDOWN INCORRECTLY WHEN MSSAGES WERE NOT ACTUALLY DELIVERED TO CONSUMER

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

R200 PSY

Document Information

Share your feedback

Need support?