[EMAIL PROTECTED] wrote:
Hi
I'm going to be a real pain, but it make no sense now...
Let's see :)
The email has been a team effort in our offices. We have included some
diagrams to help illustrate our understanding or lack off.
Using a simple example:
1/ Assume I have one httpd server (pref
Hi
I'm going to be a real pain, but it make no sense now...
The email has been a team effort in our offices. We have included some
diagrams to help illustrate our understanding or lack off.
Using a simple example:
1/ Assume I have one httpd server (prefork) that can spawn a maximum of
200 childre
[EMAIL PROTECTED] wrote:
If no value is specified then the maximum connectors is default 200.
I assumed that Tomcat would not allow more connections than 200 to be
made to port 8009. Why then do we see more than 200 connections on port
8009 on the httpd and tomcat side. Is this additional connec
Thanks for your patience, things are starting to make more sense now.
>
> Tomcat associates one thread with each incoming connection
> (at least the default connector) independant of it's
> idleness, i.e. even if there is no request coming in. The
> connectionTimeout parameter in the connecto
[EMAIL PROTECTED] wrote:
Hi
This part is still sligtly confusing to me:
We have 575 potential connections that we can except on the httpd
server, according to my understanding mod_jk will load balance these
connections to the tomcat servers. Thus typically 48 connections per
tomcat. This does s
PROTECTED]
> Sent: 29 August 2007 21:29
> To: Tomcat Users List
> Subject: Re: apache getting in "sending reply" state when
> connecting to tomcat
>
> Hi Gerhardus,
>
> you allow 575 parallel requests with Apache. If something
> gets slow and you get more a
Hi Gerhardus,
you allow 575 parallel requests with Apache. If something gets slow and
you get more and more "W" states, this parallelism will really get used.
Each parallel requests needs a connection to your Tomcat (unless it gets
served directly by Apache), and each connection to Tomcat need
monitoring and testing.
I hope that clears up any confusion.
Regards
> -Original Message-
> From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
> Sent: 29 August 2007 14:18
> To: Tomcat Users List
> Subject: RE: apache getting in "sending reply" state whe
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Subject: RE: apache getting in "sending reply" state when
> connecting to tomcat
>
> I forgot to add, that our solution at the moment is to restart apache
> which 9 out of 10 times solves the problems.
Plea
and it
happens very quickly when it does.
Regards
> -Original Message-
> From: Gerhardus Geldenhuis (GTA-LON)
> Sent: 29 August 2007 11:47
> To: users@tomcat.apache.org
> Subject: apache getting in "sending reply" state when
> connecting to tomcat
>
&g
Hi
I'm kind of between a rock and a hard place.
We have a problem in our production system that occurs quite regularly.
Apache's connections all get into a Sending Reply ( W ) state and which
makes the application unresponsive.
We have an apache 2.0.52 fronting 12 tomcat 5.5 all on CentOS 4.5 usi
11 matches
Mail list logo
