Consumers not getting messages after broker restart about lyra

[basert]

I was able to reproduce this issue by noticing that after the connection was restored by lyra, two consumers were on my queue. One was with this initial consumer tag, the other was with a new one.

I did some breakpoint debugging on the basicConsume method in com.rabbitmq.client.impl.ChannelN and the method gets called twice after the connection restore. This is due to changed behavior in rabbitmq > 4.0.0 where automatic recovery is enabled by default, resulting in a new consumer from lyra and the recovered by the rabbitmq library.

My solution was to disable this in the connection factory:

val connectionFactory = new com.rabbitmq.client.ConnectionFactory
connectionFactory.setAutomaticRecoveryEnabled(false)
val options = new ConnectionOptions(connectionFactory)

[basert]

added a PR, not sure how to release a new version though, I think that is up to you :)

[EdeMeijer]

Hello,

Just wanted to ping you to check if you maybe have time to get back to me on this :)

Kind regards.

[michaelklishin]

@EdeMeijer I doubt this has anything to do with Lyra. You are not specifying how exactly you are publishing messages but it sounds like a routing problem and not a recovery one. See Message Tracing and how to capture traffic with Wireshark.

Also consider posting questions to rabbitmq-users and providing the entire server log.

[michaelklishin]

Also consider handling exceptions in your consumer's methods. While reasonably recent RabbitMQ Java client versions log unhandled exceptions and provide both forgiving and strict consumer implementations (the strict one closes channel upon an unhandled exception), it is much easier to inspect any possible exceptions if you handle them in your own code.

[neuhaus]

It's disappointing to see the recovery broken for lyra, after all that's the reason that people use it.
@jhalterman any input on this issue and #74?

[jhalterman]

I'm no longer actively working on Lyra, but would be happy to take a PR to disable automatic recovery when using Lyra.

[michaelklishin]

Addressed in #82.