transaction commit timeout should log at CRITICAL

Bug #670986 reported by ChrisW
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ZODB
Fix Released
Undecided
Unassigned

Bug Description

See:
https://mail.zope.org/pipermail/zodb-dev/2010-November/013849.html

The logging should be at CRITICAL, since if this occurs, clients will likely be in a hosed state but the exceptions they have logged will merely be of the "client disconnected" type.

This feature could also do with some docs warning that the timeout should be set very high, eg: 5 mins.

Jim Fulton (jim-zope)
Changed in zodb:
status: New → Fix Committed
Jim Fulton (jim-zope)
Changed in zodb:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers