IIT Software wrote:
Just tested it and you're right. But it concerns "only" the case if you stop the router and don't restart it.
Not only this case. It also concerns the case when I do start the router, but too late (after max-retries are reached).
IIT Software wrote:
When the client reaches max-retries (50), it throws a JMSException on producer.commit but not on the consumer.commit. We will have to check this.
Exactly. In this case the consumer thread gets blocked and cannot be interrupted, which is a fatal problem.
IIT Software wrote:
However, transparent reconnect works. If you stop the router and restart it before your client reaches max-retries, everything continues as expected.
Sure, but the situation when the router does not become available until max-retries are reached must be handled properly, too.
