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 окт. 2024 г. в 18:04, Мурад Байгильдин <baigildi...@gmail.com>:
> 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
> really sure if it was set by library used or by the broker
>
> Calling msg.setJMSMessageId(msgId) with some manually generated value did
> reflect on userID property of the message, however it still could not be
> read by responder app via STOMP, unless
> msg.putStringProperty('some-header-name', msgId) was called
>
> As a solution for now we settled on manually putting message ID into
> string properties
>
> чт, 3 окт. 2024 г. в 17:13, Justin Bertram <jbert...@apache.org>:
>
>> 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. Generally speaking
>> we
>> recommend folks set their own unique ID if they're wanting to track
>> messages.
>>
>>
>> Justin
>>
>> On Thu, Oct 3, 2024 at 2:17 AM Мурад Байгильдин <baigildi...@gmail.com>
>> wrote:
>>
>> > 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, unless the sender app manually generates an id for the
>> message
>> > and passes it into some custom-named header.
>> > Could not find any related info on this property in the archive.
>> > Maybe it is possible to add a STOMP configuration flag, similar to
>> > stompEnableMessageId (stompEnableUserId e.g.), that would control if a
>> > message's userID value is being passed into STOMP headers?
>> >
>> > artemis version 2.37.0
>> >
>>
>
