[
https://issues.jboss.org/browse/AS7-3229?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-3229:
-----------------------------------
PassivatingBackingCacheImpl.get(K key), is calling:
E entry = store.get(key, lock);
And then later:
if (isClustered()) {
passivationManager.postReplicate(entry);
}
The passivationManager.postReplicate(entry) method contains:
// Restore the entry's ref to the group and object
SerializationGroup<K, V, G> group = entry.getGroup();
if (group == null && entry.getGroupId() != null) {
group = groupCache.get(entry.getGroupId());
}
Perhaps we wouldn't be trying to deserialize the same buffer twice, if the first
deserialization set the "group" in entry (if clustering is enabled).
OptionalDataException failure during deserialization of nested bean
-------------------------------------------------------------------
Key: AS7-3229
URL:
https://issues.jboss.org/browse/AS7-3229
Project: Application Server 7
Issue Type: Sub-task
Components: Clustering
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.Final
Test case branch link is coming (I need to recreate it without the Hibernate
4.0.1-SNAPSHOT dependency).
The bug didn't recreate with the simple test
https://github.com/scottmarlow/jboss-as/commits/AS7-3229. Might need to push the XPC
serialization changes before it can be recreated.
Exception call stack
http://pastie.org/3155867
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira