Resolution:
Description:
===========
Other symptom of the issue:

If tibemsadmin connected to A, there is a connection ID in "show route B".
If tibemsadmin connected to B, there is NO connection ID in "show route A".

Causes:
======
When there is a temporary network problem between A and B, B detects that A is disconnected while A is not aware that the route is disconnected.  B keeps trying to reconnect to A.  When network connection resumes, A logs "rejected connect from route: route already connected", and B logs "Route 'xxx' connecting to url 'xxx'".

Resolution:
=========
To prevent this, configure the following parameters in tibemsd.conf of both A and B:

server_heartbeat_server
server_timeout_server_connection

To immediately fix the issue, delete the route connection.  For example, if tibemsadmin is connected to A, run:

delete connection &ltroute_connection_ID>

Environment:
===========
All

Keywords:
=========
reject server_heartbeat_server route server_timeout_server_connection

When there is a route between two servers A and B, why does A log "rejected connect from route: route already connected", and B log "Route 'xxx' connecting to url 'xxx'"?