[ZODB-Dev] POSKeyError with Zope 2.7.2, suddenly appeared, thendisappeared...

[Florent Guillaume]

Hi Dieter,

Dieter Maurer  <dieter at handshake.de> wrote:
> >I can't agree that info level was inappropriate here, at least not without a
> >lot more thought than I can give to it now.  A problem with ZEO is that
> >people normally want a way to tell that ZEO is still _alive_ in info-level
> >logs.  Logging info about transaction-lock activity is one natural way to do
> >that (if you're doing transactions over ZEO, but not seeing those msgs, you
> >can deduce that ZEO is dead or deadlocked or something; and looking then at
> >the last lock activity logged can be a good clue about how things got
> >hosed).
> 
> I changed this (in our private copy) and now
> explicitly log when a transaction needs to wait for the
> transaction lock (and what (user and description) is holding
> this lock) and when it is restarted.

Could you point me to where you added these logs? I'm trying to find the
reason for a deadlock we have here...

Florent

-- 
Florent Guillaume, Nuxeo (Paris, France)   CTO, Director of R&D
+33 1 40 33 71 59   http://nuxeo.com   fg at nuxeo.com