I see, so message ID is not really meant to be used as identifier by client
apps.
We will try setting JMSCorellationId on sender, if thats not gonna work
will probably redefine request-response mapper
Thank you all for clarification!
чт, 3 окт. 2024 г. в 18:47, Robbie Gemmell :
> Given the mentio
Given the mentions of JMS and AMQP I would presume that
qpid-jms-client is being used. It will populate the JMSMessageID
header itself during send (unless configured not to) as per the JMS
requirements the field is set by provider-on-send.
Message.setJMSMessageID() (and most other header setters li
If the sender is invoking Message.setJMSCorrelationID(String) [1] that
should be mapped onto the STOMP message using "correlation-id" (and vice
versa). Again, using message ID is not recommended. You should be using
correlation ID as that is what it was designed for.
Justin
[1]
https://docs.orac
As far as i know library that sender team uses automatically maps request
with response, they just need to set up response handler class.
Setting own unique id and mapping request with response would require
reimplementing library classes, not really sure if that's an ideal approach
чт, 3 окт. 202
On 10/3/24 11:04, Мурад Байгильдин wrote:
Hi, Justin!
Sender sends message into request queue and expects response message in
response queue, with response's JMSCorellationId header being set to
message ID that was sent (and could not be read by responder app).
Sender (java app) originally was no
Hi, Justin!
Sender sends message into request queue and expects response message in
response queue, with response's JMSCorellationId header being set to
message ID that was sent (and could not be read by responder app).
Sender (java app) originally was not explicitly specifying message ID, not
real
Can you clarify your use-case and how the message ID is being set on the
client sending the message?
Typically the message ID is set by the client implementation or by the
broker and it can also change in some circumstances so it's not
particularly meaningful to the messaging application. Generall
Hi, we ran into an issue when receiving messages via STOMP protocol.
Message was sent by java application using JMSSerializer via AMQP protocol,
resulting in message id being stored in userID message property. When
receiving this message via STOMP, the value of userID was not present in
any header,
