tbain98 wrote
In your broker-to-broker networkConnectors, are you using maxReconnects=0
as an argument to the failover URI? It wouldn't explain why amq4 got
demoted, but it could explain why messages aren't transferring to amq5
instead.
Here is the definition of my networkConnectors inside
Quick update...
I re-ran my tests as suggested.
First my producer connected to amq4 and the consumer to amq1. That setup
worked quite well without any error or timeout.
Then I re-configured it again with messages being sent to amq1 and consumed
from amq4. To my surprise it worked this time (I
that property is only set in the ActiveMQMessageConsumer, when onMessage
throws an exception.
The value is then set as the poisonCause of a message ack.
In camel, the broker dlq processing is bypassed b/c the exceptions are
trapped by spring.
peek at
HI,
we are using ActiveMQ 5.10 and configured the Mirrored Queues. Enabling
mirroring, creates virtual topic for all the queues, but a given point of
time, i am interested in capturing messages for 1 or 2 Queues and that too
for all times of broker. My questions.
- is they any where we can
masterslave: is an alias for failover: with maxReconnects=0. (There might
be another URI option included in the alias, I don't remember; I think the
details are in the JIRA where Gary added the failover transport, if you're
curious.) So there's no need to try using failover explicitly, since the
1.For the dead letter queue ActiveMQ.DLQ, I would like to configure a policy
whereby messages in DLQ get deleted after they have resided in DLQ for 5
days.
I couldnt see how to do it in the documentation.
My current activemq.xml configuration file is below...how do I modify it for
autoexpiring my
2. That plugin will cause messages to be discarded immediately instead of
going to the DLQ. There's 5-day timeout like you're looking for, they just
go straight into the bit bucket.
On Fri, Oct 17, 2014 at 11:17 AM, gchakra gopal.chakravar...@fox.com
wrote:
1.For the dead letter queue
you really need an enhancement of your own plugin that will implement
sendToDeadLetterQueue b/c the current impl will clear the expiration of the
message, so it is in theory not possible for a message sent to the DLQ, to
expire.
the main meat is in:
https://github.com/apache/activemq/blob/d54e0d6ab590b6a6148a5e2629c45b95d3f40eb8/activemq-broker/src/main/java/org/apache/activemq/plugin/DiscardingDLQBroker.java#L47
maybe an option in there will give you a quick win, do what regionBroker
does but set an expiration.
On 17
ok.. that’s reasonable. Thanks for the reply.. I think what I’ll do is
have some basic sanity assertions run periodically.
On Wed, Oct 15, 2014 at 12:51 AM, Gary Tully gary.tu...@gmail.com wrote:
It will depend on the queue depth b/c it is a linear search to find a
match. But all messages
Those plugin modifications will get the message into the DLQ with an
expiration date, but is there anything that will cause messages in the DLQ
to be deleted when they expire? Or will Gopal also need to implement
something to do that?
On Fri, Oct 17, 2014 at 2:28 PM, Gary Tully
11 matches
Mail list logo
