Re: Berkeley DB problem: "Could not allocate memory"

>>184 Number of current locks.
>>380 Number of current lockers.
>>7 Number of current lock objects.
>>
>>
>Your repository should never have an lock accumulation when there are
>no attached processes. If you did this db_stat during such a time,
>then the fact that you have lock accumulation at all means that some
>processes didn't cleanly detach from the Berkeley DB environment.
>When this occurs, you can start seeing "Cannot allocate memory" errors
>well before the reported lock accumulation nears the maximums.
>
>

This repository is used only from an Apache httpd installation through
mod_dav_svn, and I see no traces of Apache coredumping or something
similar...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 8 21:46:56 2005