My Oracle Support Banner

Deadline Causing Instance To Be Aborted Due To InvalidProcessDeadlineValueException (Doc ID 1291884.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version: 6.0.0 to 10.3
Information in this document applies to any platform.

Symptoms

An instance deadline is causing the instance to be aborted (rather then be handled by the exception handler properly). In the logs we see the following exception:



Instance '/TestDeadlineProcess1#Default-1.0/1/0' cannot be completed in activity '/TestDeadlineProcess1#Default-1.0/RestoreStatusMicroActivity[HandleException2-In[End]]' since it expired at '2011-02-04 12:31:08-06:00'.
fuego.papi.exception.InvalidProcessDeadlineValueException: Instance '/TestDeadlineProcess1#Default-1.0/1/0' cannot be completed in activity '/TestDeadlineProcess1#Default-1.0/RestoreStatusMicroActivity[HandleException2-In[End]]' since it expired at '2011-02-04 12:31:08-06:00'.
at fuego.server.ProcInst.validateProcessDeadline(ProcInst.java:3105)
at fuego.server.ProcInst.restoreStatusAndRemoveStack(ProcInst.java:2350)
at fuego.server.execution.microactivity.RestoreStatusMicroActivity.execute(RestoreStatusMicroActivity.java:57)
at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:57)
at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
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.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:267)
at fuego.server.execution.ToDoItem.run(ToDoItem.java:556)
at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:775)
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.ToDoQueueThread$PrincipalWrapper.processBatch(ToDoQueueThread.java:469)
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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

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