activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johan Stenberg (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1578) Cannot use "user-id" property in AMQP message selector
Date Mon, 08 Jan 2018 17:06:00 GMT


Johan Stenberg commented on ARTEMIS-1578:

Thanks for your response Timothy. So, when a plain AMQP client tries to perform message selection
it has to use a JMS-style filter which requires it to specify JMS specific identifiers such
as "JMSXUserID" instead of AMQP property "user-id". If that is seen as "works as designed"
it might be helpful to have a small section about message filtering at
describing the intended behaviour.

> Cannot use "user-id" property in AMQP message selector
> ------------------------------------------------------
>                 Key: ARTEMIS-1578
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 2.4.0
>            Reporter: Johan Stenberg
>            Priority: Minor
>         Attachments:, pom.xml
> It is not possible to use the "user-id" property specified in
for message selection in a subscription. Instead one has to use the JMS specific "JMSXUserID"
property name.
> This could be maybe fixed by changing the line
> {code:java}
> } else if (key.equals(MessageUtil.JMSXUSERID) || key.equals("user-id") {
> {code}
> but is also prevented by the org.apache.activemq.artemis.selector.impl.SelectorParser
which interprets "user-id" as an arethmetic operations.
> It is also not possible to use the "userId" property instead - which is used as key in
the HashMap [AMQPMessage#_properties|]
- because [AMQPMessage#getObjectProperty|]
only resolves values from the [application properties|]
of an AMQP message.

This message was sent by Atlassian JIRA

View raw message