What happens when a client temporarily loses the connection to IBM Spectrum Symphony?

The following are the four environment variables that you can define on your client machine to influence how the client behaves when it loses its connection to the session manager:

  • SOAM_RECONNECTION_RETRY_INTERVAL
  • SOAM_RECONNECTION_RETRY_LIMIT
  • SOAM_RELOCATED_RECONNECTION_RETRY_INTERVAL
  • SOAM_RELOCATED_RECONNECTION_RETRY_LIMIT

How variables work together

When a client loses its connection to the session manager, it tries to reconnect to the existing session manager up to the SOAM_RECONNECTION_RETRY_LIMIT. Each reconnection attempt is SOAM_RECONNECTION_RETRY_INTERVAL seconds apart.

  • If the client succeeds in reconnecting to a session manager, the API attempts to refresh all sessions on the connection. If the session manager was relocated during the disconnection, any non-recoverable sessions are aborted.
  • If reconnection was unsuccessful, the API stops trying to reconnect to the existing session manager and attempts to locate a new session manager. It then tries to locate and connect to a new session manager up to the SOAM_RELOCATED_RECONNECTION_RETRY_LIMIT. Each reconnection attempt is SOAM_RELOCATED_RECONNECTION_RETRY_INTERVAL seconds apart.
    • If the client fails to reconnect to a session manager, the API stops trying to reconnect and throws an exception indicating that IBM® Spectrum Symphony is no longer available.
    • If the client succeeds in reconnecting to a session manager, the API attempts to refresh all sessions on the connection. If the session manager was relocated during the disconnection, any non-recoverable sessions are aborted.