Timer Events not Triggering and appear stuck in a Clustered Environment (Setting up RecoveryConfig)
(Doc ID 1956385.1)
Last updated on SEPTEMBER 03, 2020
Oracle Business Process Management Suite - Version 18.104.22.168.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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!