Thomas Wood created ARTEMIS-2337:
------------------------------------
Summary: federated queues not working correctly with wildcards or
defaults
Key: ARTEMIS-2337
URL: https://issues.apache.org/jira/browse/ARTEMIS-2337
Project: ActiveMQ Artemis
Issue Type: Bug
Affects Versions: 2.8.0
Environment: RHEL
Reporter: Thomas Wood
artemis1 upstream federated to artemis2.
clients consume artemis2 messages from artemis1.
client connects to artemis1 and messaged are routed from artemis2 as expected,
but any new messages that land on artemis2 are not routed to artemis1 until
either the client reconnects.
It seems that the issue is related to wildcards:
<queue-policy name="queue-federation" priority-adjustment="1"
include-federated="false">
<include queue-match="#" address-match="#"/>
</queue-policy>
The following config works as expected with the client receiving message prior
and during the client connection.
<queue-policy name="queue-federation" priority-adjustment="1"
include-federated="false">
<include queue-match="TEST.OUT_Q" address-match="TEST.OUT_Q"/>
</queue-policy>
also noticed that the following causes the issue too:
<queue-policy name="queue-federation" priority-adjustment="1"
include-federated="false">
<include queue-match="TEST.OUT_Q" address-match="TEST.OUT_Q"/>
<exclude queue-match="ActiveMQ.#" address-match="#"/>
</queue-policy>
but not:
<queue-policy name="queue-federation" priority-adjustment="1"
include-federated="false">
<include queue-match="TEST.OUT_Q" address-match="TEST.OUT_Q"/>
<exclude queue-match="ActiveMQ.#" address-match="ActiveMQ.#"/>
</queue-policy>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
