My Oracle Support Banner

WLS10.3/KODO 4.2: Stuck thread issue in OpenJPA bundled with WebLogic. (Doc ID 1268411.1)

Last updated on MAY 24, 2017

Applies to:

Oracle Kodo - Version 4.1 and later
Information in this document applies to any platform.

Symptoms

On Kodo 4.x you may notice the below stuck threads.  When it happens it appears to affect many of the other threads.

"[STUCK] ExecuteThread: '44' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x0483c000 nid=0x198 runnable [0x3ac7d000]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.__tc_get(Unknown Source)
at java.util.HashMap.get(Unknown Source)
at org.apache.openjpa.jdbc.kernel.TableJDBCSeq.getStatus(TableJDBCSeq.java:308)
at org.apache.openjpa.jdbc.kernel.TableJDBCSeq.nextInternal(TableJDBCSeq.java:253)
at org.apache.openjpa.jdbc.kernel.AbstractJDBCSeq.next(AbstractJDBCSeq.java:63)
at org.apache.openjpa.util.ImplHelper.generateValue(ImplHelper.java:160)
at org.apache.openjpa.util.ImplHelper.generateFieldValue(ImplHelper.java:144)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.assignField(JDBCStoreManager.java:592)
at org.apache.openjpa.util.ApplicationIds.assign(ApplicationIds.java:464)
at org.apache.openjpa.util.ApplicationIds.assign(ApplicationIds.java:440)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.assignObjectId(JDBCStoreManager.java:576)
at kodo.jdbc.kernel.KodoJDBCStoreManager.assignObjectId(KodoJDBCStoreManager.java:33)

Changes

N/A.

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.