My Oracle Support Banner

Threads Stuck In BPM Managed Servers (Doc ID 2959076.1)

Last updated on JULY 05, 2023

Applies to:

Oracle Business Process Management Suite - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

Intermittently stuck threads occur during the recovery process.

STACK THREAD PRINTED IN THE LOGS WHEN THE ISSUE OCCURS:
---------------------
<[ACTIVE] ExecuteThread: '282' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <add4c47d-af15-4887-b70b-c74572e77996-0216c1fc> <1679445511737> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000337> <[STUCK] ExecuteThread: '299' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "2,400" seconds working on the request "Workmanager: default_dspSystem, Version: 0, Scheduled=true, Started=true, Started time: 2400332 ms
", which is more than the configured time (StuckThreadMaxTime) of "2,400" seconds in "server-failure-trigger". Stack trace:
sun.nio.ch.FileDispatcherImpl.read0(Native Method)
sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
sun.nio.ch.IOUtil.read(IOUtil.java:197)
...
com.collaxa.cube.persistence.dao.impl.jpa.JpaDeliveryMessageDaoImpl.getRecoverCallbackMessages(JpaDeliveryMessageDaoImpl.java:190)
com.collaxa.cube.engine.agents.recovery.RecoveryManager.recoverCallback(RecoveryManager.java:467)
com.collaxa.cube.engine.agents.recovery.RecoveryManager.performRecovery(RecoveryManager.java:307)
com.collaxa.cube.engine.CubeEngine.handleRecover(CubeEngine.java:479)
com.collaxa.cube.engine.ejb.impl.CubeEngineBean.handleRecover(CubeEngineBean.java:589)
com.collaxa.cube.engine.ejb.impl.bpel.BPELEngineBean_uhguq6_ICubeEngineLocalBeanImpl.__WL_invoke(Unknown Source)
weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:33)
com.collaxa.cube.engine.ejb.impl.bpel.BPELEngineBean_uhguq6_ICubeEngineLocalBeanImpl.handleRecover(Unknown Source)
com.collaxa.cube.engine.dispatch.message.domain.RecoverMessageHandler.handle(RecoverMessageHandler.java:34)
com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:154)
com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:150)
com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:90)
com.collaxa.cube.engine.dispatch.WMExecutor$W.run(WMExecutor.java:248)
weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
weblogic.work.ExecuteThread.run(ExecuteThread.java:360)
>

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!


In this Document
Symptoms
Cause
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.