Timer Events not Triggering and appear stuck in a Clustered Environment (Setting up RecoveryConfig)
Last updated on SEPTEMBER 20, 2017
Applies to:Oracle Business Process Management Suite - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
***Checked for relevance on 06-June-2016***
Timer schedules are lost in a clustered environment if the cluster is restarted 2 or more times. There will be no exceptions in the logs. You will only notice that timer activities are not firing properly and appear to be stuck.
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