• Welcome to KonaKart Community Forum. Please login or sign up.
 

GWT RPC ServletException, please help

Started by lvfisher, October 18, 2008, 12:37:46 am

Previous topic - Next topic

lvfisher

Hi,

I am calling another GWT app from within KK.  The app uses an RPC servlet.  When the servlet is called, I get the following error. 

"Exception while dispatching incoming RPC call javax.servlet.ServletException: Content-Type must be 'text/plain' with 'charset=utf-8'"

The GWT app was developed with GWT 1.5.2.

What version of GWT does KK use anyway?

Below is a log.

Anyone interested in helping?

Thank you.

17-Oct 17:31:10 ERROR (ApplicationContext.java:log:675) Exception while dispatch
ing incoming RPC call
javax.servlet.ServletException: Content-Type must be 'text/plain' with 'charset=
utf-8' (or unspecified charset)
        at com.google.gwt.user.server.rpc.RemoteServiceServlet.readPayloadAsUtf8
(RemoteServiceServlet.java:119)
        at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServ
iceServlet.java:178)
        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(Appl
icationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:869)
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p
rocessConnection(Http11BaseProtocol.java:664)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:527)
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
        at java.lang.Thread.run(Thread.java:619)

kate

The 2.2.6.0 release uses GWT 1.4.61 - but we have plans to use 1.5.2 in the next release.

Could it be that you're getting problems with incompatible gwt jars?

Kate

lvfisher

Thank you for your response, Kate.

Yes, Googling seems to indicate that this problem has occurred for some when moving from 1.4 to 1.5. 

Do you know when the next release may happen? 

Meanwhile, I will try to find what is needed to build with 1.4.61 to see if that affects the problem.

Regards  :)

kate

Hi,

I'm afraid I don't know when the next release is due out... however there are no immediate plans.

Kate

lvfisher

Kate,
For those who may have similar exceptions when using recent version of GWT, I modified my GWT app for 1.4.62 and that does fix the problem.  Thank you.