On 22 March 2018 at 18:59, Robbie Gemmell <[email protected]> wrote: > I'd guess that the brokers message conversion is taking the sent AMQP > 1.0 message, finding it has a string message-id, and processing it > such that it ends up with a UUID in the converted AMQP 0-10 message > metadata. That in itself isnt an issue, but if thats happening the > broker would also need to ensure 0-10 consumers had processed the ID > similarly when any selection is being performed for them. >
Possible. I wasn't completely certain from Bryan's description if it was relying of the Broker's message conversion feature. Some producer and consumer code would take the guess work away. > Robbie > > On 22 March 2018 at 18:48, Keith W <[email protected]> wrote: >> Bryan, >> >> That seems surprising. I am not aware of any such problem. Do you >> have an executable example that demonstrates the problem? >> >> cheers, Keith. >> >> On 22 March 2018 at 17:55, Bryan Dixon <[email protected]> wrote: >>> We are using Qpid JMS 0.30.0 to publish messages to a Broker-J 7.0.2 broker. >>> We have some java apps that have to use the older JMS AMQP 0-x 6.3.0 client >>> and others that can use the newer JMS 0.30.0 client. I just found that when >>> using the JMS Message.getJMSMessageID() method call for the same message >>> results in 2 different messages Ids being returned by each client version. >>> That by itself I guess is OK but not what I would expect. The bigger issue >>> I just noticed with the older JMS AMQP 0-x 6.3.0 client is when I get the >>> JMSMessageID value, I can't use that value returned in a message selector to >>> retrieve (either consume or browse) that message - the message is not found. >>> >>> Here is an example. I published a message and the JMS JMS 0.30.0 client >>> returns the following value from the Message.getJMSMessageID() call: >>> ID:eventapp-40500566-2ca4-439e-9a2d-4e00c88ea682:9:1:1-1 >>> >>> However when using the JMS AMQP 0-x 6.3.0 client Message.getJMSMessageID() >>> call on the same exact message call the following ID is returned: >>> ID:fcae0a4b-9810-3214-b161-8572e5df8ea6 >>> >>> When I use the QueueBrowser class with the JMS AMQP 0-x 6.3.0 client to >>> browse the message using this message selector the message is not returned >>> by the browse() method: >>> JMSMessageID ='ID:fcae0a4b-9810-3214-b161-8572e5df8ea6' >>> >>> It doesn't seem right that the 6.3.0 client can't retrieve the message by >>> the JMSMessageID it returned. >>> >>> I need a way to be able to retrieve a message by its ID for the 6.3.0 >>> client. This does work successfully wit the JMS 0.30.0 client. >>> >>> Bryan >>> >>> >>> >>> >>> >>> >>> >>> -- >>> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
