This is the exact point of a messaging broker. That you hand control of the
message to it decoupling the producers from the consumers. As such you will get
an ack on the producer as soon as the broker receives the message and has met
the persistence and replication requirements that you configur
In 2.7.0 the feature called auto-delete is being added. This is configurable at
the address-setting level to default apply to all queues on the address and
able to be applied at the queue level for finer control.
This is alread in master and in the docs their should you want to read and see
Have you taken a look at the ActiveMQ Artemis documentation [1] on this
subject?
Justin
[1] https://activemq.apache.org/artemis/docs/latest/using-jms.html (scroll
down to the "JNDI" section)
On Tue, Mar 12, 2019 at 9:42 PM Peter Chandler wrote:
> Trying to configure log4j2 JMS Appender for ac
Trying to configure log4j2 JMS Appender for activemq-artemis which uses JNDI
for the connection factory and destinations.
Questions
1. How do I populate activemq-artemis's JNDI Service with the required
Objects?
2. What names do I use in the Log4j2.xml?
factoryName*="org.apache.activem
There's a feature being added for that in 2.7.0. I'm on an iphone now
and I can't do much research on it. but there's an option being added.
On Tue, Mar 12, 2019 at 6:48 PM artemisn00b wrote:
>
> Is there any configuration that Artemis directly handles a case of a durable
> subscriber being remov
Is there any configuration that Artemis directly handles a case of a durable
subscriber being removed, if offline for X minutes or so?
Thanks!
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Suppose I have a symmetric cluster of 3 artemis servers. I send a message to
server 1, and it forwards it to other servers who have consumers. Now, when
exactly does the producer get an ACK?
I have a couple of scenarios where I wouldn't be able to figure out how it
works -
A) Server 1 forwarded a
