Wiebe Tijsma

+1 I've ran into this issue only when I wanted multiple consumers on the same queue.

By default you can't have multiple message types per queue. Can you try to register the HandlerCollectionPerQueueFactory as IHandlerCollectionFactory in your container and see if that works for you?

@StanislavChankov having multiple message types per queue is not supported by default, I have used it before by registering the HandlerCollectionPerQueueFactory as IHandlerCollectionFactory, if that doesn't work anymore I don't...

Perhaps there's something that can generate change notes based on the tags and git log? Using most github features for tracking seems to make sense but I don't have a...

Thanks @pardahlman!

One way would be to take the DefaultConsumerErrorStrategy, modify it with own implementation and register that in the container.

I think because the default message body is always JSON, it makes sense to assume it's JSON in the DefaultConsumerErrorStrategy right?

I just think EasyNetQ was never written to be able to recover from longer RMQ outages. I think it's something we can look at for a new major version, but...

@mrychter I partially agree, I have worked mostly in environments that always required RabbitMQ to be available, if it wasn't then having to restart dependent services was probably the least...

@stevenxi is this still an issue? Is there a way this is reproducible using a unit test?