-
Bug
-
Resolution: Fixed
-
P3
-
6
-
b01
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2202112 | 7 | Sean Coffey | P3 | Resolved | Fixed | b120 |
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
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
- backported by
-
JDK-2202112 JMXServiceURL like service:jmx:rmi:///jndi/iiop:// should be rejected by the RMI conn provider.
- Resolved
- relates to
-
JDK-6984520 NPE IN RMIConnector.connect
- Resolved
-
JDK-6770624 JMXServiceURL like service:jmx:rmi:///jndi/iiop:// drives to a NPE
- Resolved
-
JDK-6769658 javax/management/remote/mandatory/connection/IllegalIIOPURLTest isn't reliable
- Closed