PK72567: A MESSAGING ENGINE CONTINUES TO RUN WHILE THE DATABASE PROVIDING ITS MESSAGE STORE IS UNAVAILABLE WITH UNPREDICTABLE

Fixes are available

APAR status

Closed as program error.

Error description

When the database hosting the message store for a service
integration bus messaging engine is taken down, for example for
maintenance, the messaging engine continues to run and accept
work.

Work which requires updates to the persisted data in the message
store fails. These failures can occur in a large number of areas
of the code, including when performing nonpersistent messaging
as the messaging engine may need to use the message store to
allocate a unique id to a message, or spill nonpersistent
messages out of memory.  This makes the behavior of the
messaging engine unpredictable while the database is
unavailable, and increases the risk of the messaging engine
being in an inconsistent state when the database is restored.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for WebSphere Application Server v6 and v7  *
****************************************************************
* PROBLEM DESCRIPTION: Stopping the database while             *
*                      the messaging engine is running         *
*                      can cause problems with the messaging   *
*                      engine runtime.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The APAR introduces a custom property that allows you to
change the behavior of the messaging engine when it loses its
connection to the database.

The messaging engine custom property name is:
sib.msgstore.jdbcFailoverOnDBConnectionLoss

There are two possible behaviors:
- When the property is false the messaging engine continues
  to accept work from applications. It periodically attempts
  to regain the connection to the database.
  If work continues to be submitted to the messaging engine
  while the database is unavailable, the results can be
  unpredictable.
  This is the default behavior in V6.0 and V6.1.
- When the property is true, the messaging engine
  informs the high availability manager to terminate the
  application server process when the next "is alive" check
  takes place.
  If a node agent is monitoring the server and "Automatic
  restart" is enabled, the server automatically restarts.
  The messaging engine will be started by the high
  availability manager when an appropriate application
  server is available (according to the core group policy).
  This is the default behavior in V7.0 and later.

The above behavior only occurs when connectivity to a
database is lost by a messaging engine which is running and has
established exclusive access to its data store in the
database.

It does not apply when a database is unavailable (or exclusive
access cannot be established) during the startup of a messaging
engine on an application server.
For information on the behavior of a messaging engine
during startup, please refer to the following sources:
- APAR PK59051
http://www.ibm.com/support/docview.wss?rs=180&&uid=swg1PK59051
- The "Learning about data stores" section of the WebSphere
  Application Server information center.

Problem conclusion

This APAR introduces the custom property.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.0.2.33, 6.1.0.23 and 7.0.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
PK72567
Reported component name
PLAT MSG COM
Reported component ID
620400101
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-22
Closed date
2008-10-30
Last modified date
2008-10-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
620400101

Applicable component levels

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

Document Information

Modified date:
28 December 2021

Tips

PK72567: A MESSAGING ENGINE CONTINUES TO RUN WHILE THE DATABASE PROVIDING ITS MESSAGE STORE IS UNAVAILABLE WITH UNPREDICTABLE

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

R100 PSY

Document Information

Share your feedback

Need support?