[
https://issues.apache.org/jira/browse/ARTEMIS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Przygódzki updated ARTEMIS-1648:
--------------------------------------
Summary: Messages from 1.x clients to 2.x cluster are lost when the are
load balanced to nodes with matching consumers (was: Messages from 1.x clients
are lost when the are load balanced to nodes in the 2.x cluster with matching
consumers)
> Messages from 1.x clients to 2.x cluster are lost when the are load balanced
> to nodes with matching consumers
> -------------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1648
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1648
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.3.0
> Reporter: Jarek Przygódzki
> Priority: Major
>
> When a message from 1.x client is transfered to node in the cluster with
> matching consumers (message-load-balancing=ON_DEMAND), it's moved to
> appropriate replication queue, forwarded to target node and then subsequently
> dropped because there aren't any matching bindings for message address.
> This is because if the original message is sent to address with the jms.queue
> prefix (1.x clients), than the message sent by ClusterConnectionBridge also
> has the prefixed destination address and this situation is not supported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
