Comment 1 for bug 857714

I don't remember seeing this before, and I'm wondering if there is a try catch that is getting missed in the db code because of the interaction with eventlet. Some things to try:

diff -r f30a2fa65f30 eventlet/hubs/hub.py
--- a/eventlet/hubs/hub.py Wed Jun 08 23:47:26 2011 -0700
+++ b/eventlet/hubs/hub.py Sat Sep 24 04:51:22 2011 -0700
@@ -173,7 +173,7 @@
                 cur.parent = self.greenlet
         except ValueError:
             pass # gets raised if there is a greenlet parent cycle
- clear_sys_exc_info()
+ #clear_sys_exc_info()
         return self.greenlet.switch()

     def squelch_exception(self, fileno, exc_info):

And:

https://bitbucket.org/which_linden/eventlet/pull-request/1/fix-broken-expiration-timer-for

Can you see if any of those make a difference. It would also be great to have a very simple repro case for this error to aid in testing.