On Mon, 2004-03-08 at 13:44, Chris Ochs wrote:
> sub handler {
> $r = shift;
> untie %session;
%session is a global then? That explains why you have trouble when the
script dies. I'd suggest switching to using $r->pnotes() for storing
it. Alternatively, you could use a cleanup h
- Original Message -
From: "Perrin Harkins" <[EMAIL PROTECTED]>
To: "Chris Ochs" <[EMAIL PROTECTED]>
Cc: "Modperl List" <[EMAIL PROTECTED]>
Sent: Monday, March 08, 2004 6:27 AM
Subject: Re: Apache::Session and DB_File problems
> On S
On Sun, 2004-03-07 at 13:34, Perrin Harkins wrote:
> Jeffrey W. Baker wrote:
> > I wasn't aware of these issues before. Looks like I'll have to use
> > BerkeleyDB or Tie::DB_Lock or something.
>
> On closer inspection I think it's mostly okay because the session object
> is supposed to go out of
On Sun, 2004-03-07 at 21:13, Chris Ochs wrote:
> Been doing some more testing on this. Previously I was untying the
> sessions when the handler was finished. But it seems that all it takes is
> just one child to exit uncleanly where I cant' catch the error and untie the
> sesssions, and that's a
>
> On closer inspection I think it's mostly okay because the session object
> is supposed to go out of scope and get destroyed (and thus untie) after
> every interaction, and the locking should mean that only process is
> writing during that time. You could run into trouble though if a
> process
Jeffrey W. Baker wrote:
I wasn't aware of these issues before. Looks like I'll have to use
BerkeleyDB or Tie::DB_Lock or something.
On closer inspection I think it's mostly okay because the session object
is supposed to go out of scope and get destroyed (and thus untie) after
every interaction,
On Sun, 2004-03-07 at 09:31, Perrin Harkins wrote:
> Chris Ochs wrote:
> > This must be my day... I am stress testing a new application that uses
> > apache::session with the DB_File backend store. When hitting it with apache
> > bench after a few hundred connections something with the db file g
Hi there,
On Sat, 6 Mar 2004, Chris Ochs wrote:
> stress testing a new application that uses apache::session with the
> DB_File backend store. When hitting it with apache bench after a
> few hundred connections something with the db file gets wacked, and
> apache starts to segfault until I delet
Chris Ochs wrote:
This must be my day... I am stress testing a new application that uses
apache::session with the DB_File backend store. When hitting it with apache
bench after a few hundred connections something with the db file gets
wacked, and apache starts to segfault until I delete the .db
This must be my day... I am stress testing a new application that uses
apache::session with the DB_File backend store. When hitting it with apache
bench after a few hundred connections something with the db file gets
wacked, and apache starts to segfault until I delete the .db file, at which
po
10 matches
Mail list logo
