Hybrid Integration 10.1 | Integrating On-Premises Applications | Document Conventions | Managing Server Clustering | How Integration Server Cluster and Terracotta Server Array Handle Failures | What Happens when Integration Server Cannot Connect to the Terracotta Server Array? | Integration Server Cannot Connect to the Servers in the tc-config.xml File | Solution
 
Solution
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 the following Java system properties to the custom_wrapper.conf file, which is located the Software AG_directory /profiles/IS_instance_name/configuration directory:
1. In a text editor, open custom_wrapper.conf.
2. 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.
3. Save and close custom_wrapper.conf.
4. Restart Integration Server for the changes to take effect. For more information about passing Java system properties to Integration Server, see webMethods Integration Server Administrator’s Guide.
Copyright © 2015- 2017 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.