[
https://issues.jboss.org/browse/AS7-3229?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-3229:
-----------------------------------
Another observation is that
org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.postReplicate() is
causing the deserialization to occur.
This is interesting because its the second time the same buffer has been serialized. The
first time we serialize the (same) buffer, is from
SerializationGroupMemberContainer.get(). Paul and I discussed this the other day
(
http://pastie.org/3175394 contains the two call stacks).
If deserializing the same buffer twice, fails on the second call
(SerializationGroupMemberContainer.get()), that might mean that the serialized byte buffer
has been corrupted in-between the two attempts to deserialize the same buffer.
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