Hello Robert,
Yes it exists a realy good way to got controlled Threadumps. Install
your Tomcat with Java Service Wrapper and
activate the Wrapper JMX Bean with a operation to create a
threaddump and reload the
complete server.
Links:
Wrapper
I definitely do have LD_KERNEL_ASSUME in my environment
If you search for LD_KERNEL and my name on google, you will see that I
was part of a discussion a while back that was glad to find that out.
Daniel Gibby
Oscar Carrillo wrote:
Hi,
Saw your message on the boards.
Did you make sure you
Hi,
Saw your message on the boards.
Did you make sure you have this environment variable set?
On systems that I need it, I put it in my tomcat startup file.
LD_KERNEL_ASSUME=2.2.5
Check out my howto page for my brief notes on threading and it's potential
problems with JVMs and threads.
Howdy,
Can you reproduce this behavior when running with a profiler?
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Daniel Gibby [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 17, 2004 12:21 PM
To: Tomcat Users List
Subject: thread dump analysis
My tomcat 4.1.29
I can't run a profiler on this as it is a live system. I also don't have
the resources to setup another box right now to even test it... I'm in a
fire-fighting mode half of the time, and a village building mode the
rest of the time. (Hmmm. I think I'll stop everything and write a tech
book
Howdy,
My tomcat 4.1.29 instance running J2RE 1.4.1 IBM build
cxia321411-20030930 on RedHat 9 kernel 2.4.18-14
keeps gaining processor usage until finally can't answer requests
successfully.
OK, so you can't profile. I'm not sure a thread dump would be that
useful in this scenario because it
On Tue, February 17, 2004 at 9:20 am, Daniel Gibby wrote:
I did a kill -3 on the process that showed up on top and got a stack
trace... the problem is I have no idea how to analyze the thread dump to
see what is consuming CPU.
I'm sure something must be spinning its wheels, but I don't know
Well, I'd rather not show the world what my java processes are doing in
case there is something proprietary in there.
I'll send it to you personally.
Daniel
David Rees wrote:
On Tue, February 17, 2004 at 9:20 am, Daniel Gibby wrote:
I did a kill -3 on the process that showed up on top and
On Tue, February 17, 2004 1at 2:04 pm, Daniel Gibby wrote:
Well, I'd rather not show the world what my java processes are doing in
case there is something proprietary in there.
I'll send it to you personally.
OK, but it's tough for people to help troubleshoot your issue unless you
do so. ;-)
David Rees wrote, On 2/17/2004 12:43 PM:
On Tue, February 17, 2004 1at 2:04 pm, Daniel Gibby wrote:
Well, I'd rather not show the world what my java processes are doing in
case there is something proprietary in there.
I'll send it to you personally.
OK, but it's tough for people to help
I'm going to try and disable the jcrontab servlets and see if the
problem persists. After that, I'll try and schedule some upgrades.
Thanks for your help David!
Daniel
David Rees wrote:
David Rees wrote, On 2/17/2004 12:43 PM:
On Tue, February 17, 2004 1at 2:04 pm, Daniel Gibby wrote:
Well,
Hi,
Kill -QUIT will work. It will send the output to catalina.out and not
kill the process. It doesn't have to be running in the foreground.
-e
On Mon, 1 Sep 2003, Euan Guttridge wrote:
What is the best method to get a stack dump following a frozen tomcat? I
cannot use kill -QUIT (pid)
kill -3 pid
RS
Manavendra
Gupta To: Tomcat
, December 06, 2002 9:18 PM
To: Tomcat Users List
Subject: Re: Thread dump
kill -3 pid
RS
Manavendra
Gupta To: Tomcat Users List
[EMAIL PROTECTED]
[EMAIL PROTECTED
06, 2002 9:18 PM
To: Tomcat Users List
Subject: Re: Thread dump
kill -3 pid
RS
Manavendra
Gupta To: Tomcat Users
List
[EMAIL PROTECTED]
[EMAIL PROTECTED]
cc
Run it under a JPDA debugger and use something like
- Xrunjdwp:transport=dt_shmem,server=y,suspend=y
so that the JVM stops and waits for debugger commands right away. Then
you could get to the right point in your code, and with any decent
debugger look at the thread dump without needing to send
: Denis Haskin [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 06, 2002 9:53 PM
To: Tomcat Users List
Subject: Re: Thread dump
Run it under a JPDA debugger and use something like
- Xrunjdwp:transport=dt_shmem,server=y,suspend=y
so that the JVM stops and waits for debugger commands right away
: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 06, 2002 8:01 AM
To: Tomcat Users List
Subject: RE: Thread dump
Beg your pardon? would that not actually kill the process, rather than
displaying the thread dump?
And what if one wants to see the thread dump right from
. This is a JVM feature. It can be done anytime
and is a *really* useful debugging feature.
Jeff
-Original Message-
From: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 06, 2002 8:01 AM
To: Tomcat Users List
Subject: RE: Thread dump
Beg your pardon? would
, not System.err. This is a JVM feature. It can be done anytime
and is a *really* useful debugging feature.
Jeff
-Original Message-
From: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 06, 2002 8:01 AM
To: Tomcat Users List
Subject: RE: Thread dump
20 matches
Mail list logo
