IBM Support

PI04730: MESSAGING ENGINE FAILOVER HAS BEEN INITIATED A FEW SECONDS BEFORE THE CONFIGURED DB LOCK WAIT TIME OUT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere Application Server V8.5, or later, experiences a
    failover which may occur 15 seconds prior to the configured
    time.
    
    Some of the errors which might be encountered are:
    
    CWSIP0002E: An internal messaging error occurred in
    com.ibm.ws.sib.processor.impl.ConsumerDispatcher,
    1:776:1.280.5.25,
    com.ibm.ws.sib.msgstore.MessageStoreUnavailableException:
    Operation not possible as MessageStore is unavailable!
    
    FFDC
    
    Exception:com.ibm.ws.sib.msgstore.PersistenceException
    SourceId:com.ibm.ws.sib.msgstore.transactions.MSDelegatingLocalT
    ransacti
    on.commit ProbeId:1:425:1.51.1.14
    Reporter:com.ibm.ws.sib.msgstore.transactions.MSDelegatingLocalT
    ransactionSynchronization@cc13b114
    com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1577E: The
    persistent dispatcher cannot accept work.
    

Local fix

  • ncrease the (ME retry interval * Retry count)  to a higher
    value. This will ensure that there will be more wait time before
    triggering ME failover. This requires a server restart.
    
    For example, to set the retry count as "9", set one of the
    following:
    
    Add the following as ME custom property
    sib.msgstore.jdbcDataStoreDBLockRetryCount = 9
    
    (or)
    
    Add the below entry in sib.properties file
    sib.msgstore.jdbcDataStoreDBLockRetryCount = 9
    
    (or)
    
    Set "sib.msgstore.jdbcDataStoreDBLockRetryCount = 9" as a JVM
    system property.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server 8.5    *
    *                  and above.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Messaging engine(ME) failover has been  *
    *                      initiated few seconds ahead of the      *
    *                      configured wait time.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    ME failover can be initiated from one server to another
    server if the ME cannot obtain the database(DB) lock within a
    configured period of wait time. The default configured wait
    time for initiating ME failover is 60 seconds (default
    retryInterval 20  default retryCount 3). Due to a code bug,
    it is possible that the ME failover can be initiated ahead
    (in approximately 47 seconds) instead of 60 seconds.
    Note:
    This APAR just makes sure that the ME failover is not initiated
    ahead of the configured wait time, if the ME cannot obtain the
    DB lock.
    E.g. Assume that the ME requires 55 seconds to obtain the DB
    lock. And 60 seconds is the configured wait time for obtaining
    the DB lock before initiating the ME failover.
    In the current behavior (without this APAR) the ME failover is
    initiated ahead (in 47 seconds approximately). If this APAR is
    in place, there would not be any ME fail over as the ME can
    obtain the DB lock in 55 seconds which is before the
    configured wait time (60 seconds).
    If the ME requires more than 60 seconds to obtain the DB lock,
    you cannot avoid the ME failover after 60 seconds of wait
    time. So this APAR is not applicable in this scenario and the
    underlying problem of ME taking more time to obtain the DB
    lock should be investigated seperatly.
    

Problem conclusion

  • The source code has been modified to honor the exact
    configured wait time before initiating the ME failover from
    one server to another server.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.3.  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

    PI04730

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-24

  • Closed date

    2014-02-05

  • Last modified date

    2014-02-05

  • 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

  • R850 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":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022