Forum Discussion
Chris_Lira_5487
Nimbostratus
Nimbostratusidle timeout
In our BIGIP-LTM, the idle timeout is set to 300 seconds. When we run a transaction which takes about 10 minutes, we see a second transaction enter our web/app server after about 5 minutes (so we end...
hoolio
Cirrostratus
CirrostratusLTM shouldn't retry a request unless you have an iRule which explicitly resends a request. LTM should send a FIN (or maybe a RST?) when the TCP idle timeout expires. That would instruct the peer in the connection to close the TCP connection. It would not allow for resending the same request unless the client specifically retried the request with interaction from the user.
If you capture a tcpdump of the client and server side traffic you should be able to see exactly what's happening. If you want info on capturing/inspecting a tcpdump, you can search for tcpdump on AskF5.com and/or open a case with F5 Support.
On another note, does the server actually take 10 minutes or more from the time the last request packet is received to start sending any response packets? If that's true, you should extend the TCP idle timeout to a value higher than that time to ensure LTM doesn't prematurely close the TCP connections.
Aaron
