Win a copy of The Way of the Web Tester: A Beginner's Guide to Automating Tests this week in the Testing forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JMSMessageID preserved during Pub/Sub

T.Rob Wyatt
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Using IBM MQ when I publish a message and then get it with a subscriber, the JMSMessageID returned from the publish and the subscribe are different. I would have expected them to be the same because otherwise how could Request/Reply work? I posted to Stack Overflow and Nigel Deakin the JMS Spec Lead confirmed that the intent is that the subscriber(s) should see the same JMSMessageID as the publisher got back from the send. IBM replied that the spec supports their interpretation in which the JMSMessageID changes, but they will consider requests to change the behavior.


With that in mind, I was wondering...

What behavior would *you* expect in this situation? Would you be surprised if your transport provider changed the JMSMessageID across a Publish API call?

What behavior do other transport providers exhibit? If you log the JMSMessageID as seen by a publisher and a subscriber in [Tibco | ActiveMQ | RabbitMQ | WAS | ...] do you get the same value?

I need to provide use cases to justify my enhancement request. Is this a feature you rely on using some other transport? If yes, what kind of use cases do you have?

I'm pretty sure I will be able to get IBM to make the change with what I have so far but some of these questions potentially upgrade the ammunition I have to use. It isn't often you get to club IBM over the head with their own mistake and force them to change so if you want to be a big part in a very tiny piece of history, please respond.

-- T.Rob
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic