Sovel Does not restart after "socket_closed_unexpectedly"

[LeonKarabchevsky]

We are using a shovel to forward messages between 2 machines.
Sometimes we get the following error: " Shovel ##### in virtual host '/' detected destination connection failure: socket_closed_unexpectedly"
After this message rabbitmq memory consumption raises significantly until hitting the "memory high watermark" and staying in this state until we manually restart the sovels. Looking at the shovels statuses they appear as running
Attached are the logs and "rabbitmqctl report".

report.txt
log.txt

[michaelklishin]

I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :(