Hi all,
A little more tests reveal the following:
If Apache was not installed in the default location (c:\program
files\apache foundation\apache2.2) and instead installed into a path
that does not have spaces (eg. c:\Apache2.2), while restarting will
still fail, you can manually start the service again much faster; almost
immediately after it stops. It is possible to write a monitoring windows
service to start the apache service if it detects that it has stopped,
but it's not quite the elegent solution that people want to hear about.
So while it's better, it's still not good enough. Apache must still be
able to perform a restart on its own.
Any suggestions?
Foo JH wrote:
Hi all,
I am rather disappointed (and a little frustrated as well) on
modperl's inability to survive an Apache restart on the Windows
platform. The platform combo tested are Windows 2003 + Apache 2.2 (and
Apache 2.0) + modperl2 + libapreq2
I have come to accept the fact that once in a while modperl on Win32
will segfault, but the old Apache I tried (year 2005 iirc) seems to
recover, though it threw a windows fault dialog that scared the wits
out of my clients. But this time it's just unacceptable. The odd thing
is, if you try to start apache after it failed, it will fail again.
You have to wait about a minute (or more) before starting the server.
I don't mind any creative workarounds. Please share with me any
suggestions or tips that can circumvent this. Thanks much.
