PK98846: MESSAGES ARE LEFT IN A 'LOCKED' STATE FOLLOWING A SERVICE INTEGRATION BUS MESSAGE ENGINE FAILOVER

Fixes are available

APAR status

Closed as program error.

Error description

Messages are left in locked state following a failover when
the MDB consuming them is deployed to a cluster and where the
activation specification has "Always activate MDBs in all
servers" set.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server Version 7.0*
****************************************************************
* PROBLEM DESCRIPTION: Messages might be left in locked state  *
*                      following a messaging engine failover   *
*                      if an MDB is deployed to the same       *
*                      cluster in which the messaging          *
*                      engines run, and its activation         *
*                      specification has "Always activate      *
*                      MDBs in all servers" set.               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The asynchronous code which drops connections following a
connection error did not check that the connection it intended
to drop was still the one in error. In this case the
connection which encountered the error had already been dropped
and had reconnected to the new instance of the messaging
engine, but the async code then attempted to clean up this
newly connected connection and created another.

As well as being unnecessary, the cleanup of the connection was
incomplete and left messages in locked on the queue.

Problem conclusion

The fix for this APAR resolves the problem by adding a
check to ensure that the asynchronous error handling code only
drops the connection for which the error occurred.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Restarting the messaging engine (or server hosting it) will
cause the locked messages to become unlocked and to be
available again to be consumed.

Comments

APAR Information

APAR number
PK98846
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-10-16
Closed date
2009-11-12
Last modified date
2009-11-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
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

PK98846: MESSAGES ARE LEFT IN A 'LOCKED' STATE FOLLOWING A SERVICE INTEGRATION BUS MESSAGE ENGINE FAILOVER

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?