register the Mbean
Peter
Patrick Lacson schrieb:
Spoke too soon.. :(
Our tomcat is installed using the tomcat.exe service installer that
ships with the tomcat 4.1.x series. This "Stack Trace" tool cannot do
a thread dump on the process id of tomcat.exe
-Patrick
On 4/25/05, Patrick Lacs
Spoke too soon.. :(
Our tomcat is installed using the tomcat.exe service installer that
ships with the tomcat 4.1.x series. This "Stack Trace" tool cannot do
a thread dump on the process id of tomcat.exe
-Patrick
On 4/25/05, Patrick Lacson <[EMAIL PROTECTED]> wrote:
> p
acktrace/app/launch.jnlp
>
> let me know if it helped..
> -Anoop
>
> On 4/22/05, Patrick Lacson <[EMAIL PROTECTED]> wrote:
> > If I run tomcat as a windows service, what is the best way to get a VM
> > thread dump? From a command window it's pretty easy with the
This looks promising.
the application detects VM instances and can pull a thread-dump on
that instance.. i'll try it on monday and see how it goes.
thanks!
On 4/22/05, Anoop kumar V <[EMAIL PROTECTED]> wrote:
> Patrick,
>
> I am not sure if this will help you but it i
mcat as a windows service, what is the best way to get a VM
> thread dump? From a command window it's pretty easy with the
> Control-Break command.. what are my options for doing the equivalent
> from a running tomcat windows service?
If I run tomcat as a windows service, what is the best way to get a VM
thread dump? From a command window it's pretty easy with the
Control-Break command.. what are my options for doing the equivalent
from a running tomcat windows service?
Thanks,
Pa
xample.zip
regards
Peter
Robert Herold schrieb:
I've installed tomcat as a Windows service. Is there any way to trigger the
JVM to produce a thread dump?
I understand how to do so when Tomcat is run in a console window
(cntl-break), but in this case it has to be run as a service.
Thanks for any poi
I've installed tomcat as a Windows service. Is there any way to trigger the
JVM to produce a thread dump?
I understand how to do so when Tomcat is run in a console window
(cntl-break), but in this case it has to be run as a service.
Thanks for any pointers...
-- bob
--
Robert H
Hola,
>I did a thread dump (SIG-QUIT) on both the JRun and Tomcat environments
>during the "refresh button load test" and the differences are
>significant.
The differences in internal thread management between any two servers
are likely to be significant.
>Tomcat: Java C
Our server does recover (whether JRun or Tomcat), but as Pepijn points
out, the thread management during the behaviour is the main concern.
I did a thread dump (SIG-QUIT) on both the JRun and Tomcat environments
during the "refresh button load test" and the differences are
s
ccessfully.
>
> The machine has a relatively light load.
>
> 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 spi
ocess 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 how to
tell... I can just see that when I run top my tomcat process has 9
ote:
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. ;-)
I had a look at Daniel's thread du
people to help troubleshoot your issue unless you
do so. ;-)
I had a look at Daniel's thread dump, it did not appear to be an issue
with Tomcat, but rather an issue with either some jcrontab threads or a
JVM/OS issue as he is running the IBM 1.4.1 JDK on a stock
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.
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 how to
tell... I can just see that when I run top my tomcat process has 99.9 %
of the CPU and the load
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
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
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 instance run
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 analys
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 how to
tell... I can just see that when I run top my tomcat process has 99.9 %
of the CPU and the load average is
L PROTECTED]
>Sent: Friday, December 12, 2003 7:56 PM
>To: [EMAIL PROTECTED]
>Subject: Need help to study thread dump
>
>
>Hi,
>
>My app is running on bes 5.1
>
>App sometime stops responsding and i have to restart my server. Below
is
>some portion of thread dum
Hi,
My app is running on bes 5.1
App sometime stops responsding and i have to restart my server. Below is some portion
of thread dump which i got for the app
"VBJ ThreadPool Worker" daemon prio=5 tid=0x14f1148 nid=0xad70 waiting for monitor
entry [e767d000..e76
Yoav,
Howdy,
At least on unix, it's a QUIT (not STOP) signal.
kill -s QUIT processId
Oh! Brain fart. Yep, it's QUIT, not STOP. It's still CTRL-\ from the
terminal.
-chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additiona
ember 05, 2003 8:27 AM
>To: Tomcat Users List
>Subject: [OT] How to get a thread dump (was: Severe notification ...)
>
>Mufaddal,
> > Is
>> there a facility in tomcat that would allow me to dump its threads
and
>> allow me to see where the threads are waiting and not mo
Mufaddal,
> Is
there a facility in tomcat that would allow me to dump its threads and
allow me to see where the threads are waiting and not moving on ?
People need to stop asking this question and do "google java virtual
machine thread dump". Sheesh...
Send the process a STOP s
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)"
What is the best method to get a stack dump following a frozen tomcat? I
cannot use "kill -QUIT (pid)" since running in production and do not want to
run TC in the foreground.
Thanks,
Euan
J2DSK_1.4.1_03
TC 4.1.24 (Standalone, Coyote connector)
Linux RH9.
---
ist
> Subject: RE: Thread dump
>
> I am intrigued by this feature; it would help with the debugging of a
> application. I tried to test it against tomcat but I get nothing on
> stderr (i.e., nothing in /var/log/messages, terminal, directory I am in,
> catalina.out, or any of the logs fo
r, 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:
e-
> 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 that not actually kill the process, rather than
> displaying the thread dump?
>
> And what i
Thanks. I'm gonna try jpda - i have just started exploring it.
i was interested to see the thread dump from the point tomcat's main()
starts, to get a hang of the sequence of the class loaders/resource
managers/security realms, etc starting up.
thanks,
manav.
-Original Message
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
You could use Thread.enumerate(Thread [] ) and then do a Thread.dumpStack()
on each thread in your code. I can't provide any definite answers on how to
get a thread dump right from the moment Tomcat starts, but I suppose you
could modify Tomcat code (call the about the methods in your code)
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 the moment tomcat
starts up?
Thanks,
manav.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday
12/06/02 09:53 AMSubject: Thread dump
Please respond to
I have tomcat 4.1 running on Linux. How do i see the thread dump? The
startup.sh on linux just starts it in the background, while i could use
startup.bat on windows and get the thread dump.
thanks,
manav.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands,
7;ve got a dump using CTRL-Break. Any ieads from this why
the
process is behaving like this?
This is Win2000, Tomcat 3.2.2 and apache 1.3.12
ANy sugesstions please, help put me out of my misery !
Andy C
Full thread dump:
"Thread-33" (TID:0xb4a2c0, sys_thread_t:0x1e16e88, Win32I
38 matches
Mail list logo
