-
Bug
-
Resolution: Done
-
Major
-
7.2.2.GA
-
-
-
-
-
-
+
-
https://github.com/rh-messaging/activemq-artemis/pull/256, https://code.engineering.redhat.com/gerrit/gitweb?p=messaging/activemq-artemis.git;a=commit;h=5780a00a929b88616fe73291d5322c0afde0e1f6, https://code.engineering.redhat.com/gerrit/gitweb?p=messaging/activemq-artemis.git;a=commit;h=2ee4a6f32a978fe4ab9971dc6d4cc18c736c18a8
When using JMSMessageID as a selector HornetQ client converts the header to HQUserID and Artemis is expecting headers to be AMQUserID
The broker should detect a legacy HornetQ client and adjust the incoming selector.
- clones
-
ENTMQBR-2624 HornetQ client issue while using JMSMessageID as selector
- Closed
- is incorporated by
-
JBEAP-17062 [GSS](7.2.z) Upgrade Artemis from 2.7.0.redhat-00057 to 2.9.0.redhat-00005
- Closed
- links to