PM67225: SERVICE INTEGRATION BUS MESSAGING ENGINE FAILS TO START WITH CWSOM1011E

Fixes are available

APAR status

Closed as program error.

Error description

WebSphere Application Server Service Integration Bus messaging
engine fails to start due to InvalidStateException.

The following errors are written to the SystemOut.log:

CWSIS1591E: The file store has caught an unexpected exception
during initialisation.
CWSIS0002E: The messaging engine encountered an exception
while starting. Exception: com.ibm.ws.sib.msgstore.Severe
PersistenceException: Unexpected exception caught initializing
file store: CWSOM1011E: An invalid operation was attempted on
Object=InternalTransaction(<XX.X>)/PreparedInactive/<hex_code>
while it was in state=7(int) PreparedInactive(String).

FFDC produced prior to the above error shows:

FFDC Exception:com.ibm.ws.objectManager.InvalidStateException
SourceId:com.ibm.ws.objectManager.InternalTransaction:
optimisticReplace
ProbeId:1:1365:1.36 Reporter:com.ibm.ws.objectManager.
InternalTransaction@<hex_code>
com.ibm.ws.objectManager.InvalidStateException: CWSOM1011E:
An invalid operation was attempted on Object=Internal
Transaction(<XX.X>)/PreparedInactive/<hex_code> while it was in
state=7(int) PreparedInactive(String).
at com.ibm.ws.objectManager.InternalTransaction.testState
(InternalTransaction.java:2626)
at com.ibm.ws.objectManager.InternalTransaction.optimistic
Replace(InternalTransaction.java:1333)
at com.ibm.ws.objectManager.Transaction.optimisticReplace
(Transaction.java:378)
at com.ibm.ws.objectManager.TransactionOptimisticReplaceLog
Record.performRecovery(TransactionOptimisticReplaceLog
Record.java:417)
at com.ibm.ws.objectManager.ObjectManagerState.perform
Recovery(ObjectManagerState.java:728)
at com.ibm.ws.objectManager.ObjectManagerState.performWarm
Start(ObjectManagerState.java:593)
at com.ibm.ws.objectManager.ObjectManagerState.<init>(Object
ManagerState.java:472)
at com.ibm.ws.objectManager.ObjectManager.createObjectManager
State(ObjectManager.java:293)
at com.ibm.ws.objectManager.ObjectManager.initialise(Object
Manager.java:237)
at com.ibm.ws.objectManager.ObjectManager.<init>(Object
Manager.java:197)
at com.ibm.ws.sib.msgstore.persistence.objectManager.
PersistentMessageStoreImpl.start(PersistentMessageStore
Impl.java:352)
at com.ibm.ws.sib.msgstore.impl.MessageStoreImpl.start
(MessageStoreImpl.java:1518)
at com.ibm.ws.sib.admin.impl.JsMessagingEngineImpl.start
(JsMessagingEngineImpl.java:609)
at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.
activate(HAManagerMessagingEngineImpl.java:995)
at com.ibm.ws.sib.admin.impl.JsActivationThread.run
(JsActivationThread.java:92)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for                                         *
*                  IBM WebSphere Application Server            *
****************************************************************
* PROBLEM DESCRIPTION: Messaging engine fails to start         *
*                      because of CWSOM1011E.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During recovery after a failure to stop the messaging engine
cleanly, a particular state of transactions in the
filestore log which were prepared could cause a state check to
fail, resulting in CWSOM1011E.  In this case the state was
actually valid and the problem is a programming error in the
state checking logic.

Problem conclusion

This APAR resolves the problem by correcting the state
checking logic.  Once an iFix or fix pack containing this APAR
is applied the messaging engine will be able to start.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.25, 8.0.0.5 and 8.5.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
PM67225
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
2012-06-20
Closed date
2012-07-31
Last modified date
2012-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
WAS SIB & SIBWS
Fixed component ID
620800101

Applicable component levels

R300 PSY
UP
R800 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:
29 October 2021

Tips

PM67225: SERVICE INTEGRATION BUS MESSAGING ENGINE FAILS TO START WITH CWSOM1011E

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

Document Information

Share your feedback

Need support?