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 concurrency from multiple >mod_perl processes? What happens when you run it with httpd -X ?
The same (bad) results. >Could there be a permissions issue involved? Nope, all the files get deleted and re-created in the script (and they do get created correctly). Permissions also wouldn't explain why the same thing works in 3.x. >Are you sure you're only invoking the script once under mod_perl? Yes, I'm doing it by a direct URL. > If you raise the number of repetitions, does the command-line >version exhibit the problem? No, the commandline version never does. When run under mod_perl, the "Current number of lockers" reported by db_stat is always equal to the number of iterations, no matter how many are used. >I don't see any scoping issues in your script, but are you running >it under Apache::Registry? Maybe the nested subroutines that >creates are causing problems. Ack. Ptooey. I just renamed the file to end in ".cgi" and the problem persists. I even removed mod_perl from my configuration files, and it still fails. I thought I had tested the before, but I guess not. This can only mean mod_perl isn't at fault. Sorry for the false alarm. I'll have to go back to Sleepycat with this new information. Dan Wilga [EMAIL PROTECTED] Web Technology Specialist http://www.mtholyoke.edu Mount Holyoke College Tel: 413-538-3027 South Hadley, MA 01075 "Who left the cake out in the rain?"
