[jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1211) Cache marshaller breaks when marshalling more than 32767 of "certain" objects in a single stream
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Thu Nov 8 08:14:44 EST 2007
[ http://jira.jboss.com/jira/browse/JBCACHE-1211?page=all ]
Manik Surtani resolved JBCACHE-1211.
------------------------------------
Resolution: Done
> Cache marshaller breaks when marshalling more than 32767 of "certain" objects in a single stream
> ------------------------------------------------------------------------------------------------
>
> Key: JBCACHE-1211
> URL: http://jira.jboss.com/jira/browse/JBCACHE-1211
> Project: JBoss Cache
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Replication
> Affects Versions: 2.0.0.GA
> Reporter: Manik Surtani
> Assigned To: Manik Surtani
> Priority: Critical
> Fix For: 2.1.0.GA
>
>
> This is a nasty. What started life as an optimisation for certain types of objects in a marshalled stream (Fqn, GlobalTransactio, String and Serializable) has become a major limitation in that a single stream can only hold up to 32767 different (not equal()) instances of such objects.
> Basically the optimisation was, for example, instead of writing "hello" to a stream twice, just write it once and use a reference for all subsequent times. Unfortunately this reference was encoded as a short, hence the limitation of 32767.
> Fixing this will definitely break wire compatibility with JBoss Cache 2.0.0, although JBC does allow backward compatibility by specifying replication version in your configuration, thanks to the VersionAwareMarshaller.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list