[
https://jira.terracotta.org/jira//browse/CDV-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Bale resolved CDV-244.
----------------------------
Resolution: Fixed
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.
> Serialization of shared objects fails to resolve reference fields
> -----------------------------------------------------------------
>
> Key: CDV-244
> URL: https://jira.terracotta.org/jira//browse/CDV-244
> Project: Community Development
> Issue Type: Bug
> Components: DSO:L1
> Reporter: Tim Eck
> Assignee: Scott Bale
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
