Thank you, excellent!!
I apoligise for the doublepost and for not finding this myself.
Thanks again.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
So the broker plugin does return the data that i need. However, the
beforeDeliver and afterDeliver methods are firing when a JMS subscription by
a client is made and not when the message is consumed by a JMS client. I
have verified this, I believe, by
1. Subscribing the the topic with a JMS clien
About:
But then my policies for setting ABC.Q.ABCINT.DLQ as DLQ of ABC.Q.ABCINT.>
stopped working, discarding plugin overrides them.
After debugging I found that discarding plugin has dropAll behavior always
on, so without explicitly setting dropAll to false i.e.:
it works as if drop all was ena
AMQ 5.15.3
We have configured AMQ with two brokers clustering via static uri's
---
BrokerA config
---
...
...
...
--
BrokerB config
--
...
...
...
Generally this works great, but there are an edgecase whi
See the Stuck Messages section of
http://activemq.apache.org/networks-of-brokers.html for an explanation of
the problem and its solution.
Tim
On Wed, Apr 25, 2018, 12:15 AM Dolk wrote:
> AMQ 5.15.3
>
> We have configured AMQ with two brokers clustering via static uri's
> ---
> Broke
