IBM Support

PM23655: IBM WEBSPHERE SERVICE INTEGRATION BUS MESSAGING ENGINE FAILS TO START AFTER A NETWORK CONNECTION IS LOST AND RE-ESTABLISHED

Fixes are available

7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
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

  • When a database is taken down for maintenance while an
    IBM WebSphere Application Server Service Integration Bus
    messaging engine is running, the messaging engine loses its
    lock on the datastore. When the connection to the database is
    re-established , the messaging engine still fails to acquire
    lock on the datastore and the following messages are logged
    repeatedly in the SystemOut.log:
    
    CWSIS1546I: The messaging engine, ME_UUID={0}, INC_UUID={1},
    has lost an existing lock or failed to gain an initial lock
    on the data store
    
    CWSIS1538I: The messaging engine, ME_UUID={0}, INC_UUID={1},
    is attempting to obtain an exclusive lock on the data store.
    

Local fix

  • Restart the server hosting the messaging engine
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server            *
    ****************************************************************
    * PROBLEM DESCRIPTION: The lock on the messaging engine        *
    *                      database table is not reacquired even   *
    *                      when the lock held by the previous      *
    *                      instance of the messaging engine has    *
    *                      been removed.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The messaging engine is not able to acquire a lock on the data
    store, and the following messages are output:
    
    CWSIS1546I: The messaging engine, ME_UUID={0}, INC_UUID={1},
    has lost an existing lock or failed to gain an initial lock
    on the data store
    
    CWSIS1538I: The messaging engine, ME_UUID={0}, INC_UUID={1},
    is attempting to obtain an exclusive lock on the data store.
    
    If these messages occur when there is a lock held on the
    SIBOWNER table of the data store then this is expected, and the
    database will normally remove the lock after a period of time.
    
    If these messages still occur even when the lock no longer
    exists, then it is likely that the thread attempting to do the
    locking is not running. This can be verified by taking a
    javacore of the messaging engine process that is showing the
    CWSIS1546I message and looking for a thread named:
    sib.LockThread-<ME_UUID>  where <ME_UUID> is the uuid of the
    messaging engine with the problem.
    
    The thread stopped running due to a timing window where the
    connection to the database was re-established so we could
    create a connection but was then lost again before we could
    attempt to get a lock.
    

Problem conclusion

  • This APAR makes sure that the locking thread is always running
    when attempting to acquire the lock on the data store.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.15.  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 messaging engine process.
    

Comments

APAR Information

  • APAR number

    PM23655

  • 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

    2010-10-01

  • Closed date

    2010-11-26

  • Last modified date

    2010-11-26

  • 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



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 6.1

Reference #: PM23655

Modified date: 26 November 2010