long connection

Currently my environment is a client; an F5; two rabbitmq servers, based on AMQP protocol, mainly used to send and receive messages.

The current problems encountered is to establish long connection between client and F5, send messages are based on the long connection. Because F5 load balancing approach is based on the connection, then the link would only current F5 rabbitmq server and a back-end connection is established. When this rabbitmq the server is down, my client will receive from socket write error message. My understanding is that this time the F5 and survival rabbitmq either did not establish a connection, or to establish a connection, but the connection status between F5 and client is not the same, so the connection is useless.
The main difference is that I want to load the long tcp connection instead of http connection, http connections are stateless, there is no problem I described above.
I guess the solution is to establish a connection when the client side, when and F5, F5 simultaneously and rear two machines to connect and stay connected. Such a problem when to switch.
From this issue arise out of, for the same client and F5's long connection, whether the inside of the message is sent to a different back-end servers to achieve true load balancing, F5 needs to be able to support this estimate AMQP protocol to use for the job it rabbitmq . I guess a lot of C / S architecture have my needs, such as banks, so help us to see there is no solution