Re: Bridging Artemis with classic

Hi Kunal, What kind of workload is your broker cluster designed for? I don't think there is an easy answer here as these two brokers have different sets of features implemented. It really depends on your requirements on supported features and performance. For instance, if your application requires

Re: Bridging Artemis with classic

Thanks Justin. I am planning to use Amazon MQ (only supports classic) as a central broker and Artemis as satellite brokers with the assumption that artemis is a more supported product and classic is treated as legacy with regards to development and support. Firstly, Is my assumption correct? We ar

Re: Bridging Artemis with classic

Just to clarify...ActiveMQ Classic doesn't support the Core protocol so that is why you can't use a Core bridge to integrate. Justin On Thu, Oct 3, 2024 at 8:29 AM Justin Bertram wrote: > Yes. You can bridge messages from Artemis to Classic and vice versa. > However, you can't use a Core bridg

Re: [Artemis] Passing message userID into STOMP

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

Re: Camel Route to Bridge 2 ActiveMQ Classic Brokers

> I have a Camel Route that drains all of the queues and topics (excluding Advisory Topics) from the old broker to the new broker. Conceptually speaking, there is no real way to "drain a topic" since topics don't hold messages like a queue does. When dealing with topics, messages are stored in _su

Re: [Artemis] Passing message userID into STOMP

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

Re: [Artemis] Passing message userID into STOMP

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

Re: [Artemis] Passing message userID into STOMP

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

Re: [Artemis] Passing message userID into STOMP

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

Re: [Artemis] Passing message userID into STOMP

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

Camel Route to Bridge 2 ActiveMQ Classic Brokers

Good morning, I am using ActiveMQ Classic 5.18.5 on 2 separate brokers on Windows (unfortunately). One broker is using the default kahaDB, and the other broker has been configured with database persistence using Microsoft SQL Server. I am migrating messages from the old broker using kahaDB to

Re: [Artemis] Passing message userID into STOMP

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

Re: Bridging Artemis with classic

Yes. You can bridge messages from Artemis to Classic and vice versa. However, you can't use a Core bridge to do it. Core bridges, as the name suggests, use the Core protocol. A Core bridge can't use the AMQP protocol. I recommend Camel since it's mature, powerful, and ubiquitous. You can set up Ca

Bridging Artemis with classic

Hi, Is it possible to bridge artemis with classic broker? I am trying with AMQP protocol. I am getting this error p1broker-1 | 2024-10-03 07:34:50,270 WARN [org.apache.activemq.artemis.core.server] AMQ224091: Bridge BridgeImpl@6a3012f8 [name=amqp-bridge, queue=QueueImpl[name=p1broker.out,

[Artemis] Passing message userID into STOMP

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,