fuego.papi.exception.InstanceNotFoundException Is Thrown When A Child Instance Tries To Notify A Parent Instance That Has Been Disposed

(Doc ID 1411116.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version: 6.0.5 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

You have a main process flow that calls a subflow. Parent (main) instance ID and child instance IDs are created.

Having child instances running, make the parent instance reach End state (forcibly, for example, using a Grab). Then, let Disposer dispose the parent instance.

Engine logs will show a message similar to the following one after finishing the execution of a child instance:

Could not send notification.
Reason: An instance in Process '/TestAuditTrailProcess#Default-1.0' could not be notified.
Caused by: Instance '/TestAuditTrailProcess#Default-1.0/223/0' was not found.
fuego.papi.exception.CannotStoreNotificationException: An instance in Process '/TestAuditTrailProcess#Default-1.0' could not be notified.
at fuego.server.AbstractProcessBean.receiveNotification(AbstractProcessBean.java:2560)
...

Caused by: fuego.papi.exception.InstanceNotFoundException: Instance '/TestAuditTrailProcess#Default-1.0/223/0' was not found.
at fuego.server.persistence.jdbc.JdbcProcessInstancePersMgr.load(JdbcProcessInstancePersMgr.java:1565)
...

Caused by: fuego.papi.exception.InstanceNotFoundException: Instance '/TestAuditTrailProcess#Default-1.0/223/0' was not found.

Cause

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 hundreds of Community platforms