Tobias Hoellrich wrote:
>
> Kip,
>
> I think I mentioned this yesterday in an private email message already. I
> had the same problem with Apache::Session 1.03 in my environment. For some
> obscure reason, my tied %session didn't go out of scope and was never
> "untied" at the end of one request.
There are no obscure reasons. If your hash isn't scoped at the request
level, then it is going to live forever.
> This results in a situation where Apache::Session keeps a readlock and the
> next time you try to use the same session it'll hang in IPC::Semaphore::op
> when it tries to acquire the readlock.
Actually, more than one process can hold the readlock at once. The
problem is that some process is holding a writelock indefinitely.
> I worked around this situation by explictly untie'ing the tied %session at
> the end of my request by using
>
> $r->register_cleanup(sub { untie %session });
>
> Since then the Semaphore problems have disappeared.
>
> Hope this helps
> Tobias
--
Jeffrey W. Baker * [EMAIL PROTECTED]
Critical Path, Inc. * we handle the world's email * www.cp.net
415.808.8807
