Resolution:
After deleting a bridge and restarting the EMS server, the EMS server fails to start and exits with the following error messages:

ERROR: Error: unable to add bridge specified in file=bridges.conf, line=xxx. Error=Already exists.
ERROR: Configuration error: file=bridges.conf, line=xxx error in the bridge description, unable to proceed.

Environment:

All OS
All h/w platforms
All Enterprise Message Service (EMS) versions.

Symptoms:

The EMS server fails to start with the following error messages:

ERROR: Error: unable to add bridge specified in file=bridges.conf, line=xxx. Error=Already exists.
ERROR: Configuration error: file=bridges.conf, line=xxx error in the bridge description, unable to proceed.

Cause:

When there are multiple bridges defined in the bridges.conf from one source (i.e. topic X) destination to multiple target destinations (i.e. queue A and queue B), the entry for these bridges in the bridges.conf should look like:

[topic: X]
    queue = A
    queue = B
    
If the bridges.conf in the above situation is defined as:


[topic: X]
    queue = A

[topic: X]
    queue = B


and the bridge between the topic X and queue B is deleted from tibemsadmin using the command “delete bridge source=topic:X target=queue:B”, then the bridge between topic X and queue B will be deleted and EMS server will add a duplicate entry of the bridge between topic X and queue A to the bridges.conf file and it will look like:

[topic: X]
    queue = A

[topic: X]
    queue = A

As long as the new bridges.conf file is not re-read, the EMS server will function correctly. However, after this if the EMS server is restarted, it will try to read the modified bridges.conf which contains duplicate entries and will fail to start with the above error messages.

Resolution:

While defining bridges from a single source to multiple targets, instead of defining bridges like:

[topic: X]
    queue = A

[topic: X]
    queue = B

define them like:


[topic: X]
    queue = A
    queue = B

EMS server fails to start after deleting a bridge after complaining about duplicate bridges in the bridges.conf during start up.