-
Notifications
You must be signed in to change notification settings - Fork 20
Open
Description
I noticed the other day that if my connection tries to auto-recover when there is active work in the threadpools, the connection gets re-established, but it immediately gets killed because the outstanding work tries to do message acknowledgements for messages that were received under the previous connection.
When the acknowledgements are attempted rabbitmq reports it as a protocol violation (which it is) and kills our new connection 😭.
I think this will need to be fixed in the upstream bunny gem, but wanted to document it here for any brave explorers.