Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1052208

Summary: [GSS] (6.3.0) Protocol incompatibility between serializable classes with different non-serializable superclasses
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brad Maxwell <bmaxwell>
Component: RemotingAssignee: Brad Maxwell <bmaxwell>
Status: CLOSED DUPLICATE QA Contact: Jitka Kozana <jkudrnac>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: myarboro
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1032312 Environment:
Last Closed: 2014-01-13 13:55:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brad Maxwell 2014-01-13 13:50:34 UTC 
+++ This bug was initially created as a clone of Bug #1032312 +++

Protocol versions up to 3 of the River marshalling protocol erroneously serialize a class descriptor for the first non-serializable superclass of a serializable class.

This manifests itself particularly when an IBM JVM and a Sun JVM communicate by serializing a StringBuilder or StringBuffer class. The Sun JDK contains a shared superclass called AbstractStringBuilder which is not present in IBM's version.

In version 4 the stream should be marked with a NULL when the first non-serializable class is hit.  For version 3 though we can just mark it with java.lang.Object because that is also a single byte and should work as well (in 1.4 at least, this class is only used to detect the end of the chain; it is not used to make decisions about what constructor to invoke).  Only the sender needs to change; the receiver should continue functioning.

--- Additional comment from Brad Maxwell on 2013-11-19 19:24:47 EST ---

Fixed in JBoss Marshalling 1.4.3
Comment 1 Brad Maxwell 2014-01-13 13:55:05 UTC 

*** This bug has been marked as a duplicate of bug 1052204 ***