Quantcast
Channel: The LiveCycle Post » cluster
Viewing all articles
Browse latest Browse all 4

LiveCycle ES2: This scheduler instance (SchedulerName) is still active but was recovered by another instance in the cluster

$
0
0

Issue

If you are working with LiveCycle ES2 in a cluster you may notice the following message in the server log:

org.quartz.impl.jdbcjobstore.JobStoreSupport findFailedInstances “This scheduler instance (<SchedulerName>) is still active but was recovered by another instance in the cluster. This may cause inconsistent behavior”.

Reason

This exception often occurs when the clock times on the cluster nodes are not synchronized.  If the clock times on cluster nodes are more than 1.7 seconds out of synch you will start to see these Quartz messages in the log.

Solution

Synchronize the time on all cluster nodes and then restart the cluster.  The messages should no longer appear in the log.

reference: (1647846)


Viewing all articles
Browse latest Browse all 4

Latest Images

Trending Articles



Latest Images