I understand everything you are saying, and I believe I could deal with this
if I had the time. Unfortunately, I don't, so I just coded around it. I
removed the failover transport so send will just error, I created my own
manual reconnect method which bascially creates a whole new producer and
Yes I'm using failover. The problem is that if I don't set the
maxReconnectAttempts, it waits forever when I call send and the connection
is down. But if I set the maxReconnectAttempts, then after it reaches that
max number of attempts, it never connnects again. Shouldn't I be able to
attempt a
OK, I was able to stop it from waiting forever by setting the
maxReconnectAttempts setting. However, it still does not behave as
expected.
Once everything is up and running, I shut down one of the consumers. In the
producer I get this error:
DEBUG - Transport failed with the following exceptio
Hi,
I have two consumers running, and one producer (all written in java). The
producer is sending a message to each consumer with the basic failover
transport. In the producer, I have the persistent setting set to true.
My problem is that if one of the consumer crashes, when the producer goe
I'm very new to ActiveMQ, and this is probably a problem with the way I'm
using it. I do not know how to create a JIRA. It would be hard to create a
test case without the extra processing code included. The test would be as
follows:
1) Run TIPServer.java in 2 locations.
2) Create a new instance
the consumers do have normal url's (see TIPServer.java). But for the sender,
what url do I use to send to multiple consumers?
--
View this message in context:
http://www.nabble.com/Duplicate-Messages-on-Listener-Restart-tp25440673p25452663.html
Sent from the ActiveMQ - User mailing list archive
I used fanout because I need the producer to send the same message to
multiple consumers - but only once to each consumer. How do I do this
without getting duplicates when the consumer restarts? What should the url
be?
--
View this message in context:
http://www.nabble.com/Duplicate-Messages
Unfortunately, my testing with the latest snapshot has the same problem.
I've created my own case for this to see if I get more responses (link
below). I appreciate your help.
http://www.nabble.com/Duplicate-Messages-on-Listener-Restart-td25440673.html
--
View this message in context:
http://
have you resolved this issue? I'm having the same issue. Any help would be
appreciated.
--
View this message in context:
http://www.nabble.com/Duplicate-messages-sent-to-Queue-after-broker-restarts-tp15598179p25440677.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
I have a message client that produces a message and sends to multiple
listeners by using the URL:
fanout:(static:(tcp://host1:61616,tcp://host2:61616,tcp://host3:61616
...))?fanOutQueues=true&minAckCount=1
I'm getting duplicate messages whenever any of the listener is shut down and
restarte
10 matches
Mail list logo
