Resolution:
If the client application is using an FT url, and therefore, the EMS Server will maintain the
connection information until the ft_reconnect_timeout elapses or the client closes explicitly
the connection or the connection is deleted from the admin tool.

As  the client application is killed, the client does not explicitly call the connection.close() method.
Because EMS Server is maintaining the connection information, when the client application is
restarted, the connection creation will fail because you are using the same client ID than the
connection maintained by the EMS Server.

You can reduce the ft_reconnect_timeout value in the main configuration file (if the parameter is
not there, you can add it) so that connection information is purged by the EMS server fast or the
administrator could delete the "pending" connection from the admin tool before client gets started
again.

Notice that reducing the ft_reconnect_timeout to a very low value could have an impact on the
ability of EMS clients to reconnect in the event of an EMS Server failure. Indeed, once the
ft_reconnect_timeout interval has elapsed, the EMS Server will "clear" the connection and
if later the client API attempts to reconnect (here we are not talking about restarting the
application but instead, the client API trying to reconnect), it will fail because the EMS Server
does not know anything about the connection. The default value is 60 seconds.
So we need to adjust considering this case also.