[#CDV-736] SerializationUtils (ObjectOutputStream) doesn't resolve objects - Terracotta Project Issue Tracker

Community Development

SerializationUtils (ObjectOutputStream) doesn't resolve objects

Created: 19/Apr/08 03:09 PM Updated: 07/Aug/09 02:09 PM Resolved: 22/Apr/08 10:26 AM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

File Attachments:

serializationutilstest.tgz (2 kB) 19/Apr/08 03:11 PM - Taylor Gautier

Issue Links:

Duplicate

This issue duplicates:

~~CDV-244~~ Serialization of shared objects fails to resolve reference fields

Severity:	3 Feature failure (but usable), workaround available
Fix In Branch:	trunk

Description

« Hide

See attached test. To repro untar:

$ mvn tc:start
$ mvn tc:run
$ mvn tc:run

The second run will attempt to read the object (a hand coded linked list 5 elements long) and clone it. It will print the read object, and the cloned object. Here are the results:

[INFO] [node] org.terracotta.sample.Main$Linked@5e32f9 : org.terracotta.sample.Main$Linked@5e32f9 : org.terracotta.sample.Main$Linked@5e32f9 : org.terracotta.sample.Main$Linked@5e32f9 : org.terracotta.sample.Main$Linked@5e32f9 : org.terracotta.sample.Main$Linked@5e32f9
[INFO] [node] org.terracotta.sample.Main$Linked@55c37d

The second output should have been 5 elements long like the first.

Sort Order:

[ Permalink | « Hide ]

Taylor Gautier added a comment - 19/Apr/08 03:10 PM

http://forums.terracotta.org/forums/posts/list/0/987.page

[ Permalink | « Hide ]

Scott Bale added a comment - 21/Apr/08 08:55 AM - edited

I notice that the example works correctly if you System.out.println the object BEFORE cloning it. I'm guessing there's a problem in serializing a clustered object before it is faulted into the L1 node.

Also, there's a minor bug in the print() method - you want to do buffer.append(current) rather than buffer.append(this).