I added the warns to the scripts and it appears that access to the
modules
is serialised. Each call to the handler has to run to completion before
any other handlers can execute.
Yes, on NT all accesses to the perl part are serialized. This will not
change before mod_perl 2.0
Oh my
Oh my ...
Indeed this happens. This is horrible ;o(
and make mod_perl unusable with NT web site with many visitors ;o(
How do you think - for intranet web application is it reasonable
to run few Apaches (with mod_perl) on the same box ?
yes, but as far as I know that isn't possible as
Oh my ...
Indeed this happens. This is horrible ;o(
and make mod_perl unusable with NT web site with many visitors ;o(
How do you think - for intranet web application is it reasonable
to run few Apaches (with mod_perl) on the same box ?
yes, but as far as I know that isn't possible
I am currently in the process of transferring a database driven site from
IIS to Apache on NT using mod_perl. Apache seems to lock up after about
10-20 minutes and the only way to get things going again is to restart
Apache (Apache is running from the console not as a service).
The site isn't
I am currently in the process of transferring a database driven site from
IIS to Apache on NT using mod_perl. Apache seems to lock up after about
10-20 minutes and the only way to get things going again is to restart
Apache (Apache is running from the console not as a service).
Well - I am
At 12:20 PM 1/17/00 +0100, Waldek Grudzien wrote:
I am currently in the process of transferring a database driven site from
IIS to Apache on NT using mod_perl. Apache seems to lock up after about
10-20 minutes and the only way to get things going again is to restart
Apache (Apache is running
I have just gone back and checked the logs. The majority of the time the
server locks up without putting anything in the error log. Currently,
there are only about 10 content handlers in the system and I am fairly
confident they work.
When it locks up I can still telnet into the server
At 01:26 PM 1/17/00 +0100, Gerald Richter wrote:
I would suggest, put
warn "foo" ;
allover in your perl code and then look in the error log and see where the
last warn came from, then you have the place where it lock up.
Gerald
I added the warns to the scripts and it appears that access to
I added the warns to the scripts and it appears that access to the modules
is serialised. Each call to the handler has to run to completion before
any other handlers can execute.
Yes, on NT all accesses to the perl part are serialized. This will not
change before mod_perl 2.0
Gerald
I had
