Re: Producer failover behaviour

2019-09-16 Thread ahuhatwork
It seems that using "reconnectAttempts=-1" or using "reconnectAttempts=500" both work. In other words, it looks like setting it at reconnectAttempts=6 (along with the other connection parameters I have) wasn't sufficient time for failover and failback. -- Sent from: http://activemq.2283324.n4.na

Re: Producer failover behaviour

2019-09-16 Thread yw yw
Can you try the url "tcp://artemis:61616?ha=true&reconnectAttempts=-1"? Here -1 means infinite retry. Default reconnect attempts is DEFAULT_RECONNECT_ATTEMPTS=0. ahuhatwork 于2019年9月13日周五 下午11:23写道: > Oh, that's unfortunate. I used the "< raw >" tag using nabble. > > Here is the artemis (2.9) cl

Re: Producer failover behaviour

2019-09-13 Thread ahuhatwork
Oh, that's unfortunate. I used the "< raw >" tag using nabble. Here is the artemis (2.9) client code snippet (hopefully this works): public class SampleProducer { public static void main(String[] args) throws JMSException, InterruptedException { String brokerUrl = "tcp://artemis:6161

Re: Producer failover behaviour

2019-09-12 Thread Justin Bertram
None of your code snippets or exception messages came through so it's impossible to provide any ideas at this point. Justin On Thu, Sep 12, 2019 at 4:09 PM ahuhatwork wrote: > In my setup, I have a one master and one slave. I have a sample app: > > > > Steps > 1. Start up the above app > 2. Ki