Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of Chris.Boyce@cdw.com
 designates 12.32.91.181 as permitted sender)
From: Chris Boyce <Chris.Boyce@cdw.com>
To: "users@tomcat.apache.org" <users@tomcat.apache.org>
Subject: Abandoned apache children with mod_jk
Thread-Topic: Abandoned apache children with mod_jk
Thread-Index: Ac5upwWlCkaP4gRST7WqYZSEyGzJJw==
Date: Fri, 21 Jun 2013 17:47:14 +0000
Message-ID: <45F77E934191E04DA607C76554F3BF220E334E0B@EXMBD2VH.corp.cdw.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hello,

I'm running apache 2.2.24 (worker MPM) with mod_jk 1.2.37 under Solaris 11,=
 compiled as follows (from config.log):

--with-included-apr --with-mpm=3Dworker --enable-so --enable-rewrite --enab=
le-headers --enable-proxy --enable-proxy-http --enable-expires --enable-non=
portable-atomics=3Dyes --disable-include --disable-autoindex --disable-imap=
 --disable-userdir CC=3D/usr/sfw/bin/gcc

We are running Tomcat 7.0.32.

Since moving to Solaris 11 I'm noticing over time that apache children are =
getting left in an idle state (and usually not showing up on the scoreboard=
 at all) when doing graceful restarts.=A0 If I do a hard restart, the error=
_log notes that the process had to be forcibly killed:

[Wed May 15 11:41:24 2013] [warn] child process 10057 still did not exit, s=
ending a SIGTERM
[Wed May 15 11:41:26 2013] [error] child process 10057 still did not exit, =
sending a SIGKILL

If I let apache go unchecked, it will eventually stop passing traffic compl=
etely and a hard restart is required.=A0 Example ps output looks like this:

nobody 24429 20925=A0=A0 0 11:43:59 ?=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0:02 /u=
sr/local/apache2/bin/httpd -k start
nobody=A0 9750 20925=A0=A0 0 23:59:02 ?=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0:00 =
/usr/local/apache2/bin/httpd -k start
nobody 20925=A0 2440=A0=A0 0=A0=A0 May 15 ?=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 3=
:07 /usr/local/apache2/bin/httpd -k start
nobody 24689 20925=A0=A0 0 11:47:52 ?=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0:00 /u=
sr/local/apache2/bin/httpd -k start
nobody 24628 20925 =A0=A00 11:46:18 ?=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0:01 /u=
sr/local/apache2/bin/httpd -k start
nobody 24428 20925=A0=A0 0 11:43:39 ?=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0:02 /u=
sr/local/apache2/bin/httpd -k start

Note PID 9750 is lingering, doing nothing according to pfiles and truss, an=
d its timestamp coincides with the last graceful restart (log rotation).=A0=
 Two main differences between this web server and ones that are working inc=
lude:

a) This is Solaris 11 (vs. Solaris 10)
b) I have hardened apache by putting it in a Solaris 11 zone, and I'm start=
ing apache as the "nobody" user with the net_privaddr privilege so it can f=
unction as the parent process.=A0 It talks to Tomcat on another zone and ev=
erything works great (other than the problem described here).

Apache has permission to write to /logs, and /log/apache2 is where I set th=
ese:

JkLogFile /logs/apache2/mod_jk.log
JkShmFile /logs/apache2/jk-runtime-status

And this.
PidFile /logs/apache2/run/httpd.pid


Can anyone think of a reason why children are not being recycled or getting=
 stranded like this over successive graceful restarts?=A0 We do use multipl=
e listeners, so I don't know if I'm dealing with a locking/mutex/serializat=
ion type of issue.=A0 I'm not a C programmer.=A0 There seems to be little i=
nfo out there for Solaris platforms that's recent.=A0=20

I'd be happy to post more info if needed.=A0 I appreciate your time.


Chris


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org