102

Normally to attach a debuger to a running jvm you would need start the jvm with arguments such as the following:

> java -Xdebug -Xrunjdwp:transport=dt_socket,address=1000,server=y,suspend=n

Now if I want to debug a process that wasn't started in debug mode, what can I do?

This situation arrises when a production system (i.e. started without debug args) exhibits a 'random' (I use the term loosely) bug. So I can't restart the jvm with the appropriate arguments, because nobody knows how to reproduce the bug again. Is it impossible to attach to the JVM in this situation?

Just to clarify it is not possible to use tools like jdb to attach to already running JVMs unless they were started in debug mode

from the JVM man page

Another way to use jdb is by attaching it to a Java VM that is already running. A VM that is to be debugged with jdb must be started with the following options:

1

5 Answers 5

51

You may be able to use jsadebugd (JDK) to attach a debug server to the process (available on Windows with the Debugging Tools for Windows). It is marked as experimental, so you may want to try it out on a test machine first.

Usage:

jsadebugd <pid>
jdb -connect sun.jvm.hotspot.jdi.SADebugServerAttachingConnector:debugServerName=localhost

The connector name withe arg can be found using jdb -listconnectors.

Sign up to request clarification or add additional context in comments.

5 Comments

I'm using linux so this seems to be the most promising solution
Any experiences to share with this?
My experience is that it worked well the times which I needed it, in the mean time all in factory instances of the software are no configured to launch with jvm debug options by default so we can use the supported method.
On Java 11 jsadebugd was replaced by jhsdb debugd. So that becomes jhsdb debugd --pid <pid>. See slides of a talk presenting jhsdb and the docs for jhsdb
It seems SADebugServerAttachingConnector was removed from jdb as well, and I think the replacement is supposed to be jhsdb hsdb / jhsdb clhsdb. I can't find any docs on what arguments to give to jhsdb clhsdb.
34

Just to clarify it is not possible to use tools like jdb to attach to already running JVMs > > unless they were started in debug mode

in soviet russia source reads you

jdb -connect sun.jvm.hotspot.jdi.SAPIDAttachingConnector:pid=9426

1 Comment

well that is the "supported" answer but the experimental answer is the one I accepted, so it can be done in an unsupported fasion
7

VisualVM isn't a debugger, but you can get thread dumps and heap dumps from it that can be useful in diagnosing some problems. The most useful features require JVM 5 or 6.

2 Comments

link does not work.... maybe you outa remove the http:// before the https://... I would've but dont have the enough reputation yet
+1 VisualVM looks really interesting. BTW: Link is fixed now.
6

using jstack (useful in case of deadlocks) or the btrace VisualVM plugin could also do the trick

Comments

-5

You can always use jdb and debug by hand :P

4 Comments

I always thought that you can't attach to jvm with jdb unless the jvm was started with to allow debug connections Am I wrong?
As far as I understand, the option you mentioned is to "enable" remote debug of your "java" command (the VM) But you can also use the jdb command instead. So instead of java MyApp you would go like jdb MyApp ( and debug interactively , set breakpoints, run, stop, watch, etc etc. )
I don't think that is correct according to the jdb man page -- start quote Another way to use jdb is by attaching it to a Java VM that is already running. A VM that is to be debugged with jdb must be started with the following options: -- end quote
With the correct connector(unsupported for now) jdb can connect to a running process.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.