My Oracle Support Banner

JMSJDBCStore Declared Unhealthy for Half an Hour (Doc ID 1320141.1)

Last updated on JULY 20, 2018

Applies to:

Oracle Communications ASAP - Version 5.2.0 and later
Information in this document applies to any platform.

Symptoms

The JMS JDBCStore is declared unhealthy.
When this problem occurs, the following is seen in the WebLogic logs:

####<Nov 8, 2010 6:53:43 PM CET> <Warning> <JTA> <gmihsact003> <AdminServer> <[ACTIVE] ExecuteThread: '99' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1289238823866> <BEA-110484> <The JTA health state has changed from HEALTH_OK to HEALTH_WARN with reason codes: Resource WLStore_asap_AS52.JMSJDBCStore declared unhealthy.>



When the problem ends, the following is seen in the WebLogic logs:

####<Nov 8, 2010 7:23:45 PM CET> <Info> <JTA> <gmihsact003> <AdminServer> <[ACTIVE] ExecuteThread: '73' for queue: 'weblogic.kernel.Default (self-tuning)'>
<> <> <> <1289240625421> <BEA-110207> <A previously unavailable XA resource [WLStore_asap_AS52.JMSJDBCStore] is now available.>
####<Nov 8, 2010 7:23:45 PM CET> <Info> <JTA> <gmihsact003> <AdminServer> <[ACTIVE] ExecuteThread: '73' for queue: 'weblogic.kernel.Default (self-tuning)'>
<> <> <> <1289240625421> <BEA-110483> <The JTA health state has changed from HEALTH_WARN to HEALTH_OK.>

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.