IBM Support

PM92447: THE JVM FOR WEBSPHERE APPLICATION SERVER IS NOT TERMINATED WHEN THE CONNECTION TO THE DATABASE IS LOST.

Fixes are available

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.45: Java SDK 1.6 SR16 FP60 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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The property "sib.msgstore.jdbcFailoverOnDBConnectionLoss" is
    enabled by default which implies that the server must be
    terminated when the connection to the database is lost, but it
    is not honored.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 and v7.0.0.31                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: In a WebSphere Application Server       *
    *                      Service Integration Bus, when the       *
    *                      custom property                         *
    *                      "sib.msgstore.jdbcFailoverOnDBConnectio *
    *                      nLoss" is enabled, the jvm is not       *
    *                      terminated when the messaging engine    *
    *                      running in the server loses its         *
    *                      connection to the database.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In a WebSphere Application Server Service Integration Bus,
    when the custom property
    "sib.msgstore.jdbcFailoverOnDBConnectionLoss" is enabled, the
    expected behaviour would be that the HAManager stops the
    messaging engine and the hosting server when the messaging
    engine running in the server loses its connection to the
    database. This stops all the messaging activity in the
    environment until connectivity to the database is restored.
    Also it helps the messaging engine to failover to the other
    server and attempt to start.
    However, in the current scenario, with the new feature
    included where in we would attempt to re-enable the messaging
    engine within few seconds of it going to disabled state, the
    jvm is never terminated even when the custom property
    "sib.msgstore.jdbcFailoverOnDBConnectionLoss" is enabled. This
    causes the messaging engine to continue accepting new work and
    continue the attempts to gain the lock to the database.
    

Problem conclusion

  • The solution involves checking for the property
    "sib.msgstore.jdbcFailoverOnDBConnectionLoss", if the custom
    property is enabled then we will report a local error which
    would terminate the jvm in the case where the messaging engine
    lost its connection to the database.
    
    The fix addresses the issue in following ways
    
    1)Helps to retain the original behaviour by reporting a local
    error incase in case of loss of connectivity between messaging
    engine and the database. The local error would terminate the
    JVM.
    
    2) If both the properties,
    "sib.msgstore.jdbcFailoverOnDBConnectionLoss" and
    "sib.meEnableInstanceOnFailure" are enabled then,
    "sib.meEnableInstanceOnFailure" would take precedence over
    "sib.msgstore.jdbcFailoverOnDBConnectionLoss".
    
    3)  In WebSphere Application Server V8.5, both the properties,
    "sib.msgstore.jdbcFailoverOnDBConnectionLoss" and
    "sib.meEnableInstanceOnFailure" are enabled by default. So, to
    retain the original behaviour of terminating the JVM in case
    of loss of connectivity to the Database you have to set
    "sib.meEnableInstanceOnFailure" to false and
    "sib.msgstore.jdbcFailoverOnDBConnectionLoss" to true .
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.2 and 7.0.0.33.  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

    PM92447

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-07-05

  • Closed date

    2013-11-20

  • Last modified date

    2014-04-10

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PM92447

Modified date: 10 April 2014