United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6696028 JMXServiceURL like service:jmx:rmi:///jndi/iiop:// should be rejected by the RMI conn provider.
6696028 : JMXServiceURL like service:jmx:rmi:///jndi/iiop:// should be rejected by the RMI conn provider.

Details
Type:
Bug
Submit Date:
2008-04-30
Status:
Closed
Updated Date:
2010-12-04
Project Name:
JDK
Resolved Date:
2009-01-16
Component:
core-svc
OS:
generic
Sub-Component:
javax.management
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
6
Fixed Versions:
6u12

Related Reports
Backport:
JDK-2202112 - JMXServiceURL like service:jmx:rmi:///jndi/iiop:// should be rejected by the RMI conn provider.
Relates:
JDK-6770624 - JMXServiceURL like service:jmx:rmi:///jndi/iiop:// drives to a NPE
Relates:
JDK-6984520 - NPE IN RMIConnector.connect
Relates:
JDK-6769658 - javax/management/remote/mandatory/connection/IllegalIIOPURLTest isn't reliable

Sub Tasks

Description
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.

See:
http://forum.java.sun.com/thread.jspa?threadID=5229564

Comments
EVALUATION

http://hg.openjdk.java.net/jdk7/build/jdk/rev/aed81a97aae3
2010-12-04 
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.
2008-05-02


Hardware and Software, Engineered to Work Together