tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daryl Stultz <da...@6degrees.com>
Subject Re: Apache -> Tomcat connection problem
Date Tue, 24 Feb 2009 22:31:13 GMT
On Tue, Feb 24, 2009 at 4:56 PM, Rainer Jung <rainer.jung@kippdata.de>wrote:

> You need to understand it.
> ...
> You can check your MPM by calling "httpd -V". The output will contain a
> line like
>
>  -D APACHE_MPM_DIR="server/mpm/worker"
>

Server version: Apache/2.2.2
Server built:   Jul 26 2006 11:12:08
Server's Module Magic Number: 20051115:2
Server loaded:  APR 1.2.2, APR-Util 1.2.7
Compiled using: APR 1.2.2, APR-Util 1.2.7
Architecture:   32-bit
Server MPM:     Prefork
  threaded:     no
    forked:     yes (variable process count)
Server compiled with....
 -D APACHE_MPM_DIR="server/mpm/prefork"


>
>  Tomcat AJP connector defaults to 200 for maxThreads. The site has 20
>>
>
> Defaults? I think no, and you haven't configured 200 in your abive config
> snippet.
>

See Christopher's response. Do you know of the implementation being
different than the docs?

>
>
>  applications, each with 2 ProxyPass directives for ports 80 and 443. The
>>
>
> Hmm, not sure, how ports 80 and 443 with HTTP(s) proxying come into play
> now.
>

Me neither, just trying to provide useful setup information. I have a total
of about 40 ProxyPass (mod_proxy_ajp) directives. I don't have any idea how
that impacts things.

>
> What's you platform?


Fedora Core release 5 (Bordeaux)


>
> The command counts LISTEN (the listening socket), the 2 header lines, all
> ESTABLISHED connections (those are the ones you are after) and e.g. also
> TIME_WAIT connections, all of them together. You need to count more
> specific.
>

Yes, I mentally accounted for the header lines. Leaving off the wc -l, I
have never seen anything but ESTABLISHED. I'll keep an eye on it.

>
> Consider upgrading httpd to 2.2.11, because mod_proxy_ajp was very new in
> 2.2.2 and there have been a couple of fixes after that version.
>

I'll look into that.


> First check, whether it is really ESTABISHED connections. Then configure
> reasonable timeouts as described in the mod_proxy documentation and an
> additional connectionTimeout for Tomcat.
>

This is the part where expert advice comes in. I don't have any idea what
"reasonable timeouts" are and the docs don't give a decent way to calculate
it.

Thanks.

-- 
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@6degrees.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message