if a job hangs (due to database locking for instance), then a mod_perl child
will hang as well (absent some additional watchdog-type program.) if enough
jobs hang to the point that we hit MaxClients, then it is too late to use
/server-status to see what jobs hung.
does anyone have a quick way
i'm interested in understanding the consequences of restart vs. graceful
better.
i've seen where the mod_perl guides recommend stopping and then restarting a
mod_perl apache rather than doing a graceful restart. i only saw
indications that memory does not get cleaned up cleanly if this is done.
i would like to prevent any of my mod_perl scripts from running longer than
5 seconds. is there an elegant way to make a general timeout that does not
require changing all my scripts? i run both Registry and Mason scripts in
my environment.
thank you in advance,
jlg
John Leon Guerrero --
for any HTTP 200's with zero
length
body sizes and traced backwards to see who the common culprit was. the only
caveat was that apache would sometimes log HTTP 200 when in fact the return
code
was HTTP 302 (redirect). it is natural to have a zero length body size for
a
redirect.
good luck,
John E. Leon
