[ARTEMIS-1648] Messages from 1.x clients to 2.x cluster are lost when they are load balanced to nodes with matching consumers

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.3.0
• Component/s: Broker
• Assignee: Unassigned
• Reporter: Jarek Przygódzki
• Created: 31/Jan/18 21:33
• Updated: 18/Feb/18 22:42
• Resolved: 18/Feb/18 22:42

Description

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.