JDK-6211220 : jmx.serial.form=1.0 deserializes broken ObjectNames
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 5.0,6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,windows_xp
  • CPU: generic,x86
  • Submitted: 2004-12-21
  • Updated: 2010-08-03
  • Resolved: 2005-01-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
5.0u2Fixed 6 b19Fixed
Description
When the jmx.serial.form property is set to 1.0, which should cause the
implementation to use the JMX 1.0 serial forms, deserializing an ObjectName
produces a NullPointerException whenever you call any of the majority of its
methods.  The fundamental problem is that the _canonicalName field is not
set in this case.
###@###.### 2004-12-21 14:03:06 GMT
Comments
SUGGESTED FIX In readObject(), when compat is true, call the construct(String) method with domain + ":" + propertyListString, where domain and propertyListString are obtained from the serialized fields via ObjectInputStream.readFields(). ###@###.### 2004-12-21 14:03:07 GMT
21-12-2004
EVALUATION This is very unfortunate, since the whole point of this property is to allow the sort of interoperation that fails in this case. ###@###.### 2004-12-21 14:03:06 GMT
21-12-2004