[
https://issues.apache.org/jira/browse/ARTEMIS-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Andre Pearce updated ARTEMIS-2337:
------------------------------------------
Priority: Minor (was: Critical)
> 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
> Priority: Minor
>
> artemis1 upstream federated to artemis2.
> clients consume artemis2 messages from artemis1.
> client connects to artemis1 and messages are routed from artemis2 as
> expected, but any new messages that land on artemis2 are not routed to
> artemis1 until 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 to and during the life of 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 this works:
> <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
(v8.3.4#803005)
