When running multiple clustered Servoy Application Servers on the same machine a couple of additional configuration steps are required.
Why run multiple clustered Servoy Application Servers on the same machine
Logically, is does not make sense to run multiple clustered Servoy Application Servers on the same machine, as the the goal of clustering is load balancing, scalability and failover. The only valid reason for doing so is testing purposes
Even when not running Servoy Cluster, there are a few things to take into consideration. These are documented [here] and also apply when the Servoy Application Servers are clustered.
take care to change the RMI ports (servoy.rmiStartPort, all default to 1099 in servoy.properties) and Tomcat ports (shutdown ports from 8005 to 11005, 12005, ... (for example), connector ports from 8080 to 8081, 8082, ... (for example) and from 8009 to 11009, 12009, ... (for example) in server.xml) on each one to avoid conflicts. Also clear caches (browser/java/.servoy) - in case you used those Application Servers before.
in worker.properties, change the ports & hostnames to the correct ones (can be same hostname for more workers, but with different ports (11009, 12009 for example)).
in tc-config.xml change line "<logs>%(user.home)/terracotta/client-logs</logs>" to "<logs>%(user.home)/terracotta/client-logs/%(tc.node-name)</logs>".
set an unique node name for each server by adding "-Dtc.node-name=nodeName" after "-Dtc.config=terracotta\tc-config.xml" in each "start_servoy_clustered.*".
Overview
Content Tools
Activity