Failed instance / inconsistent behavior after upgrade (cluster setup)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Failed instance / inconsistent behavior after upgrade (cluster setup)


After upgrading dotCMS 3 to 4 in a cluster setup (2 instances) we are getting the following INFO / WARN logs every +- 20 seconds in the dotCMS.log

Instance 1
INFO quartz.DotJobStore: ClusterManager: detected 1 failed or restarted instances.
INFO quartz.DotJobStore: ClusterManager: Scanning for instance "2"'s failed in-progress jobs.

Instance 2
WARN quartz.DotJobStore: This scheduler instance (2) is still active but was recovered by another instance in the cluster.  This may cause inconsistent behavior.

Could anyone tell me what this means?

Thank you.

-- - Open Source Java Content Management
You received this message because you are subscribed to the Google Groups "dotCMS User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit
For more options, visit