GOMEZ Henri wrote:
>
> >Just did a DSO version and couldn't replicate the problem (BTW, I've
> >recompiled/statically linked Apache and mod_jk again since then and the
> >problem was still there). So, maybe it has to do with statically linking
> >Apache after all...
>
> Strange problem. What's the difference between static and dynamic.
> We may have missed something at mod_jk init time ?
This only happens during a graceful restart. Normal restart is OK. What
does mod_jk do when it receives SIGUSR1? Does it actually do anything?
Maybe that's the problem. Or it could have to do with Apache's behaviour
on SIGUSR1. Something like, if DSO then modules are reloaded and
therefore reinitialised, if static then the configuration file is
re-read and that's it (pure speculative BS, I have no idea what Apache
actually does). I kind of remember that people from mod_ssl were saying
something about Apache init process being a bit strange (something like
two passes) but that I think has to do with startup. Not sure.
> >I still have to distribute this DSO version of Apache and mod_jk to some
> >slower machines to see if that makes any difference at all. The machine
> >that didn't produce any errors is a 1 GHz Athlon, so timing issues could
> >have been resolved by brute force, who knows...
>
> Thanks to tell us what happened...
Well, once I actually do that I surely will. I don't know if you've been
in the position to run your own business, but I can only 'hack' when
nothing else requires my immediate attention :-(
> >Is there a recommendation as to the order of loading mod_jk for both
> >statically linked version and the DSO version? Maybe that's important.
>
> I load mod_jk after alias and before rewrite and never get any problems.
> Not I also use php4
Thanks for the tips about module order. I'll see how that affects the
whole thing.
Bojan
