Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-04-03 Thread Dan Wilga
Based on others' comments, I found the solution to the problem. I just added a db_close(), and the problem is really, truly gone. For good measure, I put a db_sync() in as well. Why db_close isn't necessary with 3.x, but is with 4.0 is the weird part. Maybe this suggests a bug in 4.0? Or is

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-25 Thread Jim Smith
On Thu, Mar 21, 2002 at 02:01:49PM -0500, Michael Alan Dorman wrote: Perrin Harkins [EMAIL PROTECTED] writes: This sort of begs the question: why not use DB 3.x? Is there some new feature you need in DB 4? Anecdotaly, I believe the OpenLDAP and Cyrus projects have both found DB4 to be

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-22 Thread Dan Wilga
Aaron Ross wrote: my $db_key = tie( %{$Rhash}, 'BerkeleyDB::Btree', -Flags=DB_CREATE, -Filename=$file, -Env=$env ); die Can't open $file: $! .$BerkeleyDB::Error.\n if !$db_key; return $db_key; I was wondering if using

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Michael Alan Dorman
Perrin Harkins [EMAIL PROTECTED] writes: This sort of begs the question: why not use DB 3.x? Is there some new feature you need in DB 4? Anecdotaly, I believe the OpenLDAP and Cyrus projects have both found DB4 to be more reliable under load than DB3. Mike.

Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Dan Wilga
Hello, I have run into a problem specific to Berkeley 4.0.14 that I hope you can help me to diagnose. There are enough other products involved that I'm not sure if it's DB's fault or mod_perl's. Here's the setup: Linux 7.2 i386 perl 5.6.1 apache 1.3.19 with mod_perl 1.25 DB 4.0.14

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Perrin Harkins
Dan Wilga wrote: If I either use DB 3.x or even run this from the commandline (bypassing mod_perl) under DB 4 the problem goes away: only one locker is allocated per loop, and therefore the total number used does not increase unexpectedly. This sort of begs the question: why not use DB

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Dan Wilga
At 1:32 PM -0500 3/21/02, Perrin Harkins wrote: Dan Wilga wrote: If I either use DB 3.x or even run this from the commandline (bypassing mod_perl) under DB 4 the problem goes away: only one locker is allocated per loop, and therefore the total number used does not increase unexpectedly. This

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Perrin Harkins
Dan Wilga wrote: What surprises me is that all I have to do to introduce the problem is run it under mod_perl. It acts normally when run from the commandline. Well, let's see, what would be different... Is it possible that the problem is concurrency from multiple mod_perl processes? What

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Aaron Ross
I'm testing with the Perl script below, with the filename ending .mperl (which, in my configuration, causes it to run as a mod_perl registry script). I would re-write it as a handler and see if Apache::Registry is partly to blame. hth, aaron

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Dan Wilga
At 1:55 PM -0500 3/21/02, Perrin Harkins wrote: Dan Wilga wrote: What surprises me is that all I have to do to introduce the problem is run it under mod_perl. It acts normally when run from the commandline. Well, let's see, what would be different... Is it possible that the problem is

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Dan Wilga
At 2:03 PM -0500 3/21/02, Aaron Ross wrote: I'm testing with the Perl script below, with the filename ending .mperl (which, in my configuration, causes it to run as a mod_perl registry script). I would re-write it as a handler and see if Apache::Registry is partly to blame. Sorry, I

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Dan Wilga
OK, I'm an idiot who can't read. I was reading the wrong part of db_stat's output when I thought that running it with the .cgi ending also caused the problem. Turns out it doesn't. So I have not absolved mod_perl after all. It's definitely an interaction between it and DB 4. This is one of

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Dan Wilga
At 2:03 PM -0500 3/21/02, Aaron Ross wrote: I'm testing with the Perl script below, with the filename ending .mperl (which, in my configuration, causes it to run as a mod_perl registry script). I would re-write it as a handler and see if Apache::Registry is partly to blame. I tried

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Aaron Ross
I'm testing with the Perl script below, with the filename ending .mperl (which, in my configuration, causes it to run as a mod_perl registry script). I would re-write it as a handler and see if Apache::Registry is partly to blame. I tried doing it as a handler, using the

Re: Berkeley DB 4.0.14 not releasing lockers under mod_perl

2002-03-21 Thread Ed Grimm
Does shutting down apache free up your locks? (As an aside, I'm not sure I'll ever get over undef being proper closing of a database connection; it seems so synonomous to free([23]). I expect something like $db-db_close() or something.) Ed On Thu, 21 Mar 2002, Dan Wilga wrote: At 2:03 PM