Error executing RPC call after updating to GWT 1.5.3

[a_martinez]

Hi,
I developed an application with several services. After updating from
GWT 1.5.2 to 1.5.3 the RPC calls to the server doesn't work anymore. I
got an error message on server side:


java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.extract
(ServerSerializationStreamReader.java:617)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readInt
(ServerSerializationStreamReader.java:432)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.prepareToRead
(AbstractSerializationStreamReader.java:38)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepareToRead
(ServerSerializationStreamReader.java:383)
at com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:234)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall
(RemoteServiceServlet.java:163)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
(RemoteServiceServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter
(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke
(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke
(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke
(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service
(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process
(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol
$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:
664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket
(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run
(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:619)



This is how I call the service:

diversePanel.add(new Button("Pseudo Login", new ClickListener() {
public void onClick(Widget sender) {
RemoteTypeDefServiceAsync typeDefService =
(RemoteTypeDefServiceAsync) GWT.create(RemoteTypeDefService.class);
ServiceDefTarget target = (ServiceDefTarget)
typeDefService;
String serviceEntryPoint = GWT.getModuleBaseURL()
+"TypeDefService";
target.setServiceEntryPoint(serviceEntryPoint);
AsyncCallback callback = new AsyncCallback(){
public void onFailure(Throwable caught){
Window.alert("Login failed.");
}

public void onSuccess(Object result){
Window.alert("Login ok.");
}
};
typeDefService.pseudoLogin(callback);
}
}));

Can someone tell me what is wrong now?

[Danny Goovaerts]

I've experienced the same problem. Be sure to use the 1.5.3 version of
the gwt-servlet.jar in your Tomcat deployment. This fixed the problem
for me.
Danny
a_martinez schreef:

[NItin]

Hi Danny,

I checked gwt-servlet.jar version , its of GWT 1.5.3' s library

In my case, some of the RPC calls are working but, some specific RPC
calls are getting failed with this exception only in IE ( in case of
firefox all RPC calls are successful).


Thanks

On Dec 9, 4:57 pm, Danny Goovaerts <danny.goovae...@gmail.com> wrote:
> I've experienced the same problem. Be sure to use the1.5.3version of

> thegwt-servlet.jar in your Tomcat deployment. This fixed the problem

> for me.
> Danny
> a_martinez schreef:
>
> > Hi,
> > I developed an application with several services. After updating from

> >GWT1.5.2 to1.5.3the RPC calls to the server doesn't work anymore. I

[mgrouch]

We are experiencing same issue. The app build on windows and running
on windows tomcat work.
Same application built on linux with gwt 1.5.3 and linux tomcat gives
this error.
If you managed to resolve it please be kind and post here how you did
it.

Thanks a lot,
--MG

[Sam sem]

 Make Sure You are only using Jars of 1.5.3 .........remove Gwt-user and Gwt-servlet jars from your build path and place jars from version 1.5.3 ........also Update your GWT_HOME ......make sure GWT_HOME points to GWT Version 1.5.3

Thanks

Muhammad Ismail
cell (PAK) : +92.322.5100362
e-mail: sam...@gmail.com
web: http://sam4sem.wordpress.com/

This message may contain confidential and/or privileged information.  If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein.  If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.  Thank you for your cooperation.

Chat: Skype: persontation_support

--- @ WiseStamp Signature. Get it now

[mgrouch]

Thanks and nope this doesn't seem to fix it.
We are using only GWT 1.5.3 jars.
When we build on windows and deploy resulting WAR on Linux tomcat
there is no issue.
When we build with GWT 1.5.3 on linux and deploy resulting WAR on
Linux tomcat the issue occurs.
Is there a possibility that it is a bug of GWT 1.5.3 on linux.
GWT_HOME is not set at all.

RPC call we are doing is very simple. It returns a TO object which
implements IsSerializable

public class UserInfoTO extends BaseTO
{
private static final long serialVersionUID =
-5442696946109605093L;

public String webUserName;
public int userSessionTimeoutMillis;

public UserInfoTO()
{
}
}

public abstract class BaseTO implements IsSerializable, Serializable
{
private static final long serialVersionUID =
-6694354604015088934L;
}

Thanks again

On Jan 27, 5:07 am, Sam sem <sam4...@gmail.com> wrote:
>  Make Sure You are only using Jars of 1.5.3 .........remove Gwt-user and
> Gwt-servlet jars from your build path and place jars from version 1.5.3
> ........also Update your GWT_HOME ......make sure GWT_HOME points to GWT
> Version 1.5.3
>
> Thanks
>  Muhammad Ismail
> cell (PAK) : +92.322.5100362

> e-mail: sam4...@gmail.com
> web:http://sam4sem.wordpress.com/<http://www.zigron.com>

>
> This message may contain confidential and/or privileged information.  If you
> are not the addressee or authorized to receive this for the addressee, you
> must not use, copy, disclose or take any action based on this message or any
> information herein.  If you have received this message in error, please
> advise the sender immediately by reply e-mail and delete this message.
>  Thank you for your cooperation.

> Chat: Skype: persontation_support
>
> --- @ WiseStamp Signature. <http://www.wisestamp.com> Get it
> now<http://www.wisestamp.com>

[Sumit Chandel]

Hi mgrouch,

This is probably a step you've already taken, but in case you've observed this error using hosted mode with the -noserver option, have you checked that you've update the JARs on your web server to use the latest 1.5.3 gwt-servlet.jar file?

Also, for the RPC calls that you mentioned sometimes don't work, do you have an idea of the the size of the payload that should be going across the wire? We have seen some cases of RPC failure when transferring large payloads or complex objects before, so perhaps this is related.

Hope that helps,

-Sumit