Thanks for all the tips. Today I tried the AJP connector and we had no
problems. After watching a very informative presentation on tomcat
performance tuning by Filip Hanik and reading the docs, I am guessing
this was more of a function of the higher default max thread count of
the ajp connector.
From: feedly team [mailto:feedly...@gmail.com]
Subject: Re: apache/tomcat communication issues (502 response)
I have generated stack dumps throughout the day and
practically all running threads are doing socket i/o.
almost none are performing application logic.
When you catch threads
Caldarale, Charles R wrote:
[...]
When you catch threads doing socket I/O, they are almost always waiting for
input from the client. If you're using keep-alives (highly likely), that's the
normal state of a thread. This likely means you don't have enough requests
coming in to keep the
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: apache/tomcat communication issues (502 response)
That is because a KeepAlive connection will keep a server child (or
thread) tied to that particular client connection, until the KeepAlive
expires, probably doing nothing most
Caldarale, Charles R wrote:
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: apache/tomcat communication issues (502 response)
That is because a KeepAlive connection will keep a server child (or
thread) tied to that particular client connection, until the KeepAlive
expires, probably
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: apache/tomcat communication issues (502 response)
You seem to imply that idle threads use less resources in the 64-bit
world than (presumably) in a lesser-number-of-bit world.
In a 64-bit environment, each thread uses *relatively
We are running apache and tomcat on the same machine (using the http
connector) and logging requests in both. Occasionally (maybe 1% of
requests) we see 502 response in the apache log spread fairly evenly
throughout the day. these requests don't appear in the tomcat log
produced by the access
feedly team wrote:
[...]
using netstat, i see a moderate number (~80) of tomcat's sockets in
the CLOSE_WAIT state, not sure if this is relevant.
Approximately, because I am not sure I have this really understood yet :
a TCP CLOSE_WAIT state happens when the writing side of a TCP connection
From: André Warnier [mailto:a...@ice-sa.com]
a TCP CLOSE_WAIT state happens when the writing side of a TCP
connection
has finished writing and (nicely) closes its side of the socket to
indicate the fact,
Yes.
but the reading side of the connection does not read
what is left in the
Hi Andre
André Warnier wrote:
feedly team wrote:
[...]
using netstat, i see a moderate number (~80) of tomcat's sockets in
the CLOSE_WAIT state, not sure if this is relevant.
Approximately, because I am not sure I have this really understood yet
: a TCP CLOSE_WAIT state happens when the
Alan Chaney wrote:
Hi Andre
Hi. And thanks, to Peter also.
As this might start to look like a thread hijack, I'll repost with a new
CLOSE_WAIT subject to continue this discussion.
-
To unsubscribe, e-mail:
On 08.04.2009 08:23, feedly team wrote:
We are running apache and tomcat on the same machine (using the http
connector) and logging requests in both. Occasionally (maybe 1% of
requests) we see 502 response in the apache log spread fairly evenly
throughout the day. these requests don't appear
12 matches
Mail list logo
