Closed murbanowicz closed 3 years ago
Thanks for reporting, and the clear steps to reproduce @murbanowicz. I'll look into it.
One thing that may help in the meantime - if you're not using Rascal's automatic connection recovery, you could disable it, then the Vhost shouldn't reconnect.
Hi @murbanowicz, Sorry this is taking a while. I've managed to get Rascal to stop reconnecting after shutdown easily enough, but there's a secondary issue with the channel pool. The pool never completes draining and so blocks the shutdown for a new reason. I'm trying to find a workaround.
Think I've managed to figure this out. The channel pool was waiting indefinitely for a call to channel.close to yield. However, because the of the heartbeat error, the broker never replied, pool never finished draining. I've fixed in rascal this through use of a configurable destroy timeout, and volunteered to add to the timeout to the underly generic-pool library.
Fixed in 13.1.0. I'll push out a patch release if/when generic-pool-289 gets merged.
I highly appreciate your responsiveness and effort! Thanks! 🥇
Hi,
We have discovered an issue with the library.
Logs: