Instances Remain Locked For Hours Past The Activity Timeout interval
(Doc ID 1166213.1)
Last updated on MARCH 07, 2025
Applies to:
Oracle Business Process Management Suite - Version 10.3.1 and laterInformation in this document applies to any platform.
Symptoms
The following error is thrown and the instance remains locked for hours
You are currently executing another operation for instance '/CustomFulfillment#Default-1.4/1412235/33'. You cannot execute more than one operation at a time for an instance.
fuego.papi.exception.CannotLockInstanceException: You are currently executing another operation for instance '/CustomFulfillment#Default-1.4/1412235/33'. You cannot execute more than one operation at a time for an instance.
at fuego.server.ProcInstOwner.createLockException(ProcInstOwner.java:119)
at fuego.server.AbstractInstanceService.getLocked(AbstractInstanceService.java:148)
at fuego.server.execution.EngineExecutionContext.acquireCurrentInstance(EngineExecutionContext.java:1694)
at fuego.server.execution.EngineExecutionContext.preImmediateExecution(EngineExecutionContext.java:1510)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:295)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
at fuego.server.AbstractProcessBean.runTask(AbstractProcessBean.java:3208)
at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1410)
at fuego.lang.JavaObject.invoke(JavaObject.java:227)
at fuego.component.Message.process(Message.java:585)
at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:780)
at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:244)
at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
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 |