PK91746: MESSAGES NOT CONSUMED AFTER A SERVER IS TERMINATED AND RESTARTED, WHEN CONSUMING MESSAGES FROM A BUS DESTINATION

Fixes are available

APAR status

Closed as program error.

Error description

When an MDB is consuming messages from a queue point (or durable
subscription) hosted on a different messaging engine to the one
the application is connected to, and the server hosting the ME
is terminated and restarted, messages delivery might not resume
after the server restarts.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server Version 7.0*
****************************************************************
* PROBLEM DESCRIPTION: Consumption of messages might not       *
*                      resume after restarts of application    *
*                      servers in a bus containing             *
*                      multiple messaging engines              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This issue only affects an application that connects to a
messaging engine that does not own the queue (or durable
subscription) that it is consuming from.
The indirect consumption of messages from the messaging engine
that owns the queue/subscription is handled through
an asynchronous communication protocol between the two
messaging engines.
If restarts occur of the application server that host the
messaging engine the application connects to, and/or the
application server that hosts the messaging engine that owns
the queue/subscription, it is possible for the asynchronous
communication protocol to enter a state where no messages are
delivered to the consumer after the restart.

If this issue is encountered, the "Known remote queue point"
on the messaging engine that owns the queue, or "Known remote
publication point" for durable subscriptions, will show a
number of active message requests in progress.
The "Remote queue point", or "Remote publication point", of
the messaging engine the application is connected to will
show no active message requests.
Message consumption only restarts if the active message
requests are canceled manually.

Problem conclusion

The fix for this APAR allows the asynchronous communications
protocol between messaging engines to automatically resolve the
state, without needing to manually cancel the message requests.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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
PK91746
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-20
Closed date
2009-07-31
Last modified date
2009-07-31

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
620800101

Applicable component levels

R300 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
24 October 2021

Tips

PK91746: MESSAGES NOT CONSUMED AFTER A SERVER IS TERMINATED AND RESTARTED, WHEN CONSUMING MESSAGES FROM A BUS DESTINATION

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

R300 PSY

Document Information

Share your feedback

Need support?