ConnectionError after failover when credit_window=0

I came across a different issue and when I started investigate it I run into the following scenario (Hopefully the same solution will solve both problems and if not I’ll open another one):

I defined two brokers (master & slave). I connected to the master and open a receiver with credit_window=0. Then, closed the master and not long after I saw that I’m now connected again as expected. The problem was that about a minute after I got ConnectionError: local-idle-timeout expired and the application was closed… I saw in the broker logs that the InactivityIOException came form there but It didn’t happened when I didn’t set credit_window=0 so I guess it’s related.

[Gadi-Manor]

I’m using Apache ActiveMQ. I think I found the problem. I thought that if I set credit_window=0 followed by add_credit(1) then that credit will still be there even after the master/slave switch but in fact it’s 0. The strange thing is that when the credit is 0 there is an InactivityIOException after the switch. The exception isn’t thrown on the original broker even when there is no credit.

My solution to the problem is adding the credit inside the receiver_open event.

[dbit-xia]

Thank you, I verified it.