Documentation is kind of unclear about this:
"Make sure your consumers are distributed evenly across the different nodes
/if possible/. This is only an issue if you are creating and closing
consumers regularly. Since messages are always routed to the same queue once
pinned, removing a consumer from
I am trying to trace the lifetime of a message in the client application log.
That is in my application's onMessage(Message p_message) method I have
different log statements which
get printed under the thread ID: "ActiveMQ Session Task".
Like below:
[INFO ] 2018-11-27 16:29:57,642 [ActiveMQ Sess
I cant remember if FQQN is supported on openwire. If it is.
You could you use a JMSqueue with a FQQN to bind to the topic subscription you
want to share
Sent from my Samsung Galaxy smartphone.
Original message From: Timothy Bish
Date: 03/12/2018 15:53 (GMT+00:00) To: users@a
NMS API does not offer support for this and there aren't any plans to
add it. The OpenWire protocol doesn't offer the features needed to
implement shared subscriptions so it isn't easily added there. You
could trying switch to an AMQP based .NET client like AmqpNetLite and
work from there.
Hi,
We use Apache NMS library for consuming the broker (from .Net). We would
like to scale out consumers by subscribing to the same topic, but the
consumers acting as competing consumers, so that only one of them processes
any message. ActiveMQ artemis supports multiple clients to a multicast queu
Hi,
Currently we are performing Artemis crash testing before we switch
completely to it from ActiveMQ. We've applied following scenario:
- Artemis broker 2.6.3 with heap size of 2Gb, global-max-size of 400Mb, and
global address-setting to apply DROP policy whenever memory exceeds 150Mb
(max-size-b
