About Action on Startup Error Options

When Integration Server that is configured for clustering starts up, errors may prevent Integration Server from connecting to the Terracotta Server Array. These errors can be caused by some of the following: a configuration issue with the Terracotta license file, an unavailable or incorrectly configured Terracotta Server Array, or an unavailable database.

When you configure clustering for an Integration Server, you can determine how Integration Server responds when the server starts and cannot connect to the Terracotta Server Array. The action Integration Server takes affects whether Integration Server is available to process requests, which Integration Server features are available, and how you might correct the errors. The Action on Startup Error parameter determines how Integration Server reacts when the Terracotta Server Array cannot be reached at startup. You can specify one of the following options for the Action on Startup Error parameter.

Start as Stand-Alone Integration Server. If Integration Server encounters any errors that prevent it from joining the cluster at start up, Integration Server starts as a stand-alone, unclustered Integration Server. Integration Server continues to receive requests on inbound ports and serve requests. Integration Server does not use any distributed caches and instead uses local caches. You can use Integration Server to make changes needed to resolve the startup errors. When you restart Integration Server, Integration Server, will rejoin the cluster if Integration Server does not encounter any start up errors that prevent the connection to the Terracotta Server Array.

Shut Down Integration Server. If Integration Server encounters any errors that prevent it from joining the cluster at start up, Integration Server shuts down immediately. To make any changes to the clustering configuration, you must edit the configuration while running in safe mode. If you need to change the Terracotta Server Array URLs, you must start Integration Server in safe mode, change the values, and restart the Integration Server.

Enter Quiesce Mode on Stand-Alone Integration Server. If Integration Server encounters any errors that prevent it from joining the cluster at start up, Integration Server starts as a stand-alone, unclustered Integration Server in quiesce mode. When Integration Server is in quiesce mode, only the diagnostic port and quiesce port are enabled. Integration Server will not receive requests on inbound ports. However, you can use Integration Server and Integration Server Administratorto make changes needed to correct the startup errors. After correcting the errors, exit quiesce mode. When exiting quiesce mode, Integration Server starts all the cache managers and joins the cluster.

If Integration Server encounters any errors that prevent it from joining the cluster when exiting quiesce mode, Integration Server does not re-enter quiesce mode. Instead, Integration Server runs as an unclustered, stand alone server. Integration Server captures any errors that occurred while attempting to join the cluster in a report displayed in Integration Server Administrator when the server exits quiesce mode. Use the report to help correct the underlying configuration errors. Then, to rejoin the cluster, either restart Integration Server or enter and then exit quiesce mode.

To use the Enter Quiesce Mode on Stand-Alone Integration Server option, a quiesce port must be configured for Integration Server. If a quiesce port is not configured and the Enter Quiesce Mode on Stand-Alone Integration Server option is selected, when Integration Server encounters any errors that prevent it from joining the cluster at start up, Integration Server shuts down instead of entering quiesce mode.