My initial tests when enabling the TCP keepalive were successful. I've reduced my tcp_keepalive_time for 30secs instead of 2hours (7200secs) for testing. I'll update this thread if my problem goes back. :)<br><br><br>
---<br>Alvin Delagon<br><br><div class="gmail_quote">On Tue, Jun 3, 2008 at 9:00 PM, Itamar Shtull-Trauring <<a href="mailto:itamar@itamarst.org">itamar@itamarst.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Tue, 2008-06-03 at 14:10 +0200, Gabriel Rossetti wrote:<br>
> Yes, I found that in the meantime, but I tried it and it didn't work.<br>
> Sometimes when the connection is closed abruptly, the server doesn't<br>
> detect the lose. I looked at the oscar protocol implementation and they<br>
> have an application level keepalive, thus I though maybe it had to be<br>
> done that way and the server verifies every x seconds or minutes if it<br>
> hasn't received anything from a client, it removes it from it's<br>
> connected list. So Does anyone know how to deal with this problem?<br>
<br>
</div>Application level pings are the only way to go if you want quick<br>
detection of timeouts, yes. You could do that with xmlstream by sending<br>
a no-op command that expects a response every few minutes.<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.alvinatorsplayground.blogspot.com/">http://www.alvinatorsplayground.blogspot.com/</a>