Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325504 - No JMX connection for application launched with -Dcom.sun.management.jmxremote
Summary: No JMX connection for application launched with -Dcom.sun.management.jmxremote
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-16 13:31 EDT by never_read_this CLA
Modified: 2011-06-08 14:29 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description never_read_this CLA 2010-09-16 13:31:31 EDT 
Build Identifier: 20090920-1017

 

Reproducible: Always

Steps to Reproduce:
1. Start Eclipse without -Dcom.sun.management.jmxremote
2. Start some XYZ-application from Eclipse with -Dcom.sun.management.jmxremote
3. Start [JDK]/bin/jconsole.exe -or- [JDK]/bin/jvisualvm.exe

Observed:
The XYZ-application process is not visible in JConsole or JVisualVM.

Expected:
The XYZ-application process is available for connection from JConsole or JVisualVM.

The workaround:
1. Start Eclipse with -Dcom.sun.management.jmxremote
2. Start some XYZ-application from Eclipse without -Dcom.sun.management.jmxremote
This workaround allows JMX connection to Eclipse itself and all processes launched from it instead of connection to a specific process launched from Eclipse.
Comment 1 Pawel Piech CLA 2011-06-08 13:39:45 EDT 
Java debugging... I guess?
Comment 2 Michael Rennie CLA 2011-06-08 14:29:31 EDT 
This works fine for me using either jconsole or visualvm.