André,
André Vila Cova wrote:
And it's possible to know what threads are really doing?
And I don't understand why having the following 3 connectors
maxThreads=400 minSpareThreads=25 maxSpareThreads=75
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
maxThreads=150 minSpareThreads=25
1 . no
2 . lot of users
On 7/12/07, Leon Rosenberg [EMAIL PROTECTED] wrote:
Stupid question:
1. are you using keep alive?
2. how many users are actually on?
regards
Leon
On 7/13/07, Christopher Schultz [EMAIL PROTECTED] wrote:
Ingo,
Ingo Krabbe wrote:
Am Donnerstag, 12. Juli 2007 19:12
And it's possible to know what threads are really doing?
And I don't understand why having the following 3 connectors
maxThreads=400 minSpareThreads=25 maxSpareThreads=75
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
I get error:
Hi!
I've this two processes:
tomcat6404 0.0 2.6 484396 105456 ? Sl 01:05 0:14
/usr/local/java1.5/bin/java -Xms64m -Xmx200m -Xss512k -
Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -
Djava.util.logging.conf
tomcat6555 0.1 3.8 516420 154452 ? Sl 01:09
Take a thread dump of the JVM:
http://java.sun.com/developer/technicalArticles/Programming/Stacktrace/
Bill
On 7/12/07, André Vila Cova [EMAIL PROTECTED] wrote:
Hi!
I've this two processes:
tomcat6404 0.0 2.6 484396 105456 ? Sl 01:05 0:14
/usr/local/java1.5/bin/java -Xms64m
We happend to have similar problems when starting with tomcat. Our main error
was a failing connection to the database, while the connector had it's retry
flag on. So the answer to each request was, trying to connect to a
unconnectable database until the timeout has been reached, which is
More information on catalina.out:
TP-Processor80 daemon prio=1 tid=0xe0370988 nid=0x1c19 runnable
[0xda178000..0xda178fa0]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at
Lot of waits... Could you help me?
http-8085-Processor24 daemon prio=1 tid=0x082f1378 nid=0x19c6 in
Object.wait() [0xde118000..0xde118e20]
at java.lang.Object.wait(Native Method)
- waiting on 0xe619f748 (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at
Am Donnerstag, 12. Juli 2007 19:12 schrieb André Vila Cova:
Lot of waits... Could you help me?
http-8085-Processor24 daemon prio=1 tid=0x082f1378 nid=0x19c6 in
Object.wait() [0xde118000..0xde118e20]
at java.lang.Object.wait(Native Method)
- waiting on 0xe619f748 (a
From: Ingo Krabbe [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat - All threads (200) are currently busy
http-8085-Processor24 daemon prio=1 tid=0x082f1378 nid=0x19c6 in
Object.wait() [0xde118000..0xde118e20]
at java.lang.Object.wait(Native Method)
- waiting
Ingo,
Ingo Krabbe wrote:
Am Donnerstag, 12. Juli 2007 19:12 schrieb André Vila Cova:
http-8085-Processor24 daemon prio=1 tid=0x082f1378 nid=0x19c6 in
Object.wait() [0xde118000..0xde118e20]
at java.lang.Object.wait(Native Method)
- waiting on 0xe619f748 (a
Stupid question:
1. are you using keep alive?
2. how many users are actually on?
regards
Leon
On 7/13/07, Christopher Schultz [EMAIL PROTECTED] wrote:
Ingo,
Ingo Krabbe wrote:
Am Donnerstag, 12. Juli 2007 19:12 schrieb André Vila Cova:
http-8085-Processor24 daemon prio=1 tid=0x082f1378
André Vila Cova wrote:
Hello!
I get lot of times the following error:
SEVERE: All threads (200) are currently *busy*, waiting. *Increase
maxThreads*
**
*Strange is that i've configured in server.xml the following
(maxThreads=400):*
*
You have probably done that for a wrong connector.
I don't think so... I will see..but, why i get the error?
SEVERE: All threads (200) are currently *busy*, waiting. *Increase
On 7/11/07, Mladen Turk [EMAIL PROTECTED] wrote:
André Vila Cova wrote:
Hello!
I get lot of times the following error:
SEVERE: All threads (200) are currently
cause your threads are all busy serving requests (or hanging
somewhere). Perform a thread dump with kill -QUIT and you'll see what
they are doing.
regards
Leon
On 7/11/07, André Vila Cova [EMAIL PROTECTED] wrote:
I don't think so... I will see..but, why i get the error?
SEVERE: All threads
probably some threads are performing database operation
and it takes too long so new threads are being spawned,
the new threads are also taking too long, so newer threads are being spawned.
too much spawning, that is what is causing the limit break.
On 7/12/07, André Vila Cova [EMAIL PROTECTED]
16 matches
Mail list logo