Products | Versions |
---|---|
TIBCO Enterprise Message Service | - |
Not Applicable | - |
Resolution:
Description:
============
A). Start two EMS servers in FT mode.
B). Connect to the active EMS server via the tibemsadmin tool and create a queue active.test.
C). Connect to the backup EMS server via the tibemsadmin tool and create a queue backup.test.
D). Stop the active EMS server so that there will be a FT failover and the current backup server becomes active.
E). Do a “show queues” for the newly active EMS server. It will not show the active.test.
Environment:
===========
All H/W and O/S
TIBCO Enterprise Message Service – All versions
Symptoms:
========
The destinations created in the old active EMS server prior to creating destinations in the backup EMS server disappear after FT failover.
Cause:
=====
The EMS server reads the configuration files only during startup and loads the state to its memory. When two EMS servers are running in FT mode, both the servers have the initial configuration loaded up in their memory. When a new queue is created in the primary server, after both the servers have been initialized, it writes to the shared config file with the new change however the backup server will be un-aware of this change. Any vchange made to the backup server afterwards will be transparent to the backup server. After a FT failover occurs, the backup server loads the configuration from its memory (only the configuration that it read during its startup and any change that has been especially done in the backup server side after startup) and re-writes the config file. Any change made in the primary ENMS server before modifying the secondary server is lost.
Resolution:
==========
This is expected behavior. When fault-tolerant servers share configuration files, you must limit configuration changes to the current primary server only. Separately reconfiguring the backup server can cause it to overwrite the shared configuration files. Unintended mis-configuration can result. Making any configuration changes in the secondary/backup EMS server is not recommended while the primary EMS server is running.