Reconnecting is creating some "ghost" connections #9
Description
When we leave the STOMP connection idle for a while, TorStomp logs that the "connection unexpected end" and then then tries to reconnect to the queue but the old connection still activate in rabbitMQ.
Due this issue rabbitMQ sends a new queue message to this old connection that is not being handled by TorStomp anymore.