I checked the stuck and i got to a few conclusions:
after tomcat stops receiving messages it will receive some kinds and some
not:
1. if i use http client and write a string directly the tomcat will receive
the data
2. if i use http client and write a stream, the tomcat will not receive the
data
Michal Singer wrote:
Hi.
I am not sure the stuck as any thing to do with the Request Processor
accumulation.
I work with nio connector. I use acceptCount=200 so maybe this is why i
see the 200 Request Processors.
This is the full configuratin i use for connector:
Connector
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michal,
Michal Singer wrote:
I am not sure the stuck as any thing to do with the Request Processor
accumulation.
I work with nio connector. I use acceptCount=200 so maybe this is why i
see the 200 Request Processors.
acceptCount=200 just means
Hi, thanks for the response.
I have A few questions regarding your comment:
1. request processors are equivalent to threads?
2. doesn't nio work with one thread? (I thougt that this thread
configuration is irrelevant since nio works with one thread to receive
requests.)
3. I shouldn't work with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michal,
Michal Singer wrote:
1. request processors are equivalent to threads?
Yes. The only thing that can execute code is a thread. Given your
configuration, it appears that you will have 500 maximum threads.
I am a little unfamiliar with the NIO
Thanks again for the great response.
I am not worried about the request processors any more now that i understand
what they mean.
However, i see that when i use the nio, my application gets stuck. i think
working without nio is better.
I am not sure why, if as i know nio is supposed to improve
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat request processing gets stuck
2. doesn't nio work with one thread? (I thougt that this
thread configuration is irrelevant since nio works with
one thread to receive requests.)
Nope. The NIO connector is just a non
From: Michal Singer [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat request processing gets stuck
I am not sure why, if as i know nio is supposed to improve
performance.
Not true; NIO improves *capacity*, but it will slightly degrade throughput due
to more thread switching.
I am checking my
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
acceptCount=200 just means that the socket will accept 200
clients /in
addition/ to those currently being served by RequestProcessor threads.
The only way to see those waiting clients would be to query
the socket itself (maybe only
Deear Michal,
When i checked the tomcat using jconsole i see that the object
RequestProcessor
accumulates to many objects which i guess may show the cause of this
problem.
Uhm. Could you explain what you mean here? I don't understand what you
are trying to say.
You see too many request
Hi.
I am not sure the stuck as any thing to do with the Request Processor
accumulation.
I work with nio connector. I use acceptCount=200 so maybe this is why i
see the 200 Request Processors.
This is the full configuratin i use for connector:
Connector executor=AgentExecutor useExecutor=true
Michal Singer wrote:
Any ideas why the stuck, what can i do to check this? can there be a problem
with my tomcat configuration?
Almost certainly an application issue.
Take a series of thread dumps (2 or 3) 15 seconds apart and look for
threads that are consistently stuck between dumps.
Mark
Hi,
1. Please explain what do you mean by thread dumps?
2. why do you think this is an application problem?
Thanks, Michal
markt-2 wrote:
Michal Singer wrote:
Any ideas why the stuck, what can i do to check this? can there be a
problem
with my tomcat configuration?
Almost certainly an
From: Michal Singer [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat request processing gets stuck
1. Please explain what do you mean by thread dumps?
You could use Google to find definitions and examples...
The JConsole Threads tab shows the stack trace of individual threads; a thread
dump
Michal Singer wrote:
Hi,
1. Please explain what do you mean by thread dumps?
Google is your friend, as is http://tomcat.markmail.org
2. why do you think this is an application problem?
Years of experience (and if Tomcat had an issue the users list would be
full of posts reporting problems and
I didn't think it is a bug in tomcat. i thought of some problem in
configuration I use for tomcat.
maybe the default configuration is not good for load??
markt-2 wrote:
Michal Singer wrote:
Hi,
1. Please explain what do you mean by thread dumps?
Google is your friend, as is
From: Michal Singer [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat request processing gets stuck
maybe the default configuration is not good for load??
No, it's your webapp. Get the thread dumps and tell us what you see in there.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL
17 matches
Mail list logo
