PK77970: MESSAGING ENGINE STARTUP FAILS IF USER MANUALLY STARTS A MESSAGING ENGINE WHEN IT IS ALREADY STARTING

Fixes are available

APAR status

Closed as program error.

Error description

If a user attempts to manually start a messaging engine
that is already starting, the messaging engine fails to start.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for WebSphere Application Server Version    *
*                  6.1 and Version 7.0.                        *
****************************************************************
* PROBLEM DESCRIPTION: If a user attempts to start a           *
*                      messaging from the administrative       *
*                      console when that messaging engine is   *
*                      already starting, the following         *
*                      exception is seen:                      *
*                                                              *
*                      CWSID0034E: Messaging engine            *
*                      <name> cannot be started:               *
*                         caught exception thrown by           *
*                      com.ibm.ws.sib.msgstore.impl.           *
*                      MessageStoreImpl start()                *
*                      IllegalStateException in                *
*                      com.ibm.ws.sib.msgstore.impl.           *
*                      MessageStoreImpl.start                  *
*                                                              *
*                      An FFDC report is issued for the        *
*                      exception and the messaging engine      *
*                      fails to start.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Start commands for a messaging engine can come from the
high availability manager and from the user. In this case
the high availability manager had issued a start command, and
the user had also tried to start the same messaging engine via
the administrative console.
A component within the messaging engine that had already
begun startup (the message store) threw an
IllegalStateException, causing startup to fail.

Problem conclusion

The fix for this APAR adds checks to the start methods which
can be called by a user to ensure that the messaging engine is
not already starting. Checks are also added to prevent a user
from stopping a messaging engine that is already stopping.

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

Temporary fix

Restart the server hosting the messaging engine.
Alternatively, review the "Managing high availability when
messaging engines fail to start" section of the information
center for instructions to re-enable the server as a high
availability location for the messaging engine, and cause the
high availability manager to restart the messaging engine.

Comments

APAR Information

APAR number
PK77970
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-12-30
Closed date
2009-03-31
Last modified date
2009-03-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
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:
29 December 2021

Tips

PK77970: MESSAGING ENGINE STARTUP FAILS IF USER MANUALLY STARTS A MESSAGING ENGINE WHEN IT IS ALREADY STARTING

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?