[ARTEMIS-2409] HornetQ client vs Artemis broker compatibility: issue while using JMSMessageID as selector

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.0
• Fix Version/s: 2.10.0
• Component/s: Broker
• Assignee: Unassigned
• Reporter: Tomas Hofman
• Created: 03/Jul/19 10:09
• Updated: 26/Aug/19 15:50
• Resolved: 26/Aug/19 15:50

Description

When Hornetq client connects to Artemis broker, and creates consumer with selector containing e.g. JMSMessageID field, selector fails to correctly match messages.

When using JMSMessageID as a selector, HornetQ client converts the header to HQUserID, while Artemis is expecting header AMQUserID.

The broker should detect a legacy HornetQ client and adjust the incoming selector.

String selector = "JMSMessageID = 'ID:06df8801-9719-11e9-9313-972d6542d784'";
// message with above ID exists in the queue

org.hornetq.api.core.client.ClientConsumer hqConsumer = hqSession.createConsumer(queueName, selector, true);
org.hornetq.api.core.client.ClientMessage message = hqConsumer.receive(1000);
assertNotNull(message); // fails

Issue Links

• links to: GitHub Pull Request #2742