You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by EF <ef...@ccitt5.net> on 2000/08/30 04:39:48 UTC
mod_jk results in apache SIGTERM
Hello,
Has anyone ever experienced the following behavior? When switching from
mod_jserv so mod_jk in order to get ajp13 support apache 1.3.12 shuts down
directly after start.
[Wed Aug 30 04:23:41 2000] [notice] caught SIGTERM, shutting down
This occurs both with the binary linux i386 mod_jk.so from the 3.2 beta2
directory and when compiled with apxs from the 3.2 nightly build. The
mod-jk.conf file included from httpd.conf contains the following lines:
LoadModule jk_module libexec/mod_jk.so
<IfModule mod_jk.c>
JkWorkersFile /usr/local/tomcat/conf/workers.properties
JkLogFile /usr/local/tomcat/logs/mod_jk.log
JkLogLevel warn
JkMount /*.jsp ajp13
JkMount /servlet/* ajp13
</IfModule>
This is the only module that is not statically compiled into apache, so
it's the first and only loadmodule directive in httpd.conf
Apache is compiled with several other modules(staticaly), mod_ssl,
mod_php, mod_frontpage, mod_casp, but that shouldn't have any impact.
As soon as mod-jk.conf is removed from apache it starts correctly again.
If anyone has any suggestions they are all welcome.
regards Tomas