IBM Support

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

Fixes are available

7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

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



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM67225

Modified date: 31 July 2012