Am 30.09.2010, 21:32 Uhr, schrieb Jim Fulton <>:

> On Tue, Sep 28, 2010 at 6:46 PM, Jim Fulton <> wrote:
>> On Tue, Sep 28, 2010 at 6:42 PM, Matthias <> wrote:
>>> Am 29.09.2010, 00:34 Uhr, schrieb Jim Fulton <>:
>>>>> 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.

Hey Jim,

thanks for the quick fix!

I found fixing my publisher did not really help. Now I have to talk the  
right people into upgrading grok to ZODB 3.10 final once it's released :)  
Looks like 3.10 is going to be a great release.

For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -

Reply via email to