[ZODB-Dev] transaction timeouts raise no exceptions and cause strange errors on clients

[Chris Withers]

On 04/11/2010 14:50, Jim Fulton wrote:
> Actually, I think it should be used, at least for applications with
> high availability requirements. For applications like our's (ZC's)
> it amounts to a "don't be stupid" setting.
>
> For some applications, it's better to risk inconsistency than to have
> your application grind to a halt.  I consider it an emergency device
> though, which is why I'd set it pretty high.

...except that it logs at INFO ;-)

Can you raise that, or would you mind if I raised that to CRITICAL?
(it does feel like a CRITICAL kind of thing, based on the information 
you've provided today)

cheers,

Chris

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
            - http://www.simplistix.co.uk