Resolution:
Causes:
======
This error message could occur when a client is using a Fault Tolerant (FT) URL to connect with an EMS server. Having lost the connection to the EMS server at some point (i.e., due to network problem) the client tried to reconnect to the EMS server. However, the EMS server thought the original client connection was good since the connection object was still active in the EMS server.

Platforms:
========
All

Resolution:
========
There are set of parameters in tibemsd.conf that instruct the server to drop the connection when not receiving heartbeats from the client and another set of parameters that instruct the client to drop the connection when not receiving heartbeats from the EMS server.

If the parameters are not set, the server/client will drop the connections upon OS notification.  That is, only when the OS reports the connection as broken will the EMS Server detect the failurebe notified.  The timeout will vary depending on the OS. For example, if there is a network outage between the client and server, then upon OS notification, the server will disconnect the client.  It is also possible that the client machine would detect that the connection is broken before the server machine does.

-------------------------------------------------------
Detecting Network Connection Failure Parameters

- client_heartbeat_server and server_timeout_client_connection - These instruct the server when to drop the connection.

- server_heartbeat_client and client_timeout_server_connection - These instruct the client when to drop the connection.

client_heartbeat_server {interval in seconds}

In a server-to-client connection, clients send heartbeats to the server at this interval. The client_heartbeat_server parameter must be specified when a server_timeout_client_connection is set. The client_heartbeat_server interval should be no greater than one third of the server_timeout_client_connection limit.

server_timeout_client_connection

server_timeout_client_connection {limit in seconds}
In a server-to-client connection, if the server does not receive a heartbeat for a period exceeding this limit, it will close the connection. We recommend setting this value to approximately 3 times the heartbeat interval, as is specified in client_heartbeat_server.
Zero is a special value, which disables heartbeat detection in the server although clients will still send heartbeats.

server_heartbeat_client {interval in seconds}

In a server-to-client connection, the server sends heartbeats to all clients at this interval.
When omitted or zero, the default is 5 seconds.

client_timeout_server_connection {limit in seconds}

In a server-to-client connection, if a client does not receive a heartbeat for a period exceeding this limit, it will close the connection. We recommend setting this value at least.5 times the heartbeat interval. Zero is a special value, which disables heartbeat detection in the client although the server still sends heartbeats.
-------------------------------------------------------

Please refer to EMS User's Guide -> Using the Configuration Files -> tibemsd.conf.

Keywords:
reconnect active

Cause of the following error message in the EMS server log: "reconnect failed: connection active for id".