As Tim said the client is operating in the manner JMS mandates, whereby msg.setJMSMessageID(..) isnt for use by applications but rather by JMS clients, and the client sets a message ID upon send(), with the value available after the send call returns, using msg.getJMSMessageID().
There are some URI options to tweak the precise ID behaviour as Tim touched on, which can also be leveraged via code. If you desperate to control the values more explicitly, I'll note this thread: https://lists.apache.org/thread.html/rb15c0d2bbe70e736585c2379a3a1c1af6c935d16d6eef294c5a92f2a%40%3Cusers.qpid.apache.org%3E On Mon, 11 Jan 2021 at 23:24, jxz024000 <zhoujia...@hotmail.com> wrote: > > Hi Tim, > > Thanks for the answer. We do set a correlation id in message header > message.setJMSCorrelationID(some uuid); But the problem is that on Azure > Service Bus server side, the engineers can't use this correlation id to > locate the log related to the message. Azure ServiceBus support person told > me they use message id and enqueued time to find the corresponding log in > the server side. > > Thanks, > Jia > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
