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 Is Disconnected from the Terracotta Server Array? | Solution
 
Solution
The way in which Integration Server rejoins the Terracotta Server Array depends on how long the connection is lost.
If...
Then...
The connection is momentarily interrupted
If the Terracotta Server Array is configured to automatically reconnect, the Integration Server identity and state are retained on the Terracotta Server Array so that Integration Server can readily reconnect when the connection is restored. To learn more about the reconnect behavior of a Terracotta Server Array, see the information about automatic client reconnect in the Configuring Terracotta Clusters For High Availability documentation on the Terracotta website.
If the Terracotta Server Array is not configured to automatically reconnect, the Integration Server will attempt to rejoin the Terracotta Server Array.
The connection is lost for a long period of time
Integration Server attempts to rejoin the Terracotta Server Array. To prevent inconsistencies in your distributed cache, Terracotta automatically acquires a new cache state from the Terracotta server after rejoining the Terracotta Server Array. For more information about the rejoin and nonstop behavior of 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.