Re: [Twisted-Python] Moderately-long running processes timing out in Twisted
We're using good_sql already. We're doing our best to move away from Oracle, honest! ;) Steve ----- Original Message ---- From: "glyph@divmod.com" <glyph@divmod.com> To: Twisted general discussion <twisted-python@twistedmatrix.com> Sent: Friday, September 5, 2008 2:22:08 PM Subject: Re: [Twisted-Python] Moderately-long running processes timing out in Twisted It seems that you have been a victim of at least one recently-fixed bug: http://twistedmatrix.com/trac/ticket/3244 and at least one long-standing one: http://twistedmatrix.com/trac/ticket/1753 As you can see from the tone of my (unfortunate) comment on the latter ticket, I don't think a lot of people use Oracle with Twisted. However, the issue is simple to hack around temporarily: set your ConnectionPool's "good_sql" attribute to 'select 1 from dual' as itamar suggests on #1753. Then, please submit a patch, and ideally a buildslave with a copy of oracle installed so that we can maintain support for it :). On 06:06 pm, spiritualmechanic@yahoo.com wrote:
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
On 06:31 pm, spiritualmechanic@yahoo.com wrote:
(lots of stuff snipped) Hmm. I was guessing about the most likely cause since the other (fixed) bug inhibits error reporting. Do you get a more useful traceback out of twisted trunk@HEAD? I wouldn't advocate using that in production, but the error-logging bugfix would tell you at least what's really going wrong.
On Fri, Sep 5, 2008 at 3:33 PM, <glyph@divmod.com> wrote:
This could be way off base, but i used to see this on stale connections being utilized again in the next xmlrpc job, basically timing out. (mysqldb- Mysql Server has gone away). Using db.ping() could keep them alive, or testing the connection/recreating before executing a new xmlrpc job. do these exceptions occur when they are running not through the xmlrpc. Jeff
On 06:31 pm, spiritualmechanic@yahoo.com wrote:
(lots of stuff snipped) Hmm. I was guessing about the most likely cause since the other (fixed) bug inhibits error reporting. Do you get a more useful traceback out of twisted trunk@HEAD? I wouldn't advocate using that in production, but the error-logging bugfix would tell you at least what's really going wrong.
On Fri, Sep 5, 2008 at 3:33 PM, <glyph@divmod.com> wrote:
This could be way off base, but i used to see this on stale connections being utilized again in the next xmlrpc job, basically timing out. (mysqldb- Mysql Server has gone away). Using db.ping() could keep them alive, or testing the connection/recreating before executing a new xmlrpc job. do these exceptions occur when they are running not through the xmlrpc. Jeff
participants (3)
-
glyph＠divmod.com -
Jeff Dyke -
Steve Lewis