Thanks for the pointer. We will try this solution and start searching for a
performant solution. But that may take some time __
Best Merlin
Am 20.04.23, 22:41 schrieb "Justin Bertram" mailto:jbert...@apache.org>>:
Generally speaking, what you describe with the proxy sounds perfectly
reasonabl
Generally speaking, what you describe with the proxy sounds perfectly
reasonable if you were working with an HTTP based service. However, the
messaging protocols supported by ActiveMQ Artemis (i.e. core, AMQP, STOMP,
MQTT, & OpenWire) all use bare TCP, and they are stateful. HTTP is a layer
on top
Hi Justin,
thanks for your reply. I know it is TCO and the answer maybe no, that never
will work. And I am afraid your next message will be exactly this. But anyway.
To clarify: I borrowed "context" from the JavaEE configuration jargon where
context refers to the URL path under which deployment i
I'm not aware of any way to specify a "context" on the client's connection
URL. Furthermore, I don't how the broker would be configured to handle the
context and provide different behavior between different contexts.
Can you clarify your use-case here? Why exactly do you want/need to use a
"contex
Hi ActiveMQ Users,
we use an ActiveMQ deployed on JBoss 7.4 as Messaging Broker for JMS Messages.
We have a requirement that the ActiveMQ is reachable under a Context, let’s say
‘jms’ so for example “tcp://localhost:8080/jms”.
We use org.apache.activemq:artemis-jms-client:2.19.1 to connect our Ja
