Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 325504

Summary:	No JMX connection for application launched with -Dcom.sun.management.jmxremote
Product:	[Eclipse Project] JDT	Reporter:	never_read_this
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	Michael_Rennie, pawel.1.piech
Version:	3.6.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description never_read_this

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

2011-06-08 13:39:45 EDT

Java debugging... I guess?

Comment 2 Michael Rennie

2011-06-08 14:29:31 EDT

This works fine for me using either jconsole or visualvm.