Re: "queuePrefetch" policy doesn't seem to be working properly

Thanks for the quick response. I am using ActiveMQ 5.15.10 and we are connecting to activemq using MuleSoft which is running on 3.9.0 runtime version. I have set the queue prefetch at the connection level (not at the broker) like below. tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=1 I

Re: "queuePrefetch" policy doesn't seem to be working properly

Hi, I guess it’s the same as https://issues.apache.org/jira/browse/AMQ-7418 right ? I was about to add a comment in the Jira. I would need the version from both broker and client. Do you have prefetch defined on broker side ? Anyway, the scenar

"queuePrefetch" policy doesn't seem to be working properly

Hi, We are using ActiveMQ and MuleSoft in our project. We connect to ActiveMQ from MuleSoft. As per the project requirement, we are using JMXGroupId and Queueprefetch polcy. We have set Queueprefetch to 1 at the connection broker url like below and number of consumers are set to 2 tcp://localh

Re: Federation using Bi-Directional/Duplex between Artemis brokers

I am coming from a 5.x background as well with heavy usage of duplex network connectors for the same reason as you (such as firewall configurations) so I definitely understand it being a deal breaker. I'm not sure when I will get time to work on it more but I'm hoping to soon as it will make Feder

Re: Federation using Bi-Directional/Duplex between Artemis brokers

Thanks Chris, Currently we are using ActiveMQ5.x and planning to switch to Artemis to leverage its benefits but it appears Duplex feature is a deal breaker for now to make this switch. Even it is required two connections to federate, if they initiated by one broker then it would have solved our

Re: Federation using Bi-Directional/Duplex between Artemis brokers

There is currently no duplex option but it is on the list of things in the future. Originally there was only upstream connections but I recently added downstream configuration but it still requires creating a connection in each direction. The main issue is there is no current support for duplex co

Re: Failover for remote client connecting to cluster (no HA)

I was just suggesting to check your cluster configuration against the reference examples, to make sure the nodes are actually working as a group. Could it be something as simple as the "ha" URI parameter being case-sensitive? In all the examples it's in lower case, not uppercase as you have it.

Re: Failover for remote client connecting to cluster (no HA)

I don't think initial server discovery is the problem. Event if more servers are expliclitly listed the client never switches from the server it initially successfully connected to. var cf = new ActiveMQConnectionFactory( "(tcp://wildfly-01.domain:8080,tcp://wildfly-02.domain:8

Re: Failover for remote client connecting to cluster (no HA)

Hi Have you checked out the various examples for discovery here - https://github.com/apache/activemq-artemis/tree/master/examples/features/clustered ? Dave On Thu, Feb 27, 2020 at 8:18 AM Jarek Przygódzki wrote: > Hi, > I've been experimenting with Artemis cluster. Apparently remote clien

Failover for remote client connecting to cluster (no HA)

Hi, I've been experimenting with Artemis cluster. Apparently remote client (that is, one connecting from outside of the cluster) never switches to different node if a node goes down after initial connection is established. What I would like to happen is that when client connects to any node in a