My Oracle Support Banner

JMS Server Failover Not Working When Setting inactive-connection-timeout-seconds on Datasource Associated with JDBC Store (Doc ID 2097840.1)

Last updated on DECEMBER 05, 2016

Applies to:

Oracle WebLogic Server - Version 12.1.2.0.0 to 12.2.1.0.0 [Release 12c]
Information in this document applies to any platform.

Goal

You are using the JDBC Datasource harvesting setting <inactive-connection-timeout-seconds>300</inactive-connection-timeout-seconds> and this Datasource is associated with a JDBC Store.

You are then getting:

[STUCK] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x00007fce60041800 nid=0x630d in Object.wait() [0x00007fce52db2000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at weblogic.store.io.jdbc.ReservedConnection.lock(ReservedConnection.java:373)
- locked <0x00000006f073eb98> (a weblogic.store.io.jdbc.ReservedConnection)
at weblogic.store.io.jdbc.ReservedConnection.lock(ReservedConnection.java:358)
at weblogic.store.io.jdbc.JDBCStoreIO.updateTableOwnership(JDBCStoreIO.java:3095)
at weblogic.store.io.jdbc.JDBCStoreIO.updateTableOwnershipFromTimer(JDBCStoreIO.java:3050)
- locked <0x00000006f073e818> (a weblogic.store.io.jdbc.TableLockRecord)
at weblogic.store.io.jdbc.ReservedConnection.timerExpired(ReservedConnection.java:599)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:304)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

 

Solution

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

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


In this Document
Goal
Solution
References


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