Logging Level Necessary to catch TCP Session Drop from Idle Timeout

Unanswered Question
Jan 23rd, 2009

I am looking at an app that leaves tcp sessions idle for a while and am looking to tweak the idle timeout window. What level of logging will be necessary to find out when a TCP session is close due to the idle timeout settings?


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
amritpatek Fri, 01/30/2009 - 15:32

To override the global TCP or UDP idle timeouts for the specified protocol, specify the number of seconds for a different idle timeout. This timeout overrides the global TCP and UDP timeouts but will not override the global DNS timeout. (Optional).

I hope it may help you.


This Discussion