[jira] [Updated] (ARTEMIS-2337) federated queues not working correctly with wildcards or defaults
[ 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: > include-federated="false"> > > > The following config works as expected with the client receiving message > prior to and during the life of client connection: > include-federated="false"> > > > also noticed that the following causes the issue too: > include-federated="false"> > > > > but this works: > include-federated="false"> > > > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2337) federated queues not working correctly with wildcards or defaults
[ https://issues.apache.org/jira/browse/ARTEMIS-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Wood updated ARTEMIS-2337: - Description: 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: The following config works as expected with the client receiving message prior to and during the life of client connection: also noticed that the following causes the issue too: but this works: was: 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 the client reconnects. It seems that the issue is related to wildcards: The following config works as expected with the client receiving message prior to and during the life of client connection: also noticed that the following causes the issue too: but this works: > 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: Critical > > 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: > include-federated="false"> > > > The following config works as expected with the client receiving message > prior to and during the life of client connection: > include-federated="false"> > > > also noticed that the following causes the issue too: > include-federated="false"> > > > > but this works: > include-federated="false"> > > > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARTEMIS-2337) federated queues not working correctly with wildcards or defaults
[ https://issues.apache.org/jira/browse/ARTEMIS-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Wood updated ARTEMIS-2337: - Description: 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 the client reconnects. It seems that the issue is related to wildcards: The following config works as expected with the client receiving message prior to and during the life of client connection: also noticed that the following causes the issue too: but this works: was: 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 the client reconnects. It seems that the issue is related to wildcards: The following config works as expected with the client receiving message prior to and during the life of client connection: also noticed that the following causes the issue too: but not: > 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: Critical > > 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 the client reconnects. > It seems that the issue is related to wildcards: > include-federated="false"> > > > The following config works as expected with the client receiving message > prior to and during the life of client connection: > include-federated="false"> > > > also noticed that the following causes the issue too: > include-federated="false"> > > > > but this works: > include-federated="false"> > > > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARTEMIS-2337) federated queues not working correctly with wildcards or defaults
[ https://issues.apache.org/jira/browse/ARTEMIS-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Wood updated ARTEMIS-2337: - Description: 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 the client reconnects. It seems that the issue is related to wildcards: The following config works as expected with the client receiving message prior to and during the life of client connection: also noticed that the following causes the issue too: but not: was: 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: The following config works as expected with the client receiving message prior and during the client connection. also noticed that the following causes the issue too: but not: > 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: Critical > > 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 the client reconnects. > It seems that the issue is related to wildcards: > include-federated="false"> > > > The following config works as expected with the client receiving message > prior to and during the life of client connection: > include-federated="false"> > > > also noticed that the following causes the issue too: > include-federated="false"> > > > > but not: > include-federated="false"> > > > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
