Cluster configuration fails with an error indicating that Tomcat did not stop cleanly

During cluster configuration, a scheduled health check can try to restart Tomcat at the same time that the cluster setup is stopping it. The timing clash can make the stop appear to fail with an error message such as a service job reported as canceled. This causes the cluster configuration to stop.

(AA-1125)

Workaround:

Perform a full factory reset on both the nodes using the system factory-reset command and rerun the cluster configuration.