An IncompatibleRemoteServiceException was thrown

1,172 views
Skip to first unread message

Rob Tanner

unread,
Sep 15, 2011, 2:27:02 PM9/15/11
to Google Web Toolkit
Hi,

An application I build with GWT 2.1 in Eclipse (v3.5, Classic) worked
just fine in tomcat. However, I've upgraded my environment to Eclipse
Indigo (EE version) and GWT 2.3 and the same app will not run on the
production servers, but builds and runs fine in the development
environment. Since I'm testing GlassFish with the intention of moving
away from Tomcat, I tried the app there and got an extensive stack
trace error report:

WebModule[/AccountRequest]AuthenService: An
IncompatibleRemoteServiceException was thrown while processing this
call.
com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException:
Invalid type signature for
org.linfield.accountRequest.client.AsyncServices.DataToken at
com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:315) at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:
206) at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:
248) at
com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:
62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:755) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at
org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:
1534) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:
281) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:
175) at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:
655) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
595) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:
91) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:
162) at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:
326) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:
227) at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:
170) at
com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:
822) at
com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:
225) at
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:
137) at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:
104) at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:
90) at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:
79) at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:
54) at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:
59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at
com.sun.grizzly.util.AbstractThreadPool
$Worker.doWork(AbstractThreadPool.java:532) at
com.sun.grizzly.util.AbstractThreadPool
$Worker.run(AbstractThreadPool.java:513) at
java.lang.Thread.run(Thread.java:662) Caused by:
com.google.gwt.user.client.rpc.SerializationException: Invalid type
signature for
org.linfield.accountRequest.client.AsyncServices.DataToken at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.validateTypeVersions(ServerSerializationStreamReader.java:
931) at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserialize(ServerSerializationStreamReader.java:
545) at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(AbstractSerializationStreamReader.java:
119) at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader
$ValueReader$8.readValue(ServerSerializationStreamReader.java:138) at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserializeValue(ServerSerializationStreamReader.java:
385) at com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:
303) ... 30 more

Since the app was simply imported and not built from scratch on
Indigo, are there settings I need to play with? Any ideas?

Thanks,

Rob Tanner
Linfield College

Rob Tanner

unread,
Sep 15, 2011, 8:04:16 PM9/15/11
to Google Web Toolkit
I figured the problem must be 2.1 residue in a GWT 2.3 build. So an
that assumption I deleted all those may directories that running in
development mode and compiling builld. They contain javascript and
xml files and a few other sundry type. I recompiled and all those
directories cam back but with 2.3 content only. The problem went
away.

~ Rob

-sowdri-

unread,
Sep 16, 2011, 11:58:02 PM9/16/11
to google-we...@googlegroups.com
Rob,, 

The fundamental reason for the problem is, as you have rightly guessed there were residues. But what caused these residues? 

If you are using GPE, the first time you run it, it would ask for webapp directory. Select target/<web-app-name> for that. Do not use src/main/webapp which is for a different purpose. 

Do check if you still have GWT compiler output in src/main/webapp, if yes, you are likely to run into the same problem again!

Hope this helps,,
Reply all
Reply to author
Forward
0 new messages