long-lived TCP connections being RST

>> 1) The RST is sent from the F5 to the real server, not to the client right?

 

 

The RST is sent from the F5 to the client; the real server never receives an RST from F5. (If we bypass the F5, the client never receives an RST from the real server)

 

 

>> 2)Is SNAT involved in any way?

 

 

We are using a dedicated SNAT Pool for this virtual server.

 

 

>> 3) What's the highest Idle Time you've tried?

 

 

We've tried 86400 seconds, client and server profile.

 

 

>> 4) How long will a connection stay up for?

 

 

In the range from 20 to 120 minutes every one of the 16 clients we have receive an RST (TCP 3WHS rejected)

 

 

>> 5) Are monitors failing at all?

 

 

Default tcp monitors are all OK

 

 

>> 6) Doesn't the client use a keepalive?

 

 

The client communicates every 5 minutes using AMQP

 

 

>> 7) Have you used the same profile settings client and server-side?

 

 

We've tried same profile settings on both sides, and at times using slightly different keepalive intervals for server/client, without success

 

 

>> 8) Are there any firewalls in path?

 

 

There are no firewalls

 

 

 

The AMQP client loses its link with the queue server and logs RPC read timeouts, failing to consume messages, regardless of the socket connection being still open and the heartbeat still working.

 

 

In the case of SSH, the connection simply gets dropped.

 

 

Thanks you again