What is the cause of the following message in the EMS server log file? Why is the message continuously logged and how can it be stopped?‘EMS-SERVER2' connecting to url 'tcp://xxxxxxx:nnnn’

What is the cause of the following message in the EMS server log file? Why is the message continuously logged and how can it be stopped?‘EMS-SERVER2' connecting to url 'tcp://xxxxxxx:nnnn’

book

Article ID: KB0094231

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Message Service -
Not Applicable -

Description

Resolution:
Environment:
===========
EMS 5.1.0 and later

Resolution:
==========
If you have "routing=enabled” configured in the main configuration file (tibemsd.conf), and if EMS-SERVER1 specifies a route to EMS-SERVER2 defined in the routes.conf file, then EMS-SERVER1 will try to connect to EMS-SERVER2 upon startup.  If the connection between the two servers is successfully established, those messages (Route 'EMS-SERVER2' connecting to url 'tcp://localhost:7022') would not be printed.  As long as the connection between the two servers is broken, those messages will be printed in EMS 5.1.0 and later.

The "routing connection retry time interval" when a route connection is broken is 2 seconds and this interval is not configurable. The server with a broken route will continue to reconnect every 2 seconds until it reconnects to the remote server or the route is deleted.

Issue/Introduction

What is the cause of the following message in the EMS server log file? Why is the message continuously logged and how can it be stopped?‘EMS-SERVER2' connecting to url 'tcp://xxxxxxx:nnnn’