On 10/05/2012 20:06, Jon Drukman wrote:
I have a commercial app running Tomcat 6. I don't really know anything
about Tomcat, so I need some help with performance tuning.
What happens is that a small percentage of connections from our client
machines just timeout on the connect. I assume
Pid pid at pidster.com writes:
Not really. Did you change the connectionTimeout downwards from the
default 60 secs to 3 secs?
Yes. Although the original version of the file was 20 seconds.
The clients (which I wrote) all have a 3 second connect timeout, so it seemed
to make sense to make
From: Jon Drukman [mailto:j...@cluttered.com]
Subject: Re: Connection timeout
Do you really want to queue up requests, rather than just accepting them
and assigning them to threads?
Well, I assume at some point I may run out of threads.
* 400 is a guess - I've got no idea how many
Caldarale, Charles R Chuck.Caldarale at unisys.com writes:
You keep contradicting yourself: is it a massive box, or can it
only support a miniscule number of threads?
Pick one.
Where did I say it could only support a miniscule number of threads?
I'm sorry if I accidentally gave that
On 10/05/2012 21:40, Jon Drukman wrote:
Caldarale, Charles R Chuck.Caldarale at unisys.com writes:
You keep contradicting yourself: is it a massive box, or can it
only support a miniscule number of threads?
Pick one.
Where did I say it could only support a miniscule number of threads?
Pid pid at pidster.com writes:
The basic point we're making is that you are twiddling the wrong knobs.
OK, good to know.
If you want to handle more connections, increase the size of the thread
pool that handles requests, don't increase the size of the queue of
requests waiting to be handled.
From: Jon Drukman [mailto:j...@cluttered.com]
Subject: Re: Connection timeout
Is there any way to find out how many threads are being used
at a given moment?
Using JConsole or VisualVM would be a good start. Either of those will let you
see what's going on with threads, heap memory
Caldarale, Charles R Chuck.Caldarale at unisys.com writes:
Using JConsole or VisualVM would be a good start.
OK, I'll take a look at those.
There's only one app running on this tomcat, if that makes
any difference.
Does it connect to a database (or any other external resource)?
If
Typing this from my phone so sorry for top posting no other option.
You might also check your garbage collection which can introduce some
pauses in some cases. Just a thought ...
On May 11, 2012 7:26 AM, Jon Drukman j...@cluttered.com wrote:
Caldarale, Charles R Chuck.Caldarale at unisys.com
Have you tried *removeAbandonedTimeout* in connection pool settings ? this
will help to get the connectionb closed if your DB connection waiting more
than a specific amount of time.
On Thu, Nov 12, 2009 at 4:02 AM, André Warnier a...@ice-sa.com wrote:
vichi wrote:
i want to close a connection
vichi wrote:
i want to close a connection if i don't get response back in specific time
(let say in 30 sec) . is there any setting in tomcat for this purpose.
please need an urgent help
It might help if you explained what connection, to what.
And as long as you are doing that, some information
Here are some timeout settings
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html.
Can I ask, what brings you to such requirements. I consider it for
little bit unusual. So what is your case originally? If you tell us,
maybe another solution could be take.
Martin
2009/11/12
thanks Martin for valuable help. In my project i m using embedded tomcat
server 5.5.23 and with http connector . my project is a middle ware
product. so using my product a customer can create his application. since my
product use embedded tomcat server so if a user send any request it comes
to
From: vichi [mailto:vichi...@gmail.com]
Subject: Re: Connection Timeout
does closing a connection will free http thread?
No; the thread does not return to the pool until the webapp logic is completed.
You'll need to have the webapp monitor itself.
- Chuck
THIS COMMUNICATION MAY CONTAIN
14 matches
Mail list logo
