Friday, April 20, 2007

Using JConsole

I updated my eclipse to version 3.2.2, lucky me did not remove the previous version just yet, and run into a crashing system that seems to run out of memory. So I decided to connect jconsole to eclipse to view its memory consumption.
To do so I needed to start eclipse using JDK 5, with the system property -Dcom.sun.management.jmxremote.
Now JConsole is able to connect to the eclipse process and show its memory consumption.

After playing a while with eclipse the OOM exception hapened again, but saidly JConsole has lost its connection, so nothing to see what/.where had happened.

The story continues...

3 comments:

Albert said...

How did you get this to work? After starting eclipse with that property, what info do you put into JConsole to get it to connect?

Albert said...

Nevermind.

SpiderMars said...

Albert: Thanks for your reply. Using the system property -Dcom.sun.management.jmxremote enables the local JMX agent for the process.
See for more details http://www.eclipsezone.com/eclipse/forums/t102096.html?start=30 and http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html#local.