When the close method is called on the producer it does not close the socket on the rabbitmq server (it does not appear to actually close the socket locally). As a result, over time the server will gradually be depleted of resources. All of the sockets appear to still operate heartbeats, the connections and heartbeat transmissions are visible on the management ui.
Reproduction steps
In a loop create a producer
Call the close method on the producer
Monitor the sockets on the rabbitmq server, they will stay connected
Expected behavior
Calling the close method should gracefully terminate the producer and terminate the socket on the server.
Describe the bug
When the
close
method is called on the producer it does not close the socket on the rabbitmq server (it does not appear to actually close the socket locally). As a result, over time the server will gradually be depleted of resources. All of the sockets appear to still operate heartbeats, the connections and heartbeat transmissions are visible on the management ui.Reproduction steps
Expected behavior
Calling the
close
method should gracefully terminate the producer and terminate the socket on the server.Additional context
No response