Tim Peters wrote:
[Syver Enstad]
I have recently upgraded from ZODB 3.2 to 3.5.1. After doing this I
notice that ZEO throws exceptions on commiting a transaction for certain
types of Persistent classes.
...
I was able to create a small self-contained test case from this description,
and
[Syver Enstad]
I have recently upgraded from ZODB 3.2 to 3.5.1. After doing this I
notice that ZEO throws exceptions on commiting a transaction for
certain types of Persistent classes. ...
[Tim Peters]
I was able to create a small self-contained test case from this
description, and opened a
Monica chopra wrote at 2005-12-29 18:17 -0800:
I have recently jumped into python and ZODB . I am quiet familar to syntax
and everything but there is one Issue . when we create a .fs file or say
data.fs and saves in it some objects.If we open this file in notepad or other
editior. It shows
Tim Peters wrote at 2005-12-29 12:59 -0500:
...
[Tim Peters]
It means that _ConnectionPool no longer has a reason to remember
anything about that Connection. Application code can continue
keeping it alive forever, though.
[Denis Markov]
But what about RDB-Connection what stay in cache
[Dieter Maurer]
They did not tell us about their application. But, Zope's database
adapters work like this. They use the ZODB cache (and its pool) as an RDB
connection pool. Thus, if the ZODB caches are not released, the RDB
connections won't.
I believe you, but I'm not sure what to make of
[Tim Peters]
...
I suggested before that forcing calls to gc.collect() would give more
evidence. If that doesn't help, then it's most likely that the
application is keeping Connections alive.
[David Rushby]
I'm not the OP, but I was able to reproduce the problem he was
encountering. Calls
