EMS Java Client does not reconnect to EMS server.
Article ID: KB0087604
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
1). If an EMS client application uses FT URL (i.e., tcp://host1:port1, tcp://host2:port2, or tcp://host1:port1, tcp://host1:port1) to connect to an EMS server, configure the heartbeat/timeout in tibemsd.conf.
client_heartbeat_server
server_timeout_client_connection
Description
=======
When EMS connection is broken due to an unstable network or an EMS failover, the EMS Java client application does not reconnect to the EMS server. An EMS C client application can reconnect successfully.
Resolution
=======
In EMS Java client 6.3 and above, the EMS client does not send ping packets to the server by default. If the "client_heartbeat_server" is not configured in tibemsd.conf and an application is only receiving from an EMS server, when a connection is broken, the application is not aware that the connection is no longer there. The application appears to be hanging and needs to be restarted.
1). If an EMS client application uses FT URL (i.e., tcp://host1:port1, tcp://host2:port2, or tcp://host1:port1, tcp://host1:port1) to connect to an EMS server, configure the heartbeat/timeout in tibemsd.conf.
client_heartbeat_server
server_timeout_client_connection
server_heartbeat_client
client_timeout_server_connection
Issue/Introduction
EMS Java Client does not reconnect to EMS server.
Additional Information
EMS User's Guide
KB 36123, 31944, 35682, 33918
KB 36123, 31944, 35682, 33918
Feedback
Yes
No
Powered by
