No communication after recovery about lyra

[michaelklishin]

I don't know about Lyra but RabbitMQ Java client does not guarantee publisher recovery: it will recover channels, topology, consumers but any concurrent publishes or other actions from applications will fail and may interfere with recovery process (cause channel exceptions as in the protocol). Clients cannot handle every possible scenario like that so developers need to make sure their applications can handle down connections and channel exceptions.

[neuhaus]

Well I switched from the normal RabbitMQ java client to Lyra to use the high availability features. It's Lyra's raison d'être.

I don't see any exceptions getting thrown. From the log it appears as if everything is recovering, however it's not working after the recovery so i guess there's a bug.

[michaelklishin]

There is a channel exception logged but it's impossible to tell why: only RabbitMQ logs can clarify this. There are scenarios in which neither Lyra nor automatic connection recovery in the Java client can avoid channel exceptions (the topology might have changed since connection termination, e.g. by other apps).

Without a way to reproduce there is no evidence that this is not one of those cases and it's an issue in Lyra.

[neuhaus]

Thanks for getting back to me. We have decided to migrate this project away form Lyra do the the problems with recovery so i will no longer be able to assist with this issue.