The following page says to report all Hanging Builds. The Page https://wiki.jenkins-ci.org/display/JENKINS/Build+is+hanging?showComments=true&showCommentArea=true#addcomment

Hanging Builds occur regularly when using WebDriver/Selenium2.

ThreadDump all ways produces the following stack trace, for different TestSuites.

C:\Program Files\Apache Software Foundation\apache-maven-3.1.1\bin\mvn.bat -D-Dtest=AllSupportClassTests test: stdout copier

"C:\Program Files\Apache Software Foundation\apache-maven-3.1.1\bin\mvn.bat -D-Dtest=AllSupportClassTests test: stdout copier" Id=20356 Group=main RUNNABLE (in native)
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)

• locked java.io.BufferedInputStream@36648851
  at java.io.FilterInputStream.read(Unknown Source)
  at hudson.util.StreamCopyThread.run(StreamCopyThread.java:60)

Also because the stack trace is cut off at this point it is impossible to learn if where in my TestSuite the code is hanging.

It is suggested that using JMAP is used to find this, however when the ID produced in the ThreadDump the following error is produced.

C:\Users\Administrator>jmap 20356
Attaching to process ID 20356, please wait...
Error attaching to process: Windbg Error: WaitForEvent failed!

Also it would be useful if threadDump was available in a form that did not trunkate the stack trace.