Issue Details (XML | Word | Printable)

Key: CDV-244
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: 2 Major 2 Major
Assignee: Hung Huynh
Reporter: Tim Eck
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Community Development

Serialization of shared objects fails to resolve reference fields

Created: 26/Apr/07 05:13 PM   Updated: 26/Sep/08 03:16 PM
Component/s: DSO:L1
Affects Version/s: 2.7.0-stable1
Fix Version/s: 2.7.0

Issue Links:
Duplicate
 
Related
 

Severity: 3 Feature failure (but usable), workaround available
Fix In Branch: 2.7, trunk
Target: 2.7
Fixed In Revision: 10044
Date of First Response: 27/Apr/07 10:19 AM


 Description  « Hide
From the forums: http://forums.terracotta.org/forums/posts/list/0/226.page

If a shared object is serialized, it possible to observe unresolved reference values. I believe the reason for this is that field values are read using sun.misc.Unsafe.getObject(..). Specifically in java.io.ObjectStreamClass$FieldReflector.getObjFieldValues(). This method of reading field data will bypass the DSO mechanics for resolving fields.

I don't think fields that are DSO literal types are affected since they are never unresolved.

I'm not sure about logical collections -- although I guess they are okay since they implement readObject/writeObject in terms of their iterators which do flow though DSO goodness.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Tim Eck added a comment - 11/Sep/08 11:18 PM
I think should be fixed in trunk now as of rev 10044

Scott Bale added a comment - 15/Sep/08 07:57 PM
Looks like still a problem at least for clustered HashMap instances. With Tim's help I've duplicated Himadri's problem by adding to the system test that Tim wrote for this issue.

Scott Bale added a comment - 16/Sep/08 12:32 PM
similar Serialization issue, both affect Lassen Exam caching

Scott Bale added a comment - 16/Sep/08 12:34 PM
Alex and I decided there should really be a new JIRA issue, because it is really a new (albeit related) problem (CDV-907) that has been found. Tim's fix for this issue is fine and needs to be in 2.7 branch.

Hung Huynh added a comment - 19/Sep/08 04:04 PM
test existed.