qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-8139) [Broker-J] Selector containing JMSMessageID expressions might not find the message when expression JMSMessageID value starts with 'ID:' prefix but the real message id does not include the prefix
Date Mon, 07 May 2018 13:37:00 GMT

     [ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Keith Wall updated QPID-8139:
-----------------------------
    Description: 
JMS specification requires JMSMessageID value to start with prefix "ID:". The JMS client might
add the prefix "ID:" to the values not starting from "ID:" in order to be JMS compliant. If
the altered JMSMessageID value is used to build a selector expression like "JMSMEssageID='ID:<real
id>'", the target message might not be found as Broker-J uses real message ids in message
lookup.

Potentially, filtering functionality for JMSMEssageID expression can be enhanced to detect
the cases when the "ID:" prefix is specified in the selector but not included into the real
message id value and find the correct message.  

  was:
JMS specification requires JMSMessageID value to start with prefix "ID:". The JMS client might
add the prefix "ID:" to the values not starting from "ID:" in order to be JMS compliment.
If the altered JMSMessageID value is used to build a selector expression like "JMSMEssageID='ID:<real
id>'", the target message might not be found as Broker-J uses real message ids in message
lookup.

Potentially, filtering functionality for JMSMEssageID expression can be enhanced to detect
the cases when the "ID:" prefix is specified in the selector but not included into the real
message id value and find the correct message.  


> [Broker-J] Selector containing JMSMessageID expressions might not find the message when
expression JMSMessageID value starts with 'ID:' prefix but the real message id does not include
the prefix
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-8139
>                 URL: https://issues.apache.org/jira/browse/QPID-8139
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-7.0.2
>            Reporter: Alex Rudyy
>            Assignee: Alex Rudyy
>            Priority: Major
>         Attachments: 0001-QPID-8139-Broker-J-AMQP-1.0-Make-sure-that-selector-.patch,
0002-QPID-8139-Broker-J-AMQP-1.0-Summport-all-message-for.patch
>
>
> JMS specification requires JMSMessageID value to start with prefix "ID:". The JMS client
might add the prefix "ID:" to the values not starting from "ID:" in order to be JMS compliant.
If the altered JMSMessageID value is used to build a selector expression like "JMSMEssageID='ID:<real
id>'", the target message might not be found as Broker-J uses real message ids in message
lookup.
> Potentially, filtering functionality for JMSMEssageID expression can be enhanced to detect
the cases when the "ID:" prefix is specified in the selector but not included into the real
message id value and find the correct message.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message