Description:

Symptoms:
With the route EMS servers between the older EMS version: 4.2, 4.3 (EMS-Server-A) and the newer EMS versions: 4.4.x, 5.x, 6.x, 7.x, 8.x (EMS-Server-B),  you have the same wildcard queue. For example: testQ.> configured within each EMS server. If you create a child queue to a routed queue by defining the home queue server at EMS-Server-A alone with global property within EMS-Server-B.

create queue testQ.q1@EMS-Server-A global

The message sent to testQ.q1 could be routed over to EMS-Server-A if you start a message consumer to receive messages from testQ.q1 in EMS-Server-A, even the testQ.q1 in EMS-Server-A was not defined as global property.





Cause:

The issue has been fixed since EMS 4.4.0. If you use EMS routed servers with newer versions, the messages will not be routed over to EMS-Server-A, you will see following message in the EMS-Server-A server log: 2014-02-13 15:12:42.450 Route configuration: Sending queue 'test.queue14' to server tusprodintems_7555 at tcp://lwang-t430:7555,tcp://lwang-t430:7555 - sent to non-global queue 2014-02-13 15:12:42.450 (NON-IO) Flow stalled on dest queue:test.queue14 from route of tusprodintems_7555

Use a supported release of EMS Server from EMS 5.x.x .

Dynamic queue without global property serving as a routed queue