Bug ID: JDK-6387250 Regression: JConsole fails to connect to a JMX agent of a given JMXServiceURL

Type: Bug
Component: tools
Sub-Component: jconsole
Affected Version: 6

Priority: P3
Status: Resolved
Resolution: Fixed
OS: generic,linux
CPU: generic,x86

Submitted: 2006-02-17
Updated: 2010-07-29
Resolved: 2006-06-21

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

JDK 6
6 b89Fixed

The fix for "CR 6423867: Regression: Can not reconnect or make new connection to
restarted VM" introduced a regression in the JConsole connection mechanism which
broke the possibility to connect to a JMX agent through a JMXServiceURL.

EVALUATION JConsole cannot connect to a JMX agent of a given JMXServiceURL due to a regression caused by the fix for 6423867. So without this bug fix, JConsole can only connect using hostname+port or pid (i.e. the JMX agent started with the out-of-the-box management support). This bug is fixed after beta2 which is available for download from the latest Mustang snapshot at http://mustang.dev.java.net/.

28-06-2006

SUGGESTED FIX Perform the checks for secure stubs just for the "hostname:port" case.

17-02-2006

EVALUATION JConsole performs the checks for secure RMI remote stubs even for the case where a JMXServiceURL is supplied by the user at connection time. These checks should only be performed when "hostname:port" is the option used at connection time.

17-02-2006

Duplicate :	JDK-6467247 - Connection with jconsole of 1.6.0-beta2-b86 fails (while 1.5 succeeds)
Relates :	JDK-6423867 - Regression: Can not reconnect or make new connection to restarted VM