[KARAF-1742] Add command to show list of threads and stack traces

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Assignee: Christian Schneider
• Reporter: Christian Schneider
• Created: 17/Aug/12 08:24
• Updated: 18/Aug/12 16:42
• Resolved: 17/Aug/12 09:27

Description

Add a shell:threads command to show threads and stack traces.

Usage:
> shell:threads
Id | Name | State | CPU time | User time
--------------------------------------------------------
8 | ReaderThread | RUNNABLE | 0 | 0
5 | Attach Listener | RUNNABLE | 0 | 0
4 | Signal Dispatcher | RUNNABLE | 0 | 0
3 | Finalizer | WAITING | 0 | 0
2 | Reference Handler | WAITING | 0 | 0
1 | main | RUNNABLE | 234 | 109

> shell:threads 1
Thread 1 main RUNNABLE
Stacktrace:
sun.management.ThreadImpl.getThreadInfo1 line: -2
sun.management.ThreadImpl.getThreadInfo line: 154
sun.management.ThreadImpl.getThreadInfo line: 121
org.apache.karaf.shell.commands.impl.ThreadsAction.printThread line: 51
org.apache.karaf.shell.commands.impl.ThreadsTest.testThreadInfo line: 18
sun.reflect.NativeMethodAccessorImpl.invoke0 line: -2
sun.reflect.NativeMethodAccessorImpl.invoke line: 39
sun.reflect.DelegatingMethodAccessorImpl.invoke line: 25
java.lang.reflect.Method.invoke line: 597
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall line: 45
org.junit.internal.runners.model.ReflectiveCallable.run line: 15
org.junit.runners.model.FrameworkMethod.invokeExplosively line: 42
org.junit.internal.runners.statements.InvokeMethod.evaluate line: 20
org.junit.runners.ParentRunner.runLeaf line: 263
org.junit.runners.BlockJUnit4ClassRunner.runChild line: 68
org.junit.runners.BlockJUnit4ClassRunner.runChild line: 47
org.junit.runners.ParentRunner$3.run line: 231
org.junit.runners.ParentRunner$1.schedule line: 60
org.junit.runners.ParentRunner.runChildren line: 229
org.junit.runners.ParentRunner.access$000 line: 50
org.junit.runners.ParentRunner$2.evaluate line: 222
org.junit.runners.ParentRunner.run line: 300
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run line: 50
org.eclipse.jdt.internal.junit.runner.TestExecution.run line: 38
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests line: 467
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests line: 683
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run line: 390
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main line: 197