If you're going to be using message grouping in a cluster then you'll
definitely want to configure it properly (i.e. according to the
documentation you cited). That said, message grouping imposes a natural
penalty on performance due to the serialization of message consumption per
group. Generally s
> Is there any wait to max the number of "in delivery" message, because it
seems if I have at least one consumer connected there is no wait to make
use of LVQ.
If the consumer is connected then the broker will dispatch messages to it.
There is no way to force the broker to wait for an arbitrary am
After reading the documentation in more detail
"https://activemq.apache.org/components/artemis/documentation/latest/message-grouping.html";
it seems that I need to use "Clustered Grouping" for this use case.
I will try that
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341
Hi,
I am trying to use message group and I think I am facing an issue, but I
would like to confirm before trying to fix it.
Scenario:
Artemis 2.9.0 Cluster (2 Nodes)
Queue: State (LVQ: true, Durable: Yes)
Consumer 1 --> Broker 1
Consumer 2 --> Broker 2
Producer Send Message to Broker 1: Messa
Thanks for your answer, I got your point regarding "in delivery" messages.
Is there any wait to max the number of "in delivery" message, because it
seems if I have at least one consumer connected there is no wait to make use
of LVQ.
I tried to configure "jms.prefetchPolicy.all=1" to test but it w
Hello,
I would send logs from artemis instance to central Graylog. Other
Jboss/wildfly instances can send server logs via logstash-gelf library. I
was trying configure Artemis it by same way - via logging.properties + copy
jar file into classpath, but it does not work.
Could you share, if anybody
Also, I discovered this warning in the startup of JBoss.
15:47:36,686 WARN [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC
service thread 1-7) IJ020016: Missing element. XA recovery disabled
for: java:/activemq/ConnectionFactory
I even get that when I explicitly add to the
connection-
Maybe some more information;
Here's a recent local logging
14:37:17,865 DEBUG [org.apache.activemq.transport.failover.FailoverTransport]
(Periodic Recovery) Stopped tcp://localhost:61616
14:37:17,866 DEBUG [org.apache.activemq.transport.failover.FailoverTransport]
(Periodic Recovery) Reconnect
