I have an app that was working fine in 1.0.21, but is breaking during
the deserialization of an RPC request in 1.1. The problem is that
AbstractSerializationStreamReader's fSeenArray member variable doesn't
contain as many items as the code is expecting it to. (trace below)

Has anyone else seen this? Any further debug tips?

[WARN] StandardContext[]Exception while dispatching incoming RPC call
com.google.gwt.user.client.rpc.SerializationException:
java.lang.reflect.InvocationTargetException
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseriz eWithCustomSerializer(ServerSerializationStreamReader.java:250)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lize(ServerSerializationStreamReader.java:138)
        at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readO bject(AbstractSerializationStreamReader.java:59)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lizeValue(ServerSerializationStreamReader.java:61)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lizeClass(ServerSerializationStreamReader.java:189)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lize(ServerSerializationStreamReader.java:147)
        at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readO bject(AbstractSerializationStreamReader.java:59)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lizeValue(ServerSerializationStreamReader.java:61)
        at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServi ceServlet.java:249)
        at
com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceSer vlet.java:147)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
Caused by: java.lang.reflect.InvocationTargetException: null
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseriz eWithCustomSerializer(ServerSerializationStreamReader.java:239)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lize(ServerSerializationStreamReader.java:138)
        at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readO bject(AbstractSerializationStreamReader.java:59)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lizeValue(ServerSerializationStreamReader.java:61)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lizeClass(ServerSerializationStreamReader.java:189)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lize(ServerSerializationStreamReader.java:147)
        at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readO bject(AbstractSerializationStreamReader.java:59)
Caused by: java.lang.IndexOutOfBoundsException: Index: 31, Size: 15
        at java.util.ArrayList.RangeCheck(ArrayList.java:546)
        at java.util.ArrayList.get(ArrayList.java:321)
        at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readO bject(AbstractSerializationStreamReader.java:49)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lizeValue(ServerSerializationStreamReader.java:61)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lizeClass(ServerSerializationStreamReader.java:189)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lize(ServerSerializationStreamReader.java:147)
        at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readO bject(AbstractSerializationStreamReader.java:59)
        at
com.google.gwt.user.client.rpc.core.java.util.ArrayList_CustomFieldSerializ er.deserialize(ArrayList_CustomFieldSerializer.java:34)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:25)

Hi jon,

Hard to tell much from the trace, but if you can email me your project
I'd be happy to look at it.

Scott

Jon,

After examining your trace in more detail and correlating it with a problem
that's been found, I may have a fix for you:

With a zip utility, go into
gwt-user.jar/com/google/gwt/user/client/rpc/impl/ClientSerializationStreamW riter.java,
line 101.  Change that line to read:

setIntForInt(System.identityHashCode(instance), objectCount++);

You may have to pull the file out of the jar, edit it, and replace it
depending on your zip editor's capabilities.

Does this fix your problem?

Scott

On 8/15/06, jon918 <jon...@gmail.com> wrote:

Scott,

Your suggestion did in fact fix the problem. Sorry it took me a while
to get back to you.

Thanks for the quick feedback. Keep up the great work GWT team!

Jon

Hi, Scott.
I experienced problems (stack overflow) during serialization of objects
with bidirectional relation, in version 1.1
I found the same cause and did the same fix and it worked.
It's a bug, nothing to say....

Thanks, Andrey.

Yes, this one bug is responsible for all sorts of flaky behavior, from
infinite loops on the client to a failure to deserialize on the
server.  This bug is probably the worst one we've let out the door!
We're going to be putting out a bugfix release soon with this fixed.

Scott

Took me some 2 days and a lot of debugging until realised it must be a
bug.

Tnx for the hot fix tough. I'll post back after i try it.