Python/Twisted: exceptions.RuntimeError: doWrite called on a twisted.internet.tcp.Port -
we have gem of exception being thrown during start-up of application, when clients aren't connected or trying connect, when clients start connect once system has initialised,
[twisted.spread.pb.pbserverfactory] unhandled error traceback (most recent call last): file "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 88, in callwithlogger return callwithcontext({"system": lp}, func, *args, **kw) file "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 73, in callwithcontext return context.call({ilogcontext: newctx}, func, *args, **kw) file "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 118, in callwithcontext return self.currentcontext().callwithcontext(ctx, func, *args, **kw) file "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 81, in callwithcontext return func(*args,**kw) --- <exception caught here> --- file "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py", line 619, in _doreadorwrite why = selectable.dowrite() file "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1117, in dowrite "dowrite called on %s" % reflect.qual(self.__class__)) exceptions.runtimeerror: dowrite called on twisted.internet.tcp.port [twisted.spread.pb.pbserverfactory] (tcp port 37605 closed) [twisted.spread.pb.pbserverfactory] stopping factory <twisted.spread.pb.pbserverfactory instance @ 0x7f25262bcab8>
the application written in python 2.7.6 twisted 13.2.0 on ubuntu 14.04 64-bit, kernel 3.13.0-34. not see exception when running same code on windows 7 , ubuntu 10.04, have not tried on other os's.
the performance of system unpredictable @ best when exception thrown. in instances there seems no noticeable loss in performance , clients can connect , disconnect @ , data communication integrity solid , software works. in other instances clients can connect once on port , when client disconnected client can not longer connect on port. there times when clients cannot connect port @ all, if reactor stops listening on port??
i can't see reference code in traceback, i'm @ loss start looking fix.
the best reference have found issue here, however, thread seems go without solution?
has run before , found fix, or work around or had fir of rage , tossed computer out window?
cheers
Comments
Post a Comment