KB Article #177831
API Gateway does not reconnect to Tibco EMS server after a connection drop
Problem
If the connection between API Gateway and Tibco EMS server is dropped (by a firewall as example), there is no try to reconnect to JMS queue once that's possible.
Resolution
* Problem is because of reconnection parameter sets on the JMS queue. This has to be configured on Tibco EMS side.
* Configuration of reconnection can be done in the tibemsd.conf file with the reconnect_attempt_count, reconnect_attempt_delay, reconnect_attempt_timeout parameters. Default parameters handles only a short connection drop, so it's better to increase it. Here is an example of possible values:
connect_attempt_count = 60000
connect_attempt_delay = 6000
connect_attempt_timeout = 1000
reconnect_attempt_count = 100000
reconnect_attempt_delay = 6000
reconnect_attempt_timeout = 1000
* In order to better handling connection drops, it is also possible to configure heartbeat between client and server. This can be done with the following parameters:
client_heartbeat_server = 30
server_timeout_client_connection = 3600
server_heartbeat_client = 30
client_timeout_server_connection = 3600
The value of 30 means that the heartbeat will be send every 30 seconds.
The value of 3600 seconds mean that the client server will wait for 60 minutes before disconnecting and never trying again.