tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bojan Smojver <bo...@binarix.com>
Subject Problem with mod_jk 1.2.0 (latest CVS snapshot)
Date Wed, 18 Jul 2001 11:54:52 GMT
After including it in Apache 1.3.20, statically compiled/linked for
RedHat Linux 7.0, the error messages 'child pid xxxxx exit signal
Segmentation fault (11)' start appearing in the error log file of
Apache. mod_jk from Tomcat 3.3 M3 works fine with both Tomcat M3 and the
latest 3.3 CVS snapshot.

Here is the scenario to replicate the problem:

- start Tomcat and Apache, mod_jk for latest CVS
- call a few JSP/Velocity or whichever pages that exercise mod_jk
- restart Tomcat
- restart Apache (gracefully!) 2 seconds after Tomcat's startup (I'm
doing this from my startup script)
- try to load any page from the site you were just browsing and you'll
get errors along the lines that the web server didn't return anything
- log files show segfaults

If you stop Tomcat and Apache and start them again, this doesn't happen.
Also, when mod_jk shipped with M3 is used everything is sweet.

Don't know all that much about mod_jk, but it seems the problem is
related to graceful restart of Apache and subsequent reconnection to
Tomcat (ie. part of the code that does that was changed and ouch,
segfault :-)

Hope this helps.

Bojan

Mime
View raw message