On Nov 10, 2012, at 8:46 PM, Mohit Anchlia wrote:
Is it ok if I give hostname to itself in network of connectors? It's easy
to maintain the config that ways.
Not sure what exactly you mean by this. In a network connector configuration
you need to supply the address of another broker
Hello Mohit,
How does your network connector configuration look like?
In general you can use duplex=true.
There is generally no need to define a network connector with duplex=true on
both broker ends. With duplex=true one network connector definition between the
two brokers is enough.
It looks something like
static(tcp://host1:61616,tcp://host2:61616,tcp://host3:61616) On all the
hosts it's the same config. The problem either I can keep duplex or not
since I am using multiple hosts.
On Mon, Nov 12, 2012 at 12:26 AM, Torsten Mielke tors...@fusesource.comwrote:
Hello Mohit,
Thanks I realized that and removed it in my configs
On Mon, Nov 12, 2012 at 12:24 AM, Torsten Mielke tors...@fusesource.comwrote:
On Nov 10, 2012, at 8:46 PM, Mohit Anchlia wrote:
Is it ok if I give hostname to itself in network of connectors? It's easy
to maintain the config that ways.
Not yet, haven't had time. Will try to get to it tonight or tomorrow night.
I'll keep you updated...
On Wed, Nov 7, 2012 at 2:26 PM, jmls julian+activ...@dotr.com wrote:
hey, thanks for the interest. Did you have any luck in getting this to
work ?
--
View this message in context:
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
Hi,
Does anyone have a sample on how to set the redelivery policy in spring
DSL? The pooled connection factory only takes a delivery policy (not a
delivery policy map) and I got an exception saying destination is not set
when I set the ref to a RedeliveryPolicy object. According to this doc
11 matches
Mail list logo
