On Wed, 2003-10-01 at 15:53, Dan McCormick wrote: > Each day, a few dozen httpds get stuck waiting for locks on the > Apache::Session files. ... > I've set things up per the MasonX::Request::WithApacheSession docs and > sample files, and I'm not doing anything particularly extraordinary with > the sessions. Anyone have any thoughts on how I might fix the problem?
I suggest you switch to the MySQL storage, and use the NullLocker. MySQL updates are atomic, even without the extra locking that Apache::Session adds. The file stuff could be atomic in this way too, but unfortunately it isn't implemented that way. The really bad thing though is that this may indicate that you have scoping problems that are preventing your session objects from being cleaned up. This would result in lost data (since the updates won't get written) even if you fix the locking problem. I suggest you go over the code where you use the session hash very carefully and make sure it goes out of scope at the end. - Perrin