Servoy Application Servers will not restart right away when they are disconnected from the cluster.
If a server stays disconnected for more then 60 seconds, then it will restart. You can tune the timeout (in seconds) by using something like this in servoy.properties:
- Code: Select all
cluster.timeToForceShutdown=180
This way Servoy Application Servers will wait for the connection to be restored (network problems, active Terracotta server switch, ...). The active-passive should switch fast enough for default setting. If you experience something different, please file a case. You should be able to test it yourself.
Logging information related to the cluster can be found in two places:
- in the Terracotta server and client logs that can be found at the location specified in "tc-config.xml". Server logs show Terracotta Server activity and client logs show Servoy Application Server activity.
- in the Servoy log file. Terracotta life-cycle related messages can be controllerd using
- Code: Select all
log4j.logger.com.servoy.j2db.terracotta.TerracottaStatusMonitor=...
in the servoy.properties file (where "..." can be ERROR, WARN, INFO, DEBUG, TRACE). INFO is recommended for most cases, as it gives an overview of cluster events that can be useful when diagnosing problems, while at the same time the number of messages should be low.
Changing this log setting to INFO level might help you better understand what's going on when you test things like this.