William, the point I was trying to make is:
1. My restart test scope merely loads modperl + libapreq. There is ZERO
application code loaded. In other words, all I did after installing
modperl + libapreq is to ONLY load them into httpd.conf:
LoadFile c:/Perl/bin/perl58.dll
LoadModule perl_module modules/mod_perl.so
LoadFile bin/libapreq2.dll
LoadModule apreq_module modules/mod_apreq2.so
Noticed there is no other code loaded. No database used. Super duper
minimal test model.
2. When you said that you managed to get modperl to survive an apache
restart on a Win32 OS, I'm really keen to understand how you have done
it differently. Is it because you are not using libapreq? Or is the
default installation settings not optimal?
Foo, you missed my point all together.
Something in YOUR PERL APP is opening resources that are "locked" and will
prevent another process from obtaining them for approx 60 seconds.
What, why and how are your puzzles, I'm afraid. There's nothing in the
"generic" apache/perl/modperl that did this to you.
More debugging logs, finer debugging details might help you pin it down.
