RabbitMQ connection gets cached, fails when unused for a while

I'm still working to prove this is a real issue, but it seems like it could be. The rabbitMQ connection gets cached into a singleton instance, which means it could be connected and idle for a while. If the connection gets broken, there is a test for connection.isOpen(), but if it's anything like LDAP, it's a bogus call and can't tell when the server has dropped the connection (thus why LDAP has validators). So a call to publish a message could fail because the connection was bad, and there is no retry loop. When an error is thrown, the connection isn't nulled out, so it will continue using the bad connection (forever?)