On 18/11/2010 16:23, Caldarale, Charles R wrote:
> Yes, it was identifying it just as 10.0-b19 that was confusing.
Lightbulb: this was the Hotspot VM version number.
p
0x62590808.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
In your full production trace, is there an indication which thread has
the "<0xd50244e8>" lock?
I've debugged similar situations where threads were "blocked waiting
for monitor <0x.>" (getting java.sql.Connections, as it turned
out) -- identifying & examining the thread that had locked that
mo
2010/11/18 Robillard, Greg L :
> I continually get tomcat in this state and can only recover by restarting
> tomcat from the command line. Here is the stack trace that I gathered while
> getting into this state, but it does not make any sense to me.
>
> Tomcat version apache-tomcat-6.0.26
>
> OS
thx
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Thursday, November 18, 2010 10:23 AM
To: Tomcat Users List
Subject: EXTERNAL: RE: Tomcat hung
> From: Robillard, Greg L [mailto:greg.l.robill...@lmco.com]
> Subject: RE: Tomcat hung
> Ja
> From: Robillard, Greg L [mailto:greg.l.robill...@lmco.com]
> Subject: RE: Tomcat hung
> Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
> Java HotSpot(TM) Server VM (build 10.0-b19, mixed mode)
> Last I checked, this is a real VM.
Yes, it was identifying it just as 10
uck.caldar...@unisys.com]
Sent: Wednesday, November 17, 2010 3:58 PM
To: Tomcat Users List
Subject: EXTERNAL: RE: Tomcat hung
> From: Robillard, Greg L [mailto:greg.l.robill...@lmco.com]
> Subject: Tomcat hung
> JVM version is 10.0-b19
No idea what JVM that is; strongly suggest you inst
> From: Robillard, Greg L [mailto:greg.l.robill...@lmco.com]
> Subject: RE: EXTERNAL: Re: Tomcat hung
> "http-8080-200" daemon prio=10 tid=0xcbca9800 nid=0xb5e waiting on condition
> [0xc5dbc000..0xc5dbcea0]
>java.lang.Thread.State: WAITING (parking)
> at
eentrantReadWriteLock$FairSync)
at java.util.concurrent.locks.LockSupport.park(Unknown Source)
I can include more if required.
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Wednesday, November 17, 2010 3:57 PM
To: Tomcat Users List
Subject: EXTERNAL: Re: Tomcat hung
On 17/11/2010 21:50, Robillard, Greg L
> From: Robillard, Greg L [mailto:greg.l.robill...@lmco.com]
> Subject: Tomcat hung
> JVM version is 10.0-b19
No idea what JVM that is; strongly suggest you install a real one (e.g., 6u22)
and see if the problem goes away.
What happens if you run Tomcat directly, not under control o
On 17/11/2010 21:50, Robillard, Greg L wrote:
> I continually get tomcat in this state and can only recover by restarting
> tomcat from the command line. Here is the stack trace that I gathered while
> getting into this state, but it does not make any sense to me.
Production or testing?
Are th
I continually get tomcat in this state and can only recover by restarting
tomcat from the command line. Here is the stack trace that I gathered while
getting into this state, but it does not make any sense to me.
Tomcat version apache-tomcat-6.0.26
OS linux
Jstack trace on tomcat hang.
Tomcat
2010/10/12 Jason Britton :
> (..) I can
> kill -9 it but didn't know if there was any additional information I could
> gather before stopping it.
>
Take a thread dump (or better three dumps in a row). You will know
what Servlet / JSP page is busy and what it is doing.
Best regards,
Konstantin Kol
Hi all,
Tomcat 6.0.29 on 64bit RHEL 5.5. This particular tomcat instance had been
running fine for several days, today hung, stopped responding to requests,
no interesting log messages appeared until calling shutdown.sh. Then the
following appeared:
(appears multiple times at end of log)
ERROR 1
On 10.10.2009 16:45, darinpope wrote:
>
> I'm having the same issue as documented in:
>
> http://www.nabble.com/httpd-JK-Tomcat-hung-connections-td10403182.html
>
> For our situation, we haven't hit the "server reached MaxClients setting"
> issue yet, b
I'm having the same issue as documented in:
http://www.nabble.com/httpd-JK-Tomcat-hung-connections-td10403182.html
For our situation, we haven't hit the "server reached MaxClients setting"
issue yet, but we easily could.
We also have this same config running on a Wind
Rainer,
Thanks for all the info. Hopefully we can get this thing whipped into
shape.
Brantley
Rainer Jung wrote:
Brantley Hobbs wrote:
Rainer,
Thanks for the reply! You're certainly right on the JK version.
Can you be more specific on the "add some more timeouts" comment? Do
you mean
Brantley Hobbs wrote:
Rainer,
Thanks for the reply! You're certainly right on the JK version.
Can you be more specific on the "add some more timeouts" comment? Do
you mean a higher number on connection_pool_timeout?
Have a look at connect_timeout and prepost_timeout. Usually I also use
re
Rainer,
Thanks for the reply! You're certainly right on the JK version.
Can you be more specific on the "add some more timeouts" comment? Do
you mean a higher number on connection_pool_timeout?
Also, should the relationship between httpd's MaxClients and the
connector's maxThreads be 1:1 o
Please update mod_jk. 1.2.6 is *very* outdated. We are now at 1.2.22 and
a lot of things have improved.
After upgrading, check your configuration against the reference guide in
the docs, especially the pages for the worker properties and Apache
directives. You might want to add some more timeo
All,
I have a web application that appears to run just fine at low loads, but
when we ramp up to high load levels, strange things start happening.
The symptoms are a *ton* of apparently hung threads on the tomcat status
page for my JK connector. They're in stage "S", with 0KB sent and 0KB
r
20 matches
Mail list logo
