PM81521: MESSAGES STUCK IN PENDING ACKNOWLEDGEMENT STATE IN WEBSPHERE APPLICATION SERVER SERVICE INTEGRATIONS BUS DESTINATION

Fixes are available

APAR status

Closed as program error.

Error description

In WebSphere Application Server v7.0.x Service Integration
Bus, multiple messaging engines are configured to use a
Publish Subscribe topology. When more than one messaging
engine is shut down and started up in parallel and messages
are published at the same time, the messages remain in
pending acknowledgement state.

Local fix

Restart the messaging engines sequentially.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for                                         *
*                  IBM WebSphere Application Server v7.0,      *
*                  v8.0, and v8.5.5                            *
****************************************************************
* PROBLEM DESCRIPTION: Message pile up is observed on the      *
*                      Source Messaging Engine awaiting for    *
*                      the messages to be acknowledged from    *
*                      the Target Messaging Engine.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using Publish Subscribe in Service Integration Bus in a
multi Messaging Engine scenario, message pile up is observed on
the Source Messaging Engine awaiting for the messages to be
acknowledged from the Target Messaging Engine. There are
various reasons why the target messaging engine is not
acknowledging the messages.Some of the scenarios are gaps
created due to a very minute timing window between message
production and target messaging engine start-up (or) messages
being received out of order and having a lot of silences in
between (or) lack of consolidation between the streams leading
to virtual gaps.

Problem conclusion

Code has been modified to effectively synchronize the timing
window between message production and target messaging engine
start-up registration and also to consolidate effectively to
overcome the problems due to out of order delivery and silence
messages and to fill the virtual gaps.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.31,8.0.0.8 and 8.5.5.1 . Please note that This
APAR supercedes PM62615,PM71430. If applying an interim fix
for PM81521, the install sequence should be PM56596
followed by PM81521. You need not install interim fixes for
PM62615 and PM71430 .

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
PM81521
Reported component name
WAS SIB & SIBWS
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-28
Closed date
2013-06-24
Last modified date
2013-10-04

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
WAS SIB & SIBWS
Fixed component ID
620800101

Applicable component levels

R300 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:
12 January 2022

Tips

PM81521: MESSAGES STUCK IN PENDING ACKNOWLEDGEMENT STATE IN WEBSPHERE APPLICATION SERVER SERVICE INTEGRATIONS 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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?