Regarding the best Apache for Windows, I have a problem running Apache under
windows and I think this thread might help me.
I tried Apache 2.2.4 with and without SSL support, and Apache 2.2.6 from
apachelounge, but they still don't work.
I read that Apache 2.2.6 from apachelounge should work with mod_perl. Isn't
this true?
They all install correctly, and I can even start the server with the default
httpd.conf. It gave an error just a single time with the default httpd.conf.
If I install mod_perl, the percentage of the times when Apache doesn't want
to start and give errors is much bigger, but still most of the times it
starts and works.
If I install Catalyst and use a certain Catalyst app (that doesn't have
errors), Apache can start very rarely.
When I try to start the server, it appears an error message "Visual Studio
just in time debugger" that doesn't give any helpful information. Most of
the times in the error log is not printed absolutely anything, and sometimes
it prints that the main thread couldn't start the child thread and that the
thread was closed, or sometimes it prints that the main thread received a
kill signal and that it closes.
I had VS6 and VS.net 2005 installed, but I've uninstalled them both. I have
no program that starts with "Microsoft" in the Add-Remove programs list, but
that Visual Studio just in time debugger appears.
Do you have any idea what could have happened? I think it should be a
problem of Apache for Windows, or a Windows issue, or a hardware issue, but
I don't know how to
test it.
Thank you for any idea.
Octavian
----- Original Message -----
From: "Foo JH" <[EMAIL PROTECTED]>
To: "William A. Rowe, Jr." <[EMAIL PROTECTED]>
Cc: <modperl@perl.apache.org>
Sent: Wednesday, October 03, 2007 10:13 AM
Subject: Re: Best version of Apache for Win32 deployment
Right. Except there is no 2.2.5;
2.2.5 is not released on the Apache web site. Those who want this version
can get it at ApacheLounge.
Of course 2.2.4 essentially worked, while 2.2.7 will give the modperl'ers
on Windows something they have BEGGED for forever, the chance to see
parsing
errors at startup from their httpd.conf file(!!!)
Yes! It's been egging me for the longest blistering time!
