United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6238076 Serialized form of javax.management.remote.rmi.RMIConnector includes clientNotifID field
JDK-6238076 : Serialized form of javax.management.remote.rmi.RMIConnector includes clientNotifID field

Details
Type:
Bug
Submit Date:
2005-03-09
Status:
Resolved
Updated Date:
2010-07-29
Project Name:
JDK
Resolved Date:
2005-07-22
Component:
core-svc
OS:
generic
Sub-Component:
javax.management
CPU:
generic
Priority:
P5
Resolution:
Fixed
Affected Versions:
6
Fixed Versions:

Related Reports

Sub Tasks

Description
The class javax.management.remote.rmi.RMIConnector contains a field clientNotifID.  Since this class is Serializable, and since the field is not transient, the serialized form includes clientNotifID.  The purpose of this field is to track the notification sequence number in JMXConnectionNotifications from the RMIConnector (so it should really be called clientNotifSeqNo or the like).  An RMIConnector is typically only serialized if it is the value returned by RMIConnectorServer.toJMXConnector, in which case it will not have been connected and will have a sequence number of 0.  Even if an RMIConnector is serialized in other circumstances, there is little or no interest in continuing the notification sequence numbers when it is subsequently deserialized.
###@###.### 2005-03-09 09:54:47 GMT

                                    

Comments
EVALUATION

The fact that this field is not transient is clearly an oversight.  It is hard to imagine that removing it from the serial form would impact any existing code.  On the other hand, it does little harm as it is.
###@###.### 2005-03-09 09:54:47 GMT
                                     
2005-03-09
SUGGESTED FIX

Rename the clientNotifID field to clientNotifSeqNo and make it transient.
###@###.### 2005-06-24 09:40:31 GMT
                                     
2005-06-24



Hardware and Software, Engineered to Work Together