element name is: networkBridgeFilterFactory, value
conditionalNetworkBridgeFilterFactory
On 12 November 2012 21:23, jiunjiunma jiunjiu...@gmail.com wrote:
I am using JMS connection pool and concurrent consumers (with the
randomize=true setting in failover uri). I am not sure if it will cause
I had a small test case that cleans up the ActiveMQ DLQ. It works fine when I
am running a single broker. When I ran a network of brokers (2 static
brokers using per queue based DLQ setting), I noticed the client code (with
Can you post your network connector configuration?
On Mon, Nov 12, 2012 at 11:21 AM, jiunjiunma jiunjiu...@gmail.com wrote:
I had a small test case that cleans up the ActiveMQ DLQ. It works fine
when I
am running a single broker. When I ran a network of brokers (2 static
brokers using per
Sure. I am using the sample configurations bundled with activemq 5.7. They
are the same as activemq-static-network-broker1.xml and
activemq-static-network-broker2.xml. I commented out the deadLetterStrategy
section but they behave the same whether it's per queue DLQ or in shared DLQ
setting.
the dlq should behave like any other queue w.r.t a network.
One thing to note however, it that a message will only be bridged
once, so if a message is forwarded from A-B it won't by default get
forwarded back from B-A.
I wonder if that is is occurring in your scenario. It could be if your
I am using JMS connection pool and concurrent consumers (with the
randomize=true setting in failover uri). I am not sure if it will cause the
consumer bounces between brokers scenario you described. If so, does that
means my other messages may also be stuck on a broker?
I tried to use the
