Hi all,
I just want to give you an update about my problem
THANKS TO ALL
Felix gave me the final hint... I really had some connection not given back to
the pool, so the connections kept open.. - :-( I thought I checked that.
Since I fixed that and use removeAbandoned there was no
Hi Felix,
1. You are abandoning db connections and thus are draining the pool
(most likely in my eyes)
2. The pool is too small (unlikely, since no work seems to be done other
than waiting for new connections)
3. Lock contention while going through borrowObject (unlikely, since no
thread is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 3/18/13 2:07 AM, David Kumar wrote:
1. You are abandoning db connections and thus are draining the
pool (most likely in my eyes) 2. The pool is too small (unlikely,
since no work seems to be done other than waiting for new
Hey Rainer,
It got stripped by the list. Can you post it somewhere and make the URL
available?
here you go:
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail:
Hey Rainer,
It got stripped by the list. Can you post it somewhere and make the URL
available?
here you go:
http://www.telestar.de/tmp10356/threaddump.txt
thanks
David
-
To unsubscribe, e-mail:
Interesting.
If the problem was too many sockets in CLOSE_WAIT, consider looking at
the connectionLinger setting on your AJP connector's in Tomcat.
Mark
Mhh.. I haven't heard about the options before.. But it sound like a great
idea.. Default is -1. So what would be a good time, one minute?
sry I was wrong default is -1 what menas it is disabled, so I'm fine..?!?
Interesting.
If the problem was too many sockets in CLOSE_WAIT, consider looking at
the connectionLinger setting on your AJP connector's in Tomcat.
Mark
Mhh.. I haven't heard about the options before.. But it sound
close_wait for an AJP connection seen from Tomcat means the other side -
mod_jk - has closed the connection, but not Tomcat.
This is often due to a shorter Timeout on the mod_jk side than on the
Tomcat side. It is not a problem per se, but it is if it happens for too
many connections for a too
Hey,
Please please before restarting take two thread dumps. On Linux/Unix a
kill -QUIT will do that (and write the result to STDOUT, which
depending on your setup likely goes to catalina.out). The QUIT signal
does *not* terminate the JVM, it just quickly writes out the stacks of
all threads. The
Hey Rainer,
attached you can find a Threaddump. Just rename it to .zip.
I'm not sure waht all the stuff at the dump means. but I'm sure you know.. :-)
thanks
Please please before restarting take two thread dumps. On Linux/Unix a
kill -QUIT will do that (and write the result to STDOUT, which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
DAvid,
On 3/13/13 3:01 PM, David Kumar wrote:
Hey,
right no we're having our Problem. I tried gc through jconsole --
no changes and still a lot CLOSE_WAIT. So it is not a GC Problem
and disablereuse doesn't work either.. Any other ideas?
Hi.
Note:
try to avoid top-posting, on this list.
(top-posting means responding on top of the previous message, like I am doing
just now).
The reason why we ask not to do that, is that it forces whoever is reading your message,
to scroll down and try to figure out to what question(s) you are
David Kumar wrote:
Hey,
I'm using:
lsof -u tomcat
example of netstat output on one of our own systems right now :
1) first one
vovm1:~# netstat -t -pan | grep -v ESTAB
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address
Hey André,
André Warnier wrote:
The jsvc process here is the wrapper which wraps the JVM and Tomcat to
allow them to use
orts below 1024 and still run as non-root. For practical purposes,
consider it as tomcat.
As you can see, there are some AJP connections (local port 8009) in the
On 14/03/2013 13:10, David Kumar wrote:
I tried to just restart the Apache, didn't work. As suggested I
tried to use the option -DisableReuse. That did make our situation a
lot more horrible instead of days / week we it took just minutes to
shut all AJP ports down.
Interesting.
If the
Hey,
we just had that problem again. I did that GC trick, it didn't work out well.
I used:
set hosts [list]
lappend hosts {localhost:7008}
lappend hosts {localhost:9008}
# ...add as many as you want...
foreach {host} $hosts {
set parts [split $host :]
set hostname [lindex $parts 0]
set
David Kumar wrote:
Hey,
we just had that problem again. I did that GC trick, it didn't work out well.
I used:
set hosts [list]
lappend hosts {localhost:7008}
lappend hosts {localhost:9008}
# ...add as many as you want...
foreach {host} $hosts {
set parts [split $host :]
set hostname
://www.telestar.de/
-Ursprüngliche Nachricht-
Von: André Warnier [mailto:a...@ice-sa.com]
Gesendet: Mittwoch, 13. März 2013 12:20
An: Tomcat Users List
Betreff: Re: AW: AJP suddenly Stopps acting: ajp on 7009 and 9009 : connections
keept open
David Kumar wrote:
Hey,
we just had
:32
An: Tomcat Users List
Betreff: AW: AW: AJP suddenly Stopps acting: ajp on 7009 and 9009 : connections
keept open
Hey,
I'm really not sure if that tool does anything, because there is no feedback..
Funny: Just a few minutes ago a colleague showed ma a tool called something
like VM monitor
) 6592 / 712 -2829
http://www.telestar.de/
-Ursprüngliche Nachricht-
Von: David Kumar
Gesendet: Mittwoch, 13. März 2013 20:01
An: 'Tomcat Users List'
Betreff: AW: AW: AJP suddenly Stopps acting: ajp on 7009 and 9009 : connections
keept open
Hey,
right no we're having our Problem.
I
David Kumar wrote:
BTW... after a while CLOSE_WAIT changes to can't identify protocol
Huh ?
Which command are you using to see the connections in CLOSE_WAIT state ?
(and maybe paste a sample here)
-
To unsubscribe, e-mail:
Hey Mark,
thanks for reply.
I do have some more questions as the main configuration i not done by myself.
We are using Apache 2.2.16 on Debian. Therefore MaxRequestWorkers is called
MaxClients, isn't it?
Currently it is set to 312. So if we have two tomcats with 200 thread each
MaxClients is
On 12/03/2013 10:58, David Kumar wrote:
Hey Mark,
thanks for reply.
I do have some more questions as the main configuration i not done by myself.
We are using Apache 2.2.16 on Debian. Therefore MaxRequestWorkers is called
MaxClients, isn't it?
Correct.
Currently it is set to 312. So
Hey,
thanks..
I downloaded jmxsh... I keep you guy up to date..
thanks...
Mit freundlichen Grüßen
David Kumar
Softwareentwickler, B. Sc.
Abteilung Infotech - Interaktiv
TELESTAR-DIGITAL GmbH
Am Weiher 14
D-56766 Ulmen
http://www.telestar.de/
-Ursprüngliche Nachricht-
Von:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 3/12/13 6:58 AM, David Kumar wrote:
We are using Apache 2.2.16 on Debian. Therefore MaxRequestWorkers
is called MaxClients, isn't it?
That depends upon the MPM you are using. I have Debian-based systems
with both prefork and worker
25 matches
Mail list logo
