On 04:41 pm, cel...@gmail.com wrote: >Hi Jean-Paul thank a lot for your reply, intentionally I'm not >stopping the reactor this comes without my intervention
There are several calls to `reactor.stop` in the example, though. The reactor won't stop unless that method is called. >>> Failure: twisted.internet.error.ConnectionDone: Connection was >>>closed cleanly > >there is where I get lost, I'm using Solaris 10, python 2.6.2 and >twisted 10.1.0, could Solaris be the problem ? I don't know why the connection is being closed. The most likely reason is that there's a problem with the protocol class which causes it either to raise an exception locally when handling data or which causes it to send something that the server dislikes enough that it closes the connection. You could rule out the former by enabling logging when the process starts, instead of only immediately before it stops. For the latter, you'll have to look at network captures and understand the behavior of the server you're talking to. Jean-Paul _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
