Andre_12127
Jun 26, 2012Nimbostratus
Dealing with long lasting outbound TCP Connections
I am currently trying to resolve an issue concerning long lasting TCP Sessions.
One of the balanced webservers is regularly querying a database server that is outside the loadbalanced segment. The operation triggered lasts quite a long time, since it has to process a large amount of data. During that time the TCP session is still open but idle.
After one hour the session is resetted by the Big IP causing the Query to fail.
My suspicion is that this reset is caused by the wildcard forwarding server 0.0.0.0 which routes the outbound traffic back to the rest of the LAN. This server has a timeout setting in its client connect profile of 3600 seconds which would qualify as a reason.
I tried bypassing that by adding a second forwarding server which only contains the one database host needed and added a longer timeout in a separate Client Protocol Profile, as well as disabling resetting timed out TCP session without, success.
I am wondering wheter I am completely thinking wrong here or that wildcard virtual server matches before the dedicated Forwarding Server matches and I don´t see a way at the moment to reverse that, if there is one at all.
Currently I am thinking that adding an iRule to the wildcard server that exchanges the client protocol profil when an IP from a certain datagroup matches might be the most feasable solution.
Or would there be an easier way around such a problem?
The reason why I am asking is that we do not have a real test environment and everything is run over that one productive cluster (I know it should be different, but I am already sore from argumenting with the other admins), and fidgeting around with the standard route doesn´t leave me feeling comfortable.
So if there is an easier solution to this problem it would be greatly appreciated.
Regards
Andre