Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-dev@jakarta.apache.org
Sender: bojan@binarix.com
Message-ID: <3B5583D2.5B60C5C9@binarix.com>
Date: Wed, 18 Jul 2001 22:40:50 +1000
From: Bojan Smojver <bojan@binarix.com>
Organization: Binarix Corporation Pty Ltd
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Re: Problem with mod_jk 1.2.0 (latest CVS snapshot)
References: <3B55790C.ABBAA094@binarix.com> <995459112.3b558028812c8@intra.cs>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

OOPS! Sorry :-(

jk.conf (called from httpd.conf)
-----
###############################################################################
#                     Apache JK Configuration
File                            #
###############################################################################

<IfModule mod_jk.c>

JkWorkersFile /etc/tomcat/workers.properties
JkLogFile     /var/apache/logs/mod_jk.log
JkLogLevel    error

JkMount *.jsp                   ajp13
JkMount /*.jsp                  ajp13
JkMount *.vm                    ajp13
JkMount /*.vm                   ajp13
JkMount /servlet/*              ajp13
JkMount /login/j_security_check ajp13

</IfModule>
-----

workers.properties file:
-----
###############################################################################
#                        Apache JK Configuration
File                         #
###############################################################################

#
# Execution parameters
#######################

# Setup for RedHat Linux system
#
workers.tomcat_home=/usr/local/tomcat
workers.java_home=/usr/local/jdk
ps=/
worker.list=ajp13

# Definition for Ajp13 worker
#
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13
-----

BTW, this is the stuff that was running OK with Tomcat 3.3 M3 and it
runs OK with CVS Tomcat 3.3 + mod_jk from M3.

As for DSO, I'll have to work on that, so probably some time tomorrow
(Sydney time).

One of the points that I'm trying to make anyway is that statically
linked Apache is supported, so mod_jk should run with it ;-) It runs
faster anyhow and it uses less memory.

Bojan

Gomez Henri wrote:
> 
> > 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.
> 
> Could you try to rebuild it dynamically (DSO) and see if the
> problem persist. Thanks to send us mod_jk parts in httpd.conf
> and workers.properties file :)
> 
> > 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
> >
> 
> -
> Henri Gomez                 ___[_]____
> EMAIL : hgomez@slib.fr        (. .)
> PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
> PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6