Exception while deserialization of java.math.BigInteger in Sun JRE 1.6.0_14 if serialized
using a previous version e.g. JRE 1.6.0_13.
--------------------------------------------------------------------------------------------------------------------------------------
Key: JBSER-115
URL:
https://jira.jboss.org/jira/browse/JBSER-115
Project: JBoss Serialization
Issue Type: Bug
Affects Versions: 1.0.3 GA
Environment: Deserializing client:
- OS: Windows XP SP3 (32Bit)
- JRE 1.6.0_14
Serializing Server:
- OS: Linux Suse Enterprise (64 Bit)
- JDK 1.6.0_13 (64 Bit)
Reporter: Mattias Neuling
Assignee: Clebert Suconic
Failure while deserilizing java.math.BigInteger in java.math.BigDecimal on client side:
Stacktrace:
java.io.IOException: Current classpath has lesser fields on java.math.BigInteger than its
original version
at org.jboss.serial.classmetamodel.StreamingClass.readStream(StreamingClass.java:98)
at
org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:381)
at
org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
at
org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:643)
at
org.jboss.serial.persister.RegularObjectPersister.readSlotWithFields(RegularObjectPersister.java:353)
at
org.jboss.serial.persister.ObjectInputStreamProxy.defaultReadObject(ObjectInputStreamProxy.java:78)
at java.math.BigDecimal.readObject(Unknown Source)
... 42 more
In JDK 1.6.0_14 java.math.BigInteger has one field more than in previous versions.
Serialization without JBoss Serialization is no problem since it implements the methods
#readObject() and #writeObject().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira