On Thu, 2004-09-30 at 19:32, Larry Hansard wrote:
> About 2-3 times a week, we get this error that I've attached.
The error you mention is symptomatic of a db connection resource leak
elsewhere in the code.
> Will this be fixed in 1.2.1?
The candid answer is that I hope so, but it's almost impossible to make
guarantees with this kind of indsidious bug. I've cleaned up several
places where a connection could have been leaked, and a couple where a
connection was definitely leaked. The fixes are in 1.2.1b1.