On Wed, 2003-10-01 at 18:56, Dave Rolsky wrote:
> On Wed, 1 Oct 2003, Javier Alvarado wrote:
>
> > 2) Make sure the session is untied after *every* request (i.e. even if
> > a request is aborted, an error occurs in the middle, etc). Otherwise,
> > when the next request tries to tie it it w
On Wed, 1 Oct 2003, Javier Alvarado wrote:
> 2) Make sure the session is untied after *every* request (i.e. even if
> a request is aborted, an error occurs in the middle, etc). Otherwise,
> when the next request tries to tie it it will block.
With MasonX::Request::WithApacheSession, this
I don't know for sure what may be causing the lockups, but I can think
of two things to try:
1) Use Transaction => 1 when tieing your session.
2) Make sure the session is untied after *every* request (i.e. even if
a request is aborted, an error occurs in the middle, etc). Otherwise,
when t
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
Hi,
I have an Apache 1.3.27/modperl 1.27 site using HTML::Mason 1.20 with
MasonX::Request::WithApacheSession 0.23 on a Redhat 7.3 system. The
site gets about 5,000 hits/day.
Each day, a few dozen httpds get stuck waiting for locks on the
Apache::Session files. An lsof on the Apache pids reports
