-
Bug
-
Resolution: Done
-
Major
-
7.1.0.GA
The primary symptom is errors indicating invalid backreferences in the midst of deserialization.
Transfer object failing to unmarshall with this error below. The same object was successfully working in EAP 5
java.rmi.RemoteException: Error; nested exception is: java.io.InvalidObjectException: Attempt to read a backreference with an invalid ID (relative near -4) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:236) ... at com.sun.proxy.$Proxy3.invoke(Unknown Source) at com.jboss.examples.Proxy.invoke(Proxy.java:123) at com.jboss.examples.SLSB.getData(SLSB.java:234) ... Caused by: java.io.InvalidObjectException: Attempt to read a backreference with an invalid ID (relative near -4) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:257) ... at java.io.ObjectInputStream.readObject(Unknown Source) at com.jboss.examples.model.Data$Value.readObject(TraceData.java:60) ... Caused by: an exception which occurred: in field tag in object of type com.jboss.examples.model.Data$Value in object of type com.jboss.examples.model.Data$ValueList in field pointList in object of type com.jboss.examples.model.Data$LoadList$Trace in element at index [10] of size [24] in field traces in object of type com.jboss.examples.model.Data$LoadList
- incorporates
-
JBMAR-218 Object replacement does not function correctly with null values
- Resolved
- is duplicated by
-
JBEAP-14287 [GSS](7.1.z) InvalidObjectException: Attempt to read a backreference with an invalid ID (relative near -4)
- Closed
- is incorporated by
-
JBEAP-14302 [GSS](7.1.z) Upgrade JBoss Marshalling to 2.0.4.Final-redhat-1 from 2.0.2.Final-redhat-1
- Closed