The dumpthreads script sends a QUIT signal to the JVM process that Rhino is running in, causing the JVM to produce a thread dump.
The script itself has no output. It is used internally by Rhino (via the Watchdog) to produce a Java thread dump from the Rhino JVM in certain error scenarios (such as stuck event processing threads). Below is a partial example of thread-dump output:
"StageWorker/TM/1" prio=1 tid=0x082bb5c0 nid=0x192 in Object.wait() [0x9aae9000..0x9aaea060]
at java.lang.Object.wait(Native Method)
- waiting on <0x9f4154d8> (a [Lcom.opencloud.ob.RhinoSDK.mM;)
at java.lang.Object.wait(Object.java:474)
at com.opencloud.ob.RhinoSDK.oS$a.run(13520:68)
- locked <0x9f4154d8> (a [Lcom.opencloud.ob.RhinoSDK.mM;)
at java.lang.Thread.run(Thread.java:595)
"Timer-2" prio=1 tid=0x9ac06988 nid=0x18e in Object.wait() [0x9ab6a000..0x9ab6afe0]
at java.lang.Object.wait(Native Method)
- waiting on <0x9f4bff28> (a java.util.TaskQueue)
at java.util.TimerThread.mainLoop(Timer.java:509)
- locked <0x9f4bff28> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
