Failure Destination Cache Properties

Enabling the failure destination cache prevents Communications Server from trying to connect to an unavailable or unreachable destination forever, which can block threads. To configure the failure destination cache, set the following JVM properties:

-Dcom.ericsson.ssa.container.ENABLE_FAILURE_DEST_CACHE=true|false

If true, enables the failure destination cache. The default is false.

-Dcom.ericsson.ssa.container.FAILURE_RETRY_ATTEMPTS=n

Specifies the number of retry attempts Communications Server performs to connect to a destination. After n failures Communications Server avoids connecting to the destination for the duration governed by the RETRY_AFTER_FAILURE_PERIOD property.

-Dcom.ericsson.ssa.container.RETRY_AFTER_FAILURE_PERIOD=ms

Specifies the initial amount of time that Communications Server waits after FAILURE_RETRY_ATTEMPTS to retry again. The ms is the time in milliseconds, and the default is 30000, or 30 seconds.

-Dcom.ericsson.ssa.container.MAX_RETRY_AFTER_FAILURE_PERIOD=n

The RETRY_AFTER_FAILURE_PERIOD doubles after each failure until it reaches the value specified by this property. The ms is the time in milliseconds, and the default is 300000, or 300 seconds, or 5 minutes.

-Dcom.ericsson.ssa.container.ENABLE_FAILURE_DEST_CACHE_LOGGING=true|false

If true, enables failure destination cache logging. The default is false.

To promote faster release of blocked threads, you can set an additional JVM property:

-Dcom.ericsson.ssa.container.grizzlyConnectTimeoutmillis=ms

This property is not tightly related to the failure destination cache. It may be helpful to users who are experiencing problems with long delays establishing calls to unavailable or unreachable destinations. The ms is the timeout in milliseconds, and the default is 30000, or 30 seconds.