Last updated on SEPTEMBER 16, 2016
Applies to:Oracle Communications Unified Inventory Management - Version 7.1.2 to 7.1.2 [Release 7.1.2]
Information in this document applies to any platform.
Custom Timer gets executed for all the manage servers in the cluster even if the <CustomTimer>.cluster flag in timers.properties is set to true. Because of which the "Optimistic locking errors" is also observed.
cluster: The flag indicates whether this timer is cluster aware. If it is set to true, then there will only one instance of this timer running in the cluster. If it is set to flase, then each server will have this timer instance running locally.
Most of the timer should be cluster aware. An example of non-cluster aware timer is the timer which monitors whether the server which manages the cluster aware timers is still alive.
The default value is true.
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