[jboss-jira] [JBoss JIRA] (AS7-3229) OptionalDataException failure during deserialization of nested bean
Scott Marlow (JIRA)
jira-events at lists.jboss.org
Wed Jan 11 13:55:21 EST 2012
[ https://issues.jboss.org/browse/AS7-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655287#comment-12655287 ]
Scott Marlow commented on AS7-3229:
-----------------------------------
http://fpaste.org/JDwe/ shows why we deserialize twice (call stack from each of the calls). The second time comes from org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.postReplicate. The first comes from SerializationGroupMemberContainer.get
the first serialization (after an invocation) comes from SerializationGroupMemberContainer.preReplicate (called from PassivatingBackingCacheImpl.release) and the second one is from SerializationGroupMemberContainer.update (also called from PassivatingBackingCacheImpl.release) http://fpaste.org/ZrEE/
> 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
More information about the jboss-jira
mailing list