Accepted answer

Indeed (thanks VonC to point to the SO thread), Dustin, in a comment to his message, points to jstack.

I have run a little Java application (with GUI) in Eclipse, I can see the related javaw.exe in Windows' process manager and its PID, 7088 (it is even simpler in Unix, of course).

If I type at a command prompt jstack 7088, I have the wanted stack dump per thread.

Would be better if we could do that directly from Eclipse, but that's already useful as is.


Did you try to launch your eclipse with java.exe instead of javaw.exe (in your eclipse.ini) ?

That might give you the console you need, as described in this bug and in this message.

Other ideas (in term of java options) could be derived from this other SO question.


You can connect through the JVisualVM and get a thread dump. Just right click on the application node from the Applications tree and select "Thread dump"


On linux at least you can do a ps -ef | grep java to get the PID and then do a kill -3 PID and it will output it to the Eclipse console.


StackTrace is another option that you could try. From the features:

Thread dump for Java processes running as a Windows service (like Tomcat, for example), started with javaw.exe, applets running inside any browser or JVMs embedded inside another process. StackTrace works on Windows, Linux and Mac OS X.


if you prefer UI based solution visualvm might be a good choice. (it's advantage is also that it's distributed with JDK)

To take the thread dump in visualvm:

  1. connect to process (remote or local) and
  2. go for Threads (tab) -> Thread Dump (button)


Eclipse Wiki: How to Report a Deadlock lists all possible options of creating a thread dump in Eclipse. Depending on the concrete situation, one or the other may work better -- my personal favorite on Windows is the Adaptj Stacktrace tool.


You can do it when you are in debug mode: go to the debug view in the debug perspective, click on the process you have launched and click on pause, you will get a graphical stack of all your processes.

Note : this also works when using remote debugging, you do not need to launch weblogic from eclipse, you can launch it on its own, open the debugging ports and create a "remote java application debug configuration" for it.

Related Query

More Query from same tag