[jira] [Commented] (ARTEMIS-3916) Fix OpenWire selector with JMSMessageID

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574247#comment-17574247 ] 

ASF subversion and git services commented on ARTEMIS-3916:
----------------------------------------------------------

Commit dd61a651b1f5892c6dc3b75923f1f7f08914fe9b in activemq-artemis's branch refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=dd61a651b1 ]

ARTEMIS-3916 fix OpenWire selector with JMSMessageID

The OpenWire JMS client shipped with ActiveMQ "Classic" uses the
client's hostname as part of the `JMSMessageID`. Consumers may use this
data to select messages sent from particular hosts. Although this is
brittle and not recommended it is nonetheless possible.

However, when messages arrive to ActiveMQ Artemis they are converted
to core messages, and the broker doesn't properly map the selector from
`JMSMessageID` to the corresponding property on the underlying core
message. This commit fixes that problem. Changes include:

 - Mapping selector from JMSMessageID to the internal __HDR_MESSAGE_ID
 - Relocating some constant values so that both the protocol and commons
   module can use them
 - Adding a test


> Fix OpenWire selector with JMSMessageID
> ---------------------------------------
>
>                 Key: ARTEMIS-3916
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3916
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)