JDK-6696028 : JMXServiceURL like service:jmx:rmi:///jndi/iiop:// should be rejected by the RMI conn provider.
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-04-30
  • Updated: 2010-12-04
  • Resolved: 2009-01-16
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.
6u12 b01Fixed 7Fixed
Related Reports
Relates :  
Relates :  
Relates :  
URL of the form service:jmx:rmi:///jndi/iiop://... are incorrect, but somehow used to work in some cases for JDK 5.
They no longer work in JDK 6 - but the exception message that gets thrown is very confusing.
When encountering such a "bad URL' the JMXConnector providers for RMI/IIOP RMI/JRMP should throw an exception directly - with a more meaningful message - and possibly log a message on FINE or CONFIG.


EVALUATION http://hg.openjdk.java.net/jdk7/build/jdk/rev/aed81a97aae3

EVALUATION For compatibility reasons it is probably better to catch the exception if we fail to retrieve the stub from JNDI, and only then check the form of the URL. If we find that the URL is of the form ...:rmi//..../iiop://... then we can throw a "better" exception, keeping the original exception in the cause.