On Tue, Sep 28, 2010 at 6:46 PM, Jim Fulton <j...@zope.com> wrote: > On Tue, Sep 28, 2010 at 6:42 PM, Matthias <ni...@dr-code.org> wrote: >> Am 29.09.2010, 00:34 Uhr, schrieb Jim Fulton <j...@zope.com>: >> >>>> Is this a bug in ZODB? >>> >>> It appears so. Are you specifying a pool timeout? >> >> I don't set a timeout anywhere specifically. Maybe there is one a default >> one buried in grok/ztk, but I couldn't find anything on quick inspection. >> >> However, the error is gone for me now, because I discovered a mistake in my >> custom publisher. It would sometimes leave an open transaction so that the >> connection could not be closed. Too many open connections then caused the >> traceback in question I guess. Now that there aren't too many historical >> connections, the traceback does not appear anymore. > > OK. I'm glad it's cleared up. > > I'll fix this for 3.10 final.
It's fixed in 3.10.0b8. Jim -- Jim Fulton _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
