JDK-6616825 : JMX query returns no value in 1.0 compatibility mode - deserialization bug in readObject()
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 5.0u15,6u10
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,solaris_9
  • CPU: sparc
  • Submitted: 2007-10-15
  • Updated: 2010-07-29
  • Resolved: 2007-12-07
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.
Other JDK 6 JDK 7 Other
5.0u15,OpenJDK6Fixed 6u10Fixed 7Fixed OpenJDK6Fixed
The ObjectName readObject() method (deserialization) is wrong
when -Djmx.serial.form=1.0 is used. There is a test case in the attachment which shows the bug.

SUGGESTED FIX See attached jdk5-ObjectName.java.patch (for javax/management/ObjectName.java) See attached jdk5-SerialCompatTest.java.patch (for additional serial compatibility test case). See also: http://amos.france///jmgt/master/webrev/jmx/tiger/6616825_webrev/index.html for a description of the suggested fix [note: Frames diff may not work] *** (#1 of 1): [ UNSAVED ] ###@###.###

EVALUATION The problem is in ObjectName.readObject() which doesn't take into account the value of the "propertyPattern" field.