Hi,
Our application had a similar issue bridging between brokers on
different networks. We were able to reproduce the problem in a testing
environment by fiddling with iptables to completely sever connectivity
on one broker machine. In our case that made sense because in the wild
the devi
Thanks Marco.
By shutdown do you mean normal shutdown or client/broker getting abruptly
down. If getting abruptly down what could be reason for the same, this will
help in reproducing the same?
We are using 4.1, yet to migrate to 5.1. Since this is critical time in our
project we are not migrati
Hi,
we ave the same problem here. Setting wireformat.maxInactivityDuration=0 was
not a good idea because the shutdown of client or broker (i cant remeber) is
not recognised. So try if your client get notice of broker shutdown and vice
versa.
Which version of activeMQ did you use? With 5.1 the pr
In our application we are using ActiveMQ. Currently we facing
"javax.jms.IllegalStateException: The Session is closed", this exception
occurs immediately after "Channel was inactive for too long". On searching
on this we found an option for disabling the inactive timer, namely
wireformat.maxInacti
