Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

ERROR:STUCK threads are seen in MDM weblogic installation for ActiveVOS task
Problem Description

User reported system overload issue when multiple tasks are created in MDM. Blocking threads are seen from thread dump as follows:


"[STUCK] ExecuteThread: '68' for queue: 'weblogic.kernel.Default (self-tuning)'" #9571 daemon prio=1 os_prio=0 tid=0x00007f769c033000 nid=0x6428 in Object.wait() [0x00007f741d7d5000]
    java.lang.Thread.State: TIMED_WAITING (on object monitor)
  at java.lang.Object.wait(Native Method)
  at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:609)
  - locked <0x00000004c48825c8> (a weblogic.jdbc.common.internal.GenericConnectionPool)
  at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:360)
  at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:347)
  at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:612)
  at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:525)
  at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:144)
  at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:94)
  at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1902)
  at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1643)
  at weblogic.jdbc.jta.DataSource.getConnectionInternal(DataSource.java:520)
  at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:497)
  at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:614)
  at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:594)
  at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:587)
  at org.activebpel.rt.bpel.server.engine.storage.sql.AeDelegatingDataSource.getConnection(AeDelegatingDataSource.java:40)
  at org.activebpel.rt.bpel.server.engine.storage.sql.AeMonitoredDataSource.getConnection(AeMonitoredDataSource.java:41)
  at org.activebpel.rt.bpel.server.engine.storage.sql.AeDataSource.getNewConnection(AeDataSource.java:133)
  at org.activebpel.rt.bpel.server.engine.storage.sql.AeDataSource.getConnection(AeDataSource.java:312)
  at org.activebpel.rt.bpel.server.engine.storage.sql.AeJNDIDataSource.getConnection(AeJNDIDataSource.java:122)
  at org.activebpel.rt.bpel.server.engine.storage.sql.AeDataSource.getCommitControlConnection(AeDataSource.java:161)
  at org.activebpel.rt.bpel.server.engine.storage.sql.AeSQLObject.getCommitControlConnection(AeSQLObject.java:87)
  at org.activebpel.rt.bpel.server.engine.storage.sql.AeSQLObject.getCommitControlConnection(AeSQLObject.java:73)
  at org.activebpel.rt.bpel.server.engine.storage.sql.AeSQLCounterStore.getNextValues(AeSQLCounterStore.java:78)
  at org.activebpel.rt.bpel.server.engine.storage.AeCounter.getNextValues(AeCounter.java:179)
  at org.activebpel.rt.bpel.server.engine.storage.AeCounter.getNextValue(AeCounter.java:162)
  - locked <0x00000004d4450148> (a org.activebpel.rt.bpel.server.engine.storage.AeCounter)
  at org.activebpel.rt.bpel.server.engine.storage.sql.AeSQLProcessStateStorageProvider.getNextProcessId(AeSQLProcessStateStorageProvider.java:171)
  at org.activebpel.rt.bpel.server.engine.storage.AeProcessStateStorage.getNextProcessId(AeProcessStateStorage.java:87)
  at org.activebpel.rt.bpel.server.engine.AePersistentProcessManager.createBusinessProcess(AePersistentProcessManager.java:247)
  at org.activebpel.rt.bpel.impl.AeBusinessProcessEngine.internalCreateProcessWithMessage(AeBusinessProcessEngine.java:1310)
  at org.activebpel.rt.bpel.server.engine.AeBpelEngine.internalCreateProcessWithMessage(AeBpelEngine.java:665)
  at org.activebpel.rt.bpel.impl.AeBusinessProcessEngine.createProcessWithMessage(AeBusinessProcessEngine.java:1265)
  at org.activebpel.rt.bpel.impl.AeBusinessProcessEngine.createProcessWithMessage(AeBusinessProcessEngine.java:1248)
  at org.activebpel.rt.bpel.server.engine.AeBpelEngine.createProcessWithMessage(AeBpelEngine.java:649)
  at org.activebpel.rt.bpel.impl.AeBusinessProcessEngine.queueReceiveDataInternal(AeBusinessProcessEngine.java:1023)
  at org.activebpel.rt.bpel.server.engine.AeBpelEngine.queueReceiveDataInternal(AeBpelEngine.java:1017)
  at org.activebpel.rt.bpel.impl.AeBusinessProcessEngine.queueReceiveData(AeBusinessProcessEngine.java:908)
  at com.activee.rt.mom.cluster.dispatch.AeDispatchManager.dispatchInboundReceive(AeDispatchManager.java:157)
  at com.activee.rt.mom.cluster.dispatch.AeDispatchVisitor.visit(AeDispatchVisitor.java:42)
  at com.activee.rt.mom.cluster.dispatch.AeBufferedInboundReceive.accept(AeBufferedInboundReceive.java:139)
  at com.activee.rt.mom.cluster.dispatch.AeDispatchConsumer.processMessage(AeDispatchConsumer.java:88)
  at com.activee.rt.mom.jms.AeAbstractJmsListener.onMessage(AeAbstractJmsListener.java:180)
  at com.activee.rt.mom.cluster.jms.AeClusterJmsAsyncListener.onMessage(AeClusterJmsAsyncListener.java:70)
  at com.activee.rt.mom.cluster.jms.AeClusterJmsDestination$AeMessageConsumerWork.run(AeClusterJmsDestination.java:644)
  at org.activebpel.work.AeDelegatingWork.run(AeDelegatingWork.java:62)
  at org.activebpel.work.AeExceptionReportingWork.run(AeExceptionReportingWork.java:58)
  at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
  at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
  at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
  at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
  at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
  at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:652)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)

Cause
​This is configuration issue where connection pools are defined very low for ActiveVOS data source and ActiveVOS task threads are waiting for the resource.
Solution
To resolve this issue, set minimum connection pool to 10 and maximum connection pool to 100.
More Information
Applies To
Product: Active VOS
Problem Type: Stability; Configuration
User Type: Administrator
Project Phase: Optimize
Product Version:
Database:
Operating System:
Other Software:

Reference
Attachments
Last Modified Date:6/1/2020 1:26 PMID:620149
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)