[
https://issues.jboss.org/browse/ISPN-3311?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-3311:
----------------------------------------
The problem is due the work I did to reduce the per-entry overhead in Infinispan
(ISPN-3144). In 5.2.x an earlier, a cache entry stored the key and an instance of
InternalCacheValue and serialized those two. In 5.3.x, that InternalCacheValue wrapper is
gone, so we just keep a reference to the key and value, without the wrapper. We create
InternalCacheValue instances on the fly when needed. When it comes to serializing, it
changed so that the value was serialized directly, instead of the InternalCacheValue which
then serialized the value itself.
I'm checking if there's a way to somehow support both ways.
Unmarshalling error switching from 5.2 to 5.3
---------------------------------------------
Key: ISPN-3311
URL:
https://issues.jboss.org/browse/ISPN-3311
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.3.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 6.0.0.Alpha2, 6.0.0.Final
Error:
{code}Caused by: org.infinispan.CacheException: Type of data read is
unknown. Id=-2147482348 is not amongst known reader indexes.
at
org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222){code}
Full stacktrace:
https://gist.github.com/galderz/770679223e02f5b211f8
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira