Ability to dump all threads [Enhancement Requests]

laghdaf / jvmtop

Automatically exported from code.google.com/p/jvmtop

0 stars 0 forks source link

Ability to dump all threads [Enhancement Requests] #40

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

A new option to show all threads will be useful just in case the database 
server is too slow to respond resulting in a pile-up of threads in the Java 
server.

Original issue reported on code.google.com by srini.ga...@gmail.com on 4 Nov 2013 at 7:30

GoogleCodeExporter commented 9 years ago

Maybe I got you wrong - maybe you can clarify your feature idea a little bit:

Maybe you can give us an example how such an output would look like?
How would such a feature differ from the JDK's jstack utility?

Original comment by patric.r...@gmail.com on 7 Nov 2013 at 7:08

Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 9 years ago

Original comment by patric.r...@gmail.com on 5 Dec 2013 at 10:22

Changed state: NeedInfo

GoogleCodeExporter commented 9 years ago

Yes, I agree. But if one wants to use jvmtop as the main monitoring tool, that 
would be useful.

Original comment by srini.ga...@gmail.com on 5 Dec 2013 at 10:30

GoogleCodeExporter commented 9 years ago

Also voting for this feature.

Original comment by eladta...@gmail.com on 25 Jan 2015 at 9:50

GoogleCodeExporter commented 9 years ago

Hello everyone,

do I understand you correctly that you want to see all threads of a monitored 
jvm in the "detail mode"?

If you agree - what should happen if there are more lines than the screen can 
hold? Or do you just want to pipe the output into some file?

Any additional information would be helpful.

Original comment by patric.r...@gmail.com on 16 Feb 2015 at 5:08