long-lived TCP connections being RST
Hello,
We can't make AMQP permanent long-lived TCP connections to a RabbitMQ pool work smootly with LTM. The LTM keeps dropping connections with a TCP RST payload of "TCP 3WHS rejected", with the application left in an unrecoverable socket state needing a restart.
We've read thoroughly this: http://support.f5.com/kb/en-us/solutions/public/9000/800/sol9812.html, and played with different values for TCP Profiles, including Idle Timeout, Reset on Timeout, Keep Alive Interval, Max Syn/Segment Retransmission, etc. without success. We cannot change LTM 'Global Settings', but we discarded as possible causes virtual server connection limits, available pool members or limits, or iRules or SNAT problems.
We also can't make SSH connections stay open for more than 1 hour, regardless of user activity, but in this case we've not observed the TCP RST payload.
We are looking for a recipe (TCP Profile?) to make a virtual server "intouchable", making it's connections undroppable, or droppable, say, only once a day. Has someone ever used LTM as a SSH / RabbitMQ balancer with a, e.g., 6-hour inactivity tolerance?
Thanks in advance,