GWT-RPC: encodedRequest cannot be empty error

76 views
Skip to first unread message

kishorpatel415

unread,
Mar 22, 2012, 11:37:29 AM3/22/12
to google-we...@googlegroups.com
Hello,

We are using GWT 2.3 in our web application. In our log files we see the error "encodedRequest cannot be empty". This error occurs when we make GWT-RPC calls. The error is intermittent. It does not happen all of the time. Based on the log file data, it happens approx 5% of the time for GWT-RPC calls.

Any work arounds for resolving this? Thanks.

Stack Trace:
java.lang.IllegalArgumentException: encodedRequest cannot be empty
    at com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:229)
    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:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

Client Environment:
Microsoft Internet Explorer 8
MS Windows 7

Server Environment:
Tomcat 7
MS Windows 2008
JDK 1.6
GWT 2.3


Reply all
Reply to author
Forward
0 new messages