[JBoss JIRA] Created: (JBAS-5163) listThreadDump should print thread dumps in the same format as kill -3
12:23 a.m.
listThreadDump should print thread dumps in the same format as kill -3
----------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX, Management services, System service
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an MBean
that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:25 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) listThreadDump should print thread dumps in the same format as kill -3
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: jmx-serverinfo.dump
listThreadDump should print thread dumps in the same format as kill
-3
----------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX, Management services, System service
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:25 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) listThreadDump should print thread dumps in the same format as kill -3
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: kill-3.dump
listThreadDump should print thread dumps in the same format as kill
-3
----------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX, Management services, System service
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:02 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) listThreadDump should print thread dumps in the same format as kill -3
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12399048 ]
Galder Zamarreno commented on JBAS-5163:
----------------------------------------
I suspect we'll only be able to provide more detailed stacktraces via JMX when
we support Java 6 and therefore, will only be applicable to JBoss 5 for the time
being:
http://java.sun.com/javase/6/docs/technotes/guides/management/enhancement...
I'll kick off a discussion in the management forum soon.
listThreadDump should print thread dumps in the same format as kill
-3
----------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX, System service, Management services
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:57 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) listThreadDump should print thread dumps in the same format as kill -3
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12399067 ]
Dimitris Andreadis commented on JBAS-5163:
------------------------------------------
Yes, the information returned by the platforms mbeans in jdk5 is not sufficient to produce
what you want. Maybe it's better with jdk6, but the code whould have to use reflection
to stay portable.
listThreadDump should print thread dumps in the same format as kill
-3
----------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX, System service, Management services
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:41 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) listThreadDump should print thread dumps in the same format as kill -3
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12399154 ]
Galder Zamarreno commented on JBAS-5163:
----------------------------------------
It's indeed much better with JDK 6 because it offers MonitorInfo and LockInfo
classes.
Re: but the code whould have to use reflection to stay portable.
Absolutely :)
I'll rename the JIRA to "Add JDK 6 version of ServerInfo.listThreadDump() taking
advantage of new management classes".
I can do this myself but it's not a priority for JBoss 5.0.0.GA. I can work on it once
GA is out.
My aim is to make the output using JDK 6 as close as possible to something that can be
parsed by TDA, which is better than not being able to parse it with any tools out there
:)
listThreadDump should print thread dumps in the same format as kill
-3
----------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX, System service, Management services
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:43 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Summary: Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new
management classes (was: listThreadDump should print thread dumps in the same format as
kill -3)
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX, System service, Management services
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1, JBossAS-5.1.0.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:43 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) listThreadDump should print thread dumps in the same format as kill -3
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Fix Version/s: JBossAS-5.0.1.CR1
JBossAS-5.1.0.CR1
Renaming JIRA issue from "listThreadDump should print thread dumps in the same format
as kill -3"
to "Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new
management classes"
and updating fix versions.
listThreadDump should print thread dumps in the same format as kill
-3
----------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX, System service, Management services
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1, JBossAS-5.1.0.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:43 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Issue Type: Feature Request (was: Bug)
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX, System service, Management services
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1, JBossAS-5.1.0.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:56 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Priority: Minor (was: Major)
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX, System service, Management services
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Minor
Fix For: JBossAS-5.0.1.CR1, JBossAS-5.1.0.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:11 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Dimitris Andreadis updated JBAS-5163:
-------------------------------------
Fix Version/s: (was: JBossAS-5.1.0.CR1)
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX, Management services, System service
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Minor
Fix For: JBossAS-5.0.1.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:36 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12404595 ]
Galder Zamarreno commented on JBAS-5163:
----------------------------------------
One of the aims of this JIRA is that whatever output is produced
can be parsed by either TDA or Samurai, which are two of the
most used thread dump analysing tools.
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX, Management services, System service
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Minor
Fix For: JBossAS-5.0.1.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:36 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Priority: Major (was: Minor)
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX, Management services, System service
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12404721 ]
Dimitris Andreadis commented on JBAS-5163:
------------------------------------------
Just to make it clear: please don't change the existing listThreadDump method. Add a
2nd one instead that outputs information in the format you want.
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX, Management services, System service
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:55 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12404854 ]
Galder Zamarreno commented on JBAS-5163:
----------------------------------------
Well, we'll have to change listThreadDump already to take advantage of JDK 6,
won't we?
We can do this, and we can also, as you suggest, have a different method to provide
tool parseable (i doubt that word exists, but you get what I mean :) ) thread dumps. Tbh,
I dunno
whether the same format that TDA understands will be understood by Samurai. Need to dig
into it.
Bottom line, I see two parts here:
- update listThreadDump so that it takes advantage of JDK 6 classes if in use.
- create extra listThreadDump methods that output in a format that can be copy/pasted and
parsed by TDA and Samurai.
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX, Management services, System service
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:54 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12410400 ]
Galder Zamarreno commented on JBAS-5163:
----------------------------------------
FAO Dimitris:
Head has been based in Java 5 for quite a while now, so as part of this JIRA, I should
be able to convert reflection calls to JDK 5 methods into type safe ones, correct?
Obviously, I would use reflection for JDK 6 classes/methods.
Thoughts?
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX, Management services, System service
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:41 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12413687 ]
Dimitris Andreadis commented on JBAS-5163:
------------------------------------------
Yes. Use reflection to call into jdk6 features.
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:41 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12413688 ]
Dimitris Andreadis commented on JBAS-5163:
------------------------------------------
Also, I'd like to see what would the extra jdk6 info be in the output (some example).
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:57 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12413692 ]
Galder Zamarreno commented on JBAS-5163:
----------------------------------------
Re: Also, I'd like to see what would the extra jdk6 info be in the output (some
example).
Yeah, definitely. In facf, not just that, I'm creating 2 deadlock examples (one with
synchronised
monitors and one with java.util.concurrent Lock class impl) so that you can also see how
we can
print out deadlocks both JDK5 and JDK6. We could do already print synchronized monitor
deadlock
with JDK5 already, but was not implemented.
One thing I'm changing for all thread dumps is the following:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
Rather than "lockName: java.lang.Object@10cff6b" in the title, it makes more
sense to put it in the
stack itself, in the same way that any standard thread dump output does, i.e:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING
- waiting on java.lang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
The closer we are to real non JMX-console thread dumps, the easier for any of us to read
them.
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:37 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12414405 ]
Galder Zamarreno commented on JBAS-5163:
----------------------------------------
FAO Dimitris and anyone else interested in this JIRA:
In the next few minutes, I'll be uploading the following:
- a JBDS project called thread-deadlock containing source and
deployable sar that generates two type of deadlocks: one based
on synchronized statements and the other one based on
java.util.concurrent.* classes. The aim of this project is to show how
we can now find deadlocks and show them via the jmx console
output. Both types of deadlocks will only be visible with JDK 6.
- Two PDFs containing a thread dump taken with JDK 5 showing standard
thread dump and how deadlocks can be shown that are based on
synchronized statements. Bear in mind that waiting locks as now shown
as "- waiting on ..." so that they're closer to the signal based thread
dumps
that we're all used to.
- Two PDFs containing a thread dump taken with JDK 6 showing standard
thread dump and how deadlocks based on synchronized statements and
java.util.concurrent.* classes can be shown. JDK 6, *only for monitors
acquired via synchronized statements* shows where these locks were
acquired. You should be able to spot them by "- locked...". However, there's
no
API to be able to know where a java.util.concurrent.* lock class was locked,
hence we only list the locked java.util.concurrent.* locks.
If anyone is interested, I can upload a source patch for people to have a look at.
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jmx-serverinfo.dump, kill-3.dump
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:39 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: jdk5-with-deadlock.pdf
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jdk5-with-deadlock.pdf, jdk5-without-deadlock.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks.pdf, jmx-serverinfo.dump, kill-3.dump,
thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:39 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: thread-deadlock.zip
thread-deadlock JBDS project
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jdk5-with-deadlock.pdf, jdk5-without-deadlock.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks.pdf, jmx-serverinfo.dump, kill-3.dump,
thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:39 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: jdk5-without-deadlock.pdf
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jdk5-with-deadlock.pdf, jdk5-without-deadlock.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks.pdf, jmx-serverinfo.dump, kill-3.dump,
thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:39 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: jdk6-with-deadlocks.pdf
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jdk5-with-deadlock.pdf, jdk5-without-deadlock.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks.pdf, jmx-serverinfo.dump, kill-3.dump,
thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:39 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: jdk6-without-deadlocks.pdf
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jdk5-with-deadlock.pdf, jdk5-without-deadlock.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks.pdf, jmx-serverinfo.dump, kill-3.dump,
thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12414436 ]
Galder Zamarreno commented on JBAS-5163:
----------------------------------------
I'm adding new versions of the PDF where locks
are printed even closer to the traditional form.
Example:
- waiting on <0xe24fa8> (a java.lang.ref.Reference$Lock)
...
- locked <0x16aa1c3> (a java.net.SocksSocketImpl)
I prefer this output as it gets even closer to what
kill -3/Ctrl+Break thread dumps do hence helping
debugging.
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jdk5-with-deadlock-v2.pdf, jdk5-with-deadlock.pdf,
jdk5-without-deadlock-v2.pdf, jdk5-without-deadlock.pdf, jdk6-with-deadlocks-v2.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks-v2.pdf, jdk6-without-deadlocks.pdf,
jmx-serverinfo.dump, kill-3.dump, thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: jdk5-without-deadlock-v2.pdf
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jdk5-with-deadlock-v2.pdf, jdk5-with-deadlock.pdf,
jdk5-without-deadlock-v2.pdf, jdk5-without-deadlock.pdf, jdk6-with-deadlocks-v2.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks-v2.pdf, jdk6-without-deadlocks.pdf,
jmx-serverinfo.dump, kill-3.dump, thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: jdk5-with-deadlock-v2.pdf
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jdk5-with-deadlock-v2.pdf, jdk5-with-deadlock.pdf,
jdk5-without-deadlock-v2.pdf, jdk5-without-deadlock.pdf, jdk6-with-deadlocks-v2.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks-v2.pdf, jdk6-without-deadlocks.pdf,
jmx-serverinfo.dump, kill-3.dump, thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: jdk6-without-deadlocks-v2.pdf
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jdk5-with-deadlock-v2.pdf, jdk5-with-deadlock.pdf,
jdk5-without-deadlock-v2.pdf, jdk5-without-deadlock.pdf, jdk6-with-deadlocks-v2.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks-v2.pdf, jdk6-without-deadlocks.pdf,
jmx-serverinfo.dump, kill-3.dump, thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Attachment: jdk6-with-deadlocks-v2.pdf
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.1.CR1
Attachments: jdk5-with-deadlock-v2.pdf, jdk5-with-deadlock.pdf,
jdk5-without-deadlock-v2.pdf, jdk5-without-deadlock.pdf, jdk6-with-deadlocks-v2.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks-v2.pdf, jdk6-without-deadlocks.pdf,
jmx-serverinfo.dump, kill-3.dump, thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:19 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno updated JBAS-5163:
-----------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
(was: JBossAS-5.0.1.CR1)
This is actually ready to go as far as I'm concerned so moving
fix version to 5.0.0.CR1.
Dimitris, if you need more time to look into this, please feel free
to move the fix version.
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.0.CR1
Attachments: jdk5-with-deadlock-v2.pdf, jdk5-with-deadlock.pdf,
jdk5-without-deadlock-v2.pdf, jdk5-without-deadlock.pdf, jdk6-with-deadlocks-v2.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks-v2.pdf, jdk6-without-deadlocks.pdf,
jmx-serverinfo.dump, kill-3.dump, thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:33 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12415749 ]
Dimitris Andreadis commented on JBAS-5163:
------------------------------------------
Galder, please go ahead with the change in AS trunk.
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.0.CR1
Attachments: jdk5-with-deadlock-v2.pdf, jdk5-with-deadlock.pdf,
jdk5-without-deadlock-v2.pdf, jdk5-without-deadlock.pdf, jdk6-with-deadlocks-v2.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks-v2.pdf, jdk6-without-deadlocks.pdf,
jmx-serverinfo.dump, kill-3.dump, thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:43 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=comments#action_12415753 ]
Galder Zamarreno commented on JBAS-5163:
----------------------------------------
Thanks :).
Once I've done that, I'll create another JIRA to include methods
that can dump thread dumps in tool specific formats and subtasks
for each type of tool.
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.0.CR1
Attachments: jdk5-with-deadlock-v2.pdf, jdk5-with-deadlock.pdf,
jdk5-without-deadlock-v2.pdf, jdk5-without-deadlock.pdf, jdk6-with-deadlocks-v2.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks-v2.pdf, jdk6-without-deadlocks.pdf,
jmx-serverinfo.dump, kill-3.dump, thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:03 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-5163) Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of new management classes
[ http://jira.jboss.com/jira/browse/JBAS-5163?page=all ]
Galder Zamarreno resolved JBAS-5163.
------------------------------------
Resolution: Done
Add JDK 6 version of ServerInfo.listThreadDump() taking advantage of
new management classes
-------------------------------------------------------------------------------------------
Key: JBAS-5163
URL: http://jira.jboss.com/jira/browse/JBAS-5163
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.0.CR1
Attachments: jdk5-with-deadlock-v2.pdf, jdk5-with-deadlock.pdf,
jdk5-without-deadlock-v2.pdf, jdk5-without-deadlock.pdf, jdk6-with-deadlocks-v2.pdf,
jdk6-with-deadlocks.pdf, jdk6-without-deadlocks-v2.pdf, jdk6-without-deadlocks.pdf,
jmx-serverinfo.dump, kill-3.dump, thread-deadlock.zip
There're 4 ways to generate a thread dump. I have taken the output from the same run
with
different methods:
1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the
most useful
tools I've found out there!). Example:
"JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait()
[0x867f2000..0x867f30b0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9247e200> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
- locked <0x9247e200> (a java.lang.Object)
2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output:
Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING,
lockName:java.l
ang.Object@10cff6b
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it
prints previously locked
monitors. Cannot be parsed by TDA tools because it's in JBoss specific format.
3.- Thread.getAllStackTraces().
Haven't tested the output from this. What would this print? Couldn't find an
MBean that uses/parses
the output from this, but I suspect it's the same as method 2, specially since
http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed.
4.- JConsole Threads view:
Code:
Name: JBossLifeThread
State: WAITING on java.lang.Object@10cff6b
Total blocked: 0 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940)
Seems to print same info as JBoss' ServerInfo.
Bottom line: we should try generating thread dumps that look like kill -3
output to make them more readable than in their current format and to
benefit from existing tools that can parse standard kill -3 format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6079
days inactive
6215
days old
33 comments
2 participants
participants (2)
-
Dimitris Andreadis (JIRA) -
Galder Zamarreno (JIRA)