Event Timer Fails When Process is shut down or server is restarted
Last updated on MARCH 08, 2017
Applies to:Oracle Business Process Management Suite - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
***Checked for relevance on 14-January-2014***
A BPM Process that has a 'Timer Event' start works as planned, once deployed, but there does not seems to be a way of shutting the service down gracefully in the EM console. Pressing the "Shut Down..." button does not work as the Event Timer still fires, producing a remoteFault 'Fault'.
The same error appears when doing the following: Shut down the BPM process containing an event timer, wait for a few minutes for the timer cycle to occur and then Stop and restart the Admin Server and soa_server1.
Error which appears in the log is the following:
[oracle.soa.bpel.engine] [tid: orabpel.invoke.pool-8.thread-15] [userId:
[APP: soa-infra] [composite_name: BPMTimerTest] [component_name: BPMTimer]
[component_instance_id: 160015] This exception occurred because the error
thrown in the BPMN flow was not handled by any error handlers and reached the
top-level scope. Root cause : [[
Router for default/BPMTimerTest!1.0*soa_17bda504-4949-412f-871e-2593a442df11
is not able to process messages. The composite state is set to "off". The
composite can be turned "on" by using the administrative consoles.</summary>
,detail=<detail>Message Router for
default/BPMTimerTest!1.0*soa_17bda504-4949-412f-871e-2593a442df11 is not able
to process messages. The composite state is set to "off". The composite can
be turned "on" by using the administrative consoles.</detail>
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