Integration Server Cannot Connect to the Servers in the tc-config.xml File
If Integration Server has made the initial connection to the Terracotta Server Array and has obtained the tc-config.xml file, but the server cannot connect to any other servers in the Terracotta Server Array, Integration Server will wait indefinitely. Integration Server writes entries to the tc-client-logs and ehcache log files.
You can configure Integration Server to wait for a specified amount of time to connect to the Terracotta Server Array. After the wait time elapses, Integration Server takes the action associated with the selected option for the Action on Startup Error parameter. You configure the wait time for Integration Server by adding Java system properties to the custom_wrapper.conf file.
1. Go to the Software AG_directory /profiles/IS_instance_name/configuration directory.
2. In a text editor, open the custom_wrapper.conf file.
3. Add two wrapper.java.additional.n parameters as follows:
wrapper.java.additional.n=-Dcom.tc.l1.max.connect.retries=retryAttempts
wrapper.java.additional.n=-Dcom.tc.l1.socket.reconnect.waitInterval
=waitInterval_ms
Where:
n is the next unused sequential number.
retryAttempts is the number of attempts
Integration Server is to make to connect to the
Terracotta Server Array.
waitInterval_ms is the number of milliseconds
Integration Server is to wait before each attempt to retry the connection.
4. Save and close the file.
Note:
For Microservices Runtime, and the properties to JAVA_CUSTOM_OPTS in Integration Server_directory /bin/server.bat(sh). For example, the property might look like the following: set JAVA_CUSTOM_OPTS="Dcom.tc.l1.max.connect.retries=retryAttempts -Dcom.tc.l1.socket.reconnect.waitInterval= waitInterval_ms"