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 sort of begs the question: why not use DB 3.x? Is there some >new feature you need in DB 4?
I'm having problems with minor DB corruption in the last release of 3.x (3.3.11), so I wanted to try 4. >It's been a little while since I messed with this stuff, but I don't >think you need to tear down the Env each time. I think you can just >create it the first time and reuse it after that. Maybe that will >help. I tried that, believe me :-). I only did it this way in the test script to show that the problem occurs despite that bit of extra caution. (Even the "undefs" are probably not needed, but are there for clarity.) 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. >(Ah, Mount Holyoke. As a Five College alumn, I remember it well.) :-) Dan Wilga [EMAIL PROTECTED] Web Technology Specialist http://www.mtholyoke.edu Mount Holyoke College Tel: 413-538-3027 South Hadley, MA 01075 "Seduced by the chocolate side of the Force"
