[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-8139: ----------------------------- Attachment: 0002-QPID-8139-Broker-J-AMQP-1.0-Support-different-messag.patch > [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-Support-different-messag.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 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org