Chris
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Friday, February 03, 2017 11:08 AM
> To: Tomcat Users List
> Subject: Re: Increasing maxThreads results in more "Connection refused"
> errors?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 2/3/17 11:17 AM, john.e.gr...@wellsfargo.com.INVALID wrote:
> I'm doing some scalability testing of an app in Tomcat 7.0.73.
>
> Some relevant connector config details: maxThreads=80
> maxKeepAliveRequests=100 keepAliveT
All,
I'm doing some scalability testing of an app in Tomcat 7.0.73.
Some relevant connector config details:
maxThreads=80
maxKeepAliveRequests=100
keepAliveTimeout=1
maxConnections unspecified (defaults to maxThreads according to the docs)
acceptCount unspecified (100 according to the docs
to increase the
Executors thread count(maxThreads for Executor element) but also
need to increase the Connectors thread count(maxThreads for
Connector element). This behavior is not actually clearly
captured in tomcat documentation says
1. The rules: http://tomcat.apache.org/lists.html#tomcat
On Friday, January 24, 2014 7:04 PM, Konstantin Kolinko
knst.koli...@gmail.com wrote:
2014/1/24 akshay hiremath akshay...@yahoo.com:
Through some trials found that its not enough to increase the Executors
thread count(maxThreads for Executor element) but also need to increase
Through some trials found that its not enough to increase the Executors thread
count(maxThreads for Executor element) but also
need to increase the Connectors thread count(maxThreads for Connector
element). This behavior is not actually clearly captured in tomcat
documentation says
2014/1/24 akshay hiremath akshay...@yahoo.com:
Through some trials found that its not enough to increase the Executors
thread count(maxThreads for Executor element) but also need to increase the
Connectors thread count(maxThreads for Connector element). This behavior is
not actually clearly
Executor name=tomcatThreadPool
namePrefix=${server.service-Catalina.executor-tomcatThreadPool.namePrefix}
maxThreads=${server.service-Catalina.executor-tomcatThreadPool.maxThreads}
minSpareThreads=${server.service-Catalina.executor
On 23/01/2014 13:30, akshay hiremath wrote:
Why tomcat is not able to have more than 200 active Threads (parallel
threads) processng my requests?
It can. The issue is that the combination of the requests you are making
(which you fail to describe), your load testing framework (which you
fail
We have this HP load runner running a load of requests on this system. We don't
see request rejected by Tomcat but if I monitor the activeCount attribute of
Mbean Catalina:type=Executor,name=tomcatThreadPool over the period of test
why the activeCount is not going above 200. if I continuously
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
akshay,
On 1/23/14, 9:07 AM, akshay hiremath wrote:
We have this HP load runner running a load of requests on this
system. We don't see request rejected by Tomcat but if I monitor
the activeCount attribute of Mbean
mohan.radhakrish...@polarisft.com wrote:
Yes. That is probably the capacity planning part that involves think time
analysis and concurrency.
What Were They Thinking:
Modeling Think Times for Performance Testing
Tom Wilson
from Computer Measurement Group is what I plan to refer to. But don't
On 9/24/2013 12:11 AM, mohan.radhakrish...@polarisft.com wrote:
Yes. That is probably the capacity planning part that involves think time
analysis and concurrency.
What Were They Thinking:
Modeling Think Times for Performance Testing
Tom Wilson
from Computer Measurement Group is what I plan to
David kerber wrote:
On 9/24/2013 12:11 AM, mohan.radhakrish...@polarisft.com wrote:
Yes. That is probably the capacity planning part that involves think time
analysis and concurrency.
What Were They Thinking:
Modeling Think Times for Performance Testing
Tom Wilson
from Computer Measurement
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 9/24/13 7:47 AM, David kerber wrote:
On 9/24/2013 12:11 AM, mohan.radhakrish...@polarisft.com wrote:
Yes. That is probably the capacity planning part that involves
think time analysis and concurrency.
What Were They Thinking:
Yes. I understand the need for capacity planning.
It probably involves concurrency, think time analysis etc. I was wondering
if maxThreads and MaxClients are the same value. In a worker mpm
MaxClients is the Apache setting and maxThreads is the JBoss setting.
Moreover how does a figure of 200
Do not top-post. It makes it difficult to follow the conversation, who answers
to what etc.
From: Daniel Mikusa dmik...@gopivotal.com
To: Tomcat Users List users@tomcat.apache.org
Date: 09/20/2013 07:10 PM
Subject:Re: MaxClients and maxThreads
On Sep 20, 2013, at 9:27 AM
and maxThreads
On Sep 20, 2013, at 9:27 AM, mohan.radhakrish...@polarisft.com wrote:
And that was a top post you just posted.
: MaxClients and maxThreads
On Sep 20, 2013, at 9:27 AM, mohan.radhakrish...@polarisft.com wrote:
And that was a top post you just posted.
Yes, but it was difficult to do otherwise in this case, and it was a good
illustration
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 9/21/13 9:53 AM, chris derham wrote:
To add to what Daniel is saying, here is a little graphic
representation, for one single client browser :
(browser) -- HTTP -- (httpd + mod_jk) -- AJP -- (tomcat) --
(webapp) (1) | |- (local
: 09/20/2013 07:10
PM Subject:Re: MaxClients and maxThreads
On Sep 20, 2013, at 9:27 AM, mohan.radhakrish...@polarisft.com
wrote:
Is this a hard limit ?
No.
So if there are 4 cores there can only be 800 concurrent
clients. None of our banks is calculating this like
and concurrent connections
estimate I have to use 800 threads for a 4-core system if we have only
Apache there.
Mohan
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Date: 09/23/2013 06:14 PM
Subject:Re: MaxClients and maxThreads
further limits the
threads.
Appreciate any help.
Hi,
I am following the instructions in
https://access.redhat.com/site/articles/15786 to tune MaxClients in
httpd.conf and maxThreads in JBoss Tomcat.
The recommended value of maxThreads is 200 per CPU, so here we assume
the server
To add to what Daniel is saying, here is a little graphic representation,
for one single client browser :
(browser) -- HTTP -- (httpd + mod_jk) -- AJP -- (tomcat) -- (webapp)
(1)
|
|- (local resources) (2)
When the browser sends a
...@polarisft.com
To: users@tomcat.apache.org
Date: 09/19/2013 05:56 PM
Subject:MaxClients and maxThreads
Hi,
I am following the instructions in
https://access.redhat.com/site/articles/15786 to tune MaxClients in
httpd.conf and maxThreads in JBoss Tomcat.
The recommended value
the
threads.
Appreciate any help.
Hi,
I am following the instructions in
https://access.redhat.com/site/articles/15786 to tune MaxClients in
httpd.conf and maxThreads in JBoss Tomcat.
The recommended value of maxThreads is 200 per CPU, so here we assume
the server is a single
Hi,
I am following the instructions in
https://access.redhat.com/site/articles/15786 to tune MaxClients in
httpd.conf and maxThreads in JBoss Tomcat.
The recommended value of maxThreads is 200 per CPU, so here we assume
the server is a single core machine. If it had
been quad core
I am using the correct server.xml.
In the version 5.5.36 the maxThreads of 0 has no effect due to this code in
org.apache.tomcat.util.net.PoolTcpEndpoint
public void setMaxThreads(int maxThreads) {
if( maxThreads 0)
tp.setMaxThreads(maxThreads);
}
So what I observe is correct
Hermes Flying wrote:
I am using the correct server.xml.
In the version 5.5.36 the maxThreads of 0 has no effect due to this code in
org.apache.tomcat.util.net.PoolTcpEndpoint
public void setMaxThreads(int maxThreads) {
if( maxThreads 0)
tp.setMaxThreads(maxThreads);
}
So
On Jan 16, you wrote this :
Hermes Flying wrote:
Hi,
I am using Tomcat 6 (I think it is version 33 but will double check)
And JVM is Java 6 from IBM
Do you need exact versions?
And you haven't provided any other version number since then.
So why are you quoting Tomcat 5.5.36 code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hermes,
On 1/25/13 4:16 AM, Hermes Flying wrote:
I am using the correct server.xml. In the version 5.5.36 the
maxThreads of 0 has no effect due to this code in
org.apache.tomcat.util.net.PoolTcpEndpoint
You said you were using Tomcat 6. Now
this in 6 and he
said the browser stuck.
I did not notice that.
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, January 25, 2013 9:34 PM
Subject: Re: Fw: Can not understand how maxThreads
On 25/01/2013 19:58, Hermes Flying wrote:
Hi, I actually deploy in 2 servers one in 6 and one in 5. I noticed
the same behavior described (that was not believed). I did not aim
in taking anyone's time. All I wanted to do is verify the
functionality using really small values. In a previous mail
Hermes Flying wrote:
Hi,
So is there an explanation for this? All I am interested is make sure that
after a limit, clients attempted to connect are stopped based on my
configuration on maxThreads and accept count.
But I can not figure out how this works.
(This all being explained
-
maxThreads=150 minSpareThreads=4/
--
!-- A Connector represents an endpoint by which requests are received
and responses are returned. Documentation at :
Java HTTP Connector: /docs/config/http.html (blocking non-blocking)
Java AJP Connector: /docs/config
/config/http.html
says this :
quote
maxThreads
The maximum number of request processing threads to be created by this Connector, which
therefore determines the maximum number of simultaneous requests that can be handled. If
not specified, this attribute is set to 200. If an executor
From: André Warnier a...@ice-sa.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Thursday, January 24, 2013 7:14 PM
Subject: Re: Fw: Can not understand how maxThreads of Connectors works
Hermes Flying wrote:
Hi,
I don't see how this answers my issue
unlikely that processing 0 requests is what a normal user would
want, the Tomcat developers have coded this so that an obviously
nonsensical value of 0 would result in the default (of 200) being
applied.
That last one is not true: the code will happily accept maxThreads=0
but then will throw
.
That last one is not true: the code will happily accept maxThreads=0
but then will throw an exception when the connector tries to actually
start its Executor.
I suspect Hermes is editing some unrelated server.xml file: his
observations seem totally in-line with that hypothesis.
Hermes
Hi,
So is there an explanation for this? All I am interested is make sure that
after a limit, clients attempted to connect are stopped based on my
configuration on maxThreads and accept count.
But I can not figure out how this works.
From: Hermes Flying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hermes,
On 1/23/13 5:25 PM, Hermes Flying wrote:
So is there an explanation for this? All I am interested is make
sure that after a limit, clients attempted to connect are stopped
based on my configuration on maxThreads and accept count. But I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hermes,
On 1/21/13 11:17 AM, Hermes Flying wrote:
The web application works.I can not see any issue. What does this
mean?
My guess is that Tomcat isn't using the configuration file you are
modifying.
- -chris
-BEGIN PGP SIGNATURE-
On 21/01/2013 07:07, Hermes Flying wrote:
Hi,
Is there any update on this? I don't see any problem setting maxThreads=0
And if you try making a request with a Tomcat instance that uses that
configuration?
Mark
Thank you
- Forwarded Message -
From: Hermes Flying flyingher
The web application works.I can not see any issue. What does this mean?
From: Mark Thomas ma...@apache.org
To: Tomcat Users List users@tomcat.apache.org
Sent: Monday, January 21, 2013 11:06 AM
Subject: Re: Fw: Can not understand how maxThreads of Connectors
Hi,
Is there any update on this? I don't see any problem setting maxThreads=0
Thank you
- Forwarded Message -
From: Hermes Flying flyingher...@yahoo.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, January 18, 2013 8:55 AM
Subject: Re: Can not understand how maxThreads
terminology)
I meant that the client would get a failure in the TCP attempt to
connect.
Okay.
Also I used maxThreads=0 and the server worked fine. Did not see
any problem in my applications. Did not check the logs though. I
assumed that perhaps 0 would be set to some default value. Can not
answer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 1/17/13 3:32 AM, André Warnier wrote:
Quite a few messages ago, I asked the OP if he could copy/paste
his server.xml.
Yes. Getting information from the OP seems to be difficult.
The reason was that if his config uses an Executor,
=org.apache.catalina.UserDatabase
description=User database that can be updated and saved
factory=org.apache.catalina.users.MemoryUserDatabaseFactory
pathname=conf/tomcat-users.xml /
/GlobalNamingResources
Service name=Catalina
Connector port=8443 maxThreads=5000
Hi Chris,
Tried with this simple server.xml and maxThreads=0 but I did not see any kind
of errors.Attached the catalina logs
?xml version='1.0' encoding='utf-8'?
Server port=8005 shutdown=SHUTDOWN
!--APR library loader. Documentation at /docs/apr.html --
Listener className
Hermes Flying wrote:
Hi,
I am trying to understand how the maxThreads attribute of Connectors works. I
did some tests in order to configure Tomcat to limit the number of concurrent
client requests(as asked in my previous mail).
Did the following trivial configuration.
maxThreads=1
: Re: Can not understand how maxThreads of Connectors works
Hermes Flying wrote:
Hi,
I am trying to understand how the maxThreads attribute of Connectors works. I
did some tests in order to configure Tomcat to limit the number of concurrent
client requests(as asked in my previous mail).
Did
-sa.com
Sent: Wednesday, January 16, 2013 6:29 PM
Subject: Re: Can not understand how maxThreads of Connectors works
Hi,
I am using Tomcat 6 (I think it is version 33 but will double check)
And JVM is Java 6 from IBM
Do you need exact versions?
From: André Warnier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hermes,
On 1/16/13 11:01 AM, Hermes Flying wrote:
I am trying to understand how the maxThreads attribute of
Connectors works. I did some tests in order to configure Tomcat to
limit the number of concurrent client requests (as asked in my
.
Also I used maxThreads=0 and the server worked fine. Did not see any problem in
my applications. Did not check the logs though. I assumed that perhaps 0 would
be set to some default value. Can not answer about your observation.It also
makes me wonder.
Finally concerning my test setup, I need
that the client would get a failure in the TCP attempt to
connect.
Okay.
Also I used maxThreads=0 and the server worked fine. Did not see
any problem in my applications. Did not check the logs though. I
assumed that perhaps 0 would be set to some default value. Can not
answer about your observation
the forms right away after they got the emails and together
with the mailing process (that requires DB use to get email
addresses) is exhausting the maxthreads connections (300 as of
yesterday which I have increased to 400).
Are you running out of request processors (Connector
maxThreads
or metrics) that people tend to fill the forms right away after
they got the emails and together with the mailing process (that requires
DB use to get email addresses) is exhausting the maxthreads connections
(300 as of yesterday which I have increased to 400).
I assume it's not going to be easy
users to
log on the webapp and fill in some forms. It seems (without any logs or
metrics) that people tend to fill the forms right away after they got the
emails and together with the mailing process (that requires DB use to get
email addresses) is exhausting the maxthreads connections (300
the maxthreads connections (300 as of yesterday which
I have increased to 400).
How many emails does it send?
Around 1000 a minute
I assume it's not going to be easy to determine what is the cause of the
issue but which tools can I use?
It might just be simple maths. If you send more than
the forms
right away after they got the emails and together with the mailing
process (that requires DB use to get email addresses) is exhausting
the maxthreads connections (300 as of yesterday which I have
increased to 400).
Are you running out of request processors (Connector maxThreads
email addresses) is exhausting
the maxthreads connections (300 as of yesterday which I have
increased to 400).
Are you running out of request processors (Connector maxThreads) or
are you running out of database connections (Resource maxActive)?
MaxThreads
Yes: log the timestamp of each access
AM
Subject: Re: Tomcat 6.0.35 -crossing maxThreads configured count
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
G,
On 1/23/12 8:44 AM, gnath wrote:
Recently i happened to check our access logs when the server hung
and stopped responding. We were printing the thread number in the
logs and i
Hi all,
We have Tomcat 6.0.35 in our production Environment running on Linux, and we
have configured to use tomcatThreadPool with maxThreads=500 and
minSpareThreads=50 with default connectionTimeout(which is 6 sec). We have
two connectors (http and ssl) It has been giving some problems
On Mon, 2012-01-23 at 05:44 -0800, gnath wrote:
Hi all,
We have Tomcat 6.0.35 in our production Environment running on Linux, and we
have configured to use tomcatThreadPool with maxThreads=500 and
minSpareThreads=50 with default connectionTimeout(which is 6 sec).
We have two
gnath wrote:
Hi all,
We have Tomcat 6.0.35 in our production Environment running on Linux, and we
have configured to use tomcatThreadPool with maxThreads=500 and
minSpareThreads=50 with default connectionTimeout(which is 6 sec).
Which would be about 16 hours. I am not sure
On 23/01/2012 14:06, Daniel Mikusa wrote:
On Mon, 2012-01-23 at 05:44 -0800, gnath wrote:
Hi all,
We have Tomcat 6.0.35 in our production Environment running on Linux, and we
have configured to use tomcatThreadPool with maxThreads=500 and
minSpareThreads=50 with default connectionTimeout
André Warnier wrote:
gnath wrote:
Hi all,
We have Tomcat 6.0.35 in our production Environment running on Linux,
and we have configured to use tomcatThreadPool with maxThreads=500 and
minSpareThreads=50 with default connectionTimeout(which is 6 sec).
Which would be about 16 hours. I am
Thanks Dan and p
Sure, i will collect the thread dump once it happens again. Mean while here my
server.xml content related to executor and connectors:
Executor name=tomcatThreadPool
namePrefix=catalina-exec-
maxThreads=500
minSpareThreads=50
namePrefix=catalina-exec-
maxThreads=500
minSpareThreads=50/
Connector enableLookups=false executor=tomcatThreadPool port=http
port
protocol=HTTP/1.1
connectionTimeout=2
redirectPort=https port address=ip address
namePrefix=catalina-exec-
maxThreads=500
minSpareThreads=50/
Connector enableLookups=false executor=tomcatThreadPool port=http
port
protocol=HTTP/1.1
connectionTimeout=2
redirectPort=https port address=ip
Please ignore my previously sent edited configuration. Here is what our
configurations are without editing them :
Executor name=tomcatThreadPool
namePrefix=catalina-exec-
maxThreads=500
minSpareThreads=50/
Connector enableLookups=false
-
maxThreads=500
minSpareThreads=50/
Connector enableLookups=false executor=tomcatThreadPool port=http
port protocol=HTTP/1.1
connectionTimeout=2
redirectPort=https port address=ip address/
Connector enableLookups=false
: Monday, January 23, 2012 6:44 AM
Subject: Re: Tomcat 6.0.35 -crossing maxThreads configured count
On Mon, 2012-01-23 at 06:24 -0800, gnath wrote:
Thanks Dan and p
Sure, i will collect the thread dump once it happens again. Mean while here
my server.xml content related to executor and connectors
gnath wrote:
Please ignore my previously sent edited configuration. Here is what our
configurations are without editing them :
Executor name=tomcatThreadPool
namePrefix=catalina-exec-
maxThreads=500
minSpareThreads=50/
Connector
gnath wrote:
Please ignore my previously sent edited configuration. Here is what our
configurations are without editing them :
Executor name=tomcatThreadPool
namePrefix=catalina-exec-
maxThreads=500
minSpareThreads=50/
Connector
at 500). I was under impression that the threads will
be shared among the connectors and max it can go to 500. Could you
please explain why im seeing very high number than configured? Is
that maxThreads value per connector?
Since you are using a thread pool, threads are probably expiring after
On 01/04/2011 06:58, Kaushal Shriyan wrote:
Hi,
What are the implications or issues if maxThreads are increased from the
default 150 to 300 threads. Are there any performance issues ?
Yes, may be at risk of improving performance.
p
I am using TC 5.5.27 , Ubuntu Linux Server 8.04 , Sun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 4/1/2011 6:43 AM, Pid wrote:
On 01/04/2011 06:58, Kaushal Shriyan wrote:
Hi,
What are the implications or issues if maxThreads are increased from the
default 150 to 300 threads. Are there any performance issues ?
Yes, may be at risk
Hi,
What are the implications or issues if maxThreads are increased from the
default 150 to 300 threads. Are there any performance issues ?
I am using TC 5.5.27 , Ubuntu Linux Server 8.04 , Sun Java 1.6.0 Update 24
Please suggest/guide.
Thanks and Regards,
Kaushal
Hi all users.
I'm using Tomcat 6.0.29 and I have changed to maxThreads parameter to 300 from
200 and restart tomcat but I have still getting below error in catalina log.
Could you please help me,why this parameter was not activated ? so what should
i do for active this parameter ? If you help
2011/1/31 Semih Gokalp sem...@hotmail.com:
I'm using Tomcat 6.0.29 and I have changed to maxThreads parameter to 300
from 200 and restart tomcat but I have still getting below error in catalina
log.
server.xml
Connector port=8080 protocol=HTTP/1.1 server=NONE secure=true
Hi all users.
I'm using Tomcat 6.0.29 and I have changed to maxThreads parameter to 300 from
200 and restart tomcat but I have still getting below error in catalina log.
Could you please help me,why this parameter was not activated ? so what should
i do for active this parameter ? If you help
maxThreads
From: knst.koli...@gmail.com
To: users@tomcat.apache.org
2011/1/31 Semih Gokalp sem...@hotmail.com:
I'm using Tomcat 6.0.29 and I have changed to maxThreads parameter to 300
from 200 and restart tomcat but I have still getting below error in
catalina log.
server.xml
sure that it is not an old message?
Yes,I am sure tomcat restart time is older then ThreadPool logFull output
time.You can check restart time from above.
Thanks again.
Date: Mon, 31 Jan 2011 13:31:20 +0300
Subject: Re: About maxThreads
From: knst.koli...@gmail.com
To: users@tomcat.apache.org
2011/1/31 Semih Gokalp sem...@hotmail.com:
I hope this is that you want output.The below output was printed in
catalina.log when I start tomcat.If you want further informations,I can send.
(...)
Jan 28, 2011 6:35:34 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote
value that was set for
connectors ?
Semih Gokalp
Istanbul/Turkiye
Date: Mon, 31 Jan 2011 15:18:37 +0300
Subject: Re: About maxThreads
From: knst.koli...@gmail.com
To: users@tomcat.apache.org
2011/1/31 Semih Gokalp sem...@hotmail.com:
I hope this is that you want output.The below output
2011/1/31 Semih Gokalp sem...@hotmail.com:
If it is possible,how can i see real time maxThread value that was set for
connectors ?
/manager/jmxproxy?qry=*%3Atype%3DThreadPool%2C*
In Tomcat 6.0.30+ that will require a role of manager (deprecated)
or of manager-jmx (new since 6.0.30).
Best
Thanks for all useful information Konstantin.
Date: Mon, 31 Jan 2011 16:07:16 +0300
Subject: Re: About maxThreads
From: knst.koli...@gmail.com
To: users@tomcat.apache.org
2011/1/31 Semih Gokalp sem...@hotmail.com:
If it is possible,how can i see real time maxThread value that was set
On 29/11/2010 22:21, Sylvain Laurent wrote:
On 29 nov. 2010, at 15:01, Mark Thomas wrote:
On 29/11/2010 13:57, sol myr wrote:
Hi,
I'm new to Tomcat management, and would appreciate help on the 'maxThreads'
property of the Http Connector:
1) Please tell if I understood correctly
Hi,
I'm new to Tomcat management, and would appreciate help on the 'maxThreads'
property of the Http Connector:
1) Please tell if I understood correctly:
Suppose I configure 'maxThreads=100', and 130 users try to simultaneously
access my Tomcat - then 100 users will be served immediately
Sorry, correction: on section 2, I meant to say e.g. 30 on the above example
(wrote '50' by mistake). Thanks again.
--- On Mon, 11/29/10, sol myr solmy...@yahoo.com wrote:
From: sol myr solmy...@yahoo.com
Subject: [Tomcat] Can I see if 'maxThreads' is exceeded?
To: users@tomcat.apache.org
Date
On 29/11/2010 13:57, sol myr wrote:
Hi,
I'm new to Tomcat management, and would appreciate help on the 'maxThreads'
property of the Http Connector:
1) Please tell if I understood correctly:
Suppose I configure 'maxThreads=100', and 130 users try to simultaneously
access my Tomcat
Mark Thomas wrote:
On 29/11/2010 13:57, sol myr wrote:
Hi,
I'm new to Tomcat management, and would appreciate help on the 'maxThreads'
property of the Http Connector:
1) Please tell if I understood correctly:
Suppose I configure 'maxThreads=100', and 130 users try to simultaneously access my
André and Mark - thanks very much for the quick replies.
--- On Mon, 11/29/10, André Warnier a...@ice-sa.com wrote:
From: André Warnier a...@ice-sa.com
Subject: Re: [Tomcat] Can I see if 'maxThreads' is exceeded?
To: Tomcat Users List users@tomcat.apache.org
Date: Monday, November 29, 2010, 6:21
On 29 nov. 2010, at 15:01, Mark Thomas wrote:
On 29/11/2010 13:57, sol myr wrote:
Hi,
I'm new to Tomcat management, and would appreciate help on the 'maxThreads'
property of the Http Connector:
1) Please tell if I understood correctly:
Suppose I configure 'maxThreads=100', and 130
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott,
On 8/24/2010 12:12 PM, Scott Hamilton wrote:
You've got two connectors in that server.xml, and one of them is AJP
without any real other configuration parameters. If memory serves the
thread limit when not specified for a connector is
I have an issue where my Tomcat server is going down quite often with the
following message:
Aug 19, 2010 12:03:21 PM org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads
(200) or check the servlet status
Aug 20, 2010 4:47:20
From: White, Federico (Federico) [mailto:whi...@avaya.com]
Subject: Apache 5.x issue - SEVERE: All threads (200) are currently
busy, waiting. Increase maxThreads
First off, it's not Apache 5.x, it's Tomcat 5.x. The term Apache refers to
the Apache Software Foundation, for which Tomcat
the out of the box server.xml file)
?xml version=1.0 encoding=ISO-8859-1?
Server port=8006 shutdown=SHUTDOWN
Service name=website
Connector port=9602 maxThreads=100 maxSpareThreads=50
minSpareThreads=10/
Connector port=9642 protocol=AJP/1.3 /
Engine name
busy, waiting. Increase maxThreads
Hi again,
Since my first email might have not be that clear I'll re phrase it,
I'm currently running a Tomcat webserver for an application that my
company uses.
It run's on windows server 2003, and the startup command was customized
for our application
1 - 100 of 192 matches
Mail list logo
