-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi JR,
Based on your description of the problem, as you have looked at
everything else, MaxThreads is the only option you have left us with.
Further below however you let slip that mod_jk is also involved.
Why? This is a really great way to kill per
half of the number of threads,
so that there can be a "big" pile up of work, if our database suddenly
gets a hickup.
Alan M
"Andrew Pliszka" <[EMAIL PROTECTED]>
02/16/2007 11:06 AM
Please respond to
"Tomcat Users List"
To
"Tomcat Users List"
cc
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Subject: Re: Performance tuning parameters
>
> - maxThreads
> The maximum number of http worker threads that tomcat will
> create. This is the limit of the number of concurrent http
> requests that the server
gets a hickup.
Alan M
"Andrew Pliszka" <[EMAIL PROTECTED]>
02/16/2007 11:06 AM
Please respond to
"Tomcat Users List"
To
"Tomcat Users List"
cc
Subject
Re: Performance tuning parameters
Hi,
Do you have any load balancer? I am sorry if this is
Hi,
Do you have any load balancer? I am sorry if this is a trivial
questions, but I have worked with cases that people have no load
balancer and connections are just killing them.
Now, if you do not have a load balancer you might consider NetScaler, it
might lower your number of connections
> From: j r [mailto:[EMAIL PROTECTED]
> Subject: Re: Performance tuning parameters
>
> On a large pageview day, we will overflow the 750 MaxThreads.
Do you have keep-alive enabled for your connectors? If so, the
connections may be staying open beyond their useful life, tying up
I am gleaning from your comments that MaxThreads is the only thing to
tweak. Yes I do really have a connection issue. I have millions and
millions of connection requests on a very small pool of servers. The app
has been tuned constantly over years. I am either bound to buy more servers
or twea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear J,
The focus should be on your application, and configuring everything
thing around that.
If you REALLY have an out of connection problem, increase Max
Threads to 1, but I don't
think that will really help you. The problem is usually
The focus should be on the tomcat tweaking. We get errors in the tomcat
error logs that say tomcat has reached its connection limits. I never said
that it was serving slow. It hits connection limits which means that the
app will not serve any more traffic until connections clear.
If a box defi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear J'
What do you mean you are hitting connection limits?! Are you getting
errors? What are you seeing that makes you think that is slow?
Is there a database involved in this application?
I assume you are running linux on your server, with a 2.
The reason it is hitting its limits is easy: traffic. We easily get enough
website traffic to overflow the connection limits unless I have many boxes
available to serve. I know these can be configured to handle more
connections. I know that we should be able to do this in the tomcat
server. Th
First you should investigate why tomcat is hitting its limits.
Why do you think it does? Which resource is the limit?
Do you have/use any monitoring software? moskito? lambdaprobe? tomcat-manager?
regards
Leon
On 2/15/07, j r <[EMAIL PROTECTED]> wrote:
I have searched for exact documentation on
I have searched for exact documentation on this, and I always find
conflicting info. Therefore I am reaching out to this list. I have the
following info and questions:
- we are running tomcat 5.5.20
- we have the following configs in server.xml:
13 matches
Mail list logo
