Tomcat RPC Failure on Lost Client Connections.

[Danny]

I get a " Exception while dispatching incoming RPC call" exception in
Tomcat after, what I believe is caused by an RPC response not finding
the client that made the request. The stack print out is included
below. I say that I believe this is the problem, but I have not been
able to reproduce the error.

Can someone with more Tomcat experience than me, see if my belief is
well founded? Regardless, does someone have a solution? My system
seems to be running OK. Is my worry mostly about Tomcat filling my
web host's disk space with exception messages?

Thanks,

Danny

----------------------------------------------------------------------------------------------

Nov 14, 2009 7:39:50 AM org.apache.catalina.core.ApplicationContext
log
SEVERE: Exception while dispatching incoming RPC call
java.io.IOException
at org.apache.jk.common.JkInputStream.receive(JkInputStream.java:205)
at org.apache.jk.common.JkInputStream.refillReadBuffer
(JkInputStream.java:265)
at org.apache.jk.common.JkInputStream.doRead(JkInputStream.java:183)
at org.apache.coyote.Request.doRead(Request.java:428)
at org.apache.catalina.connector.InputBuffer.realReadBytes
(InputBuffer.java:304)
at org.apache.tomcat.util.buf.ByteChunk.substract(ByteChunk.java:405)
at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:
327)
at org.apache.catalina.connector.CoyoteInputStream.read
(CoyoteInputStream.java:193)
at com.google.gwt.user.server.rpc.RPCServletUtils.readContentAsUtf8
(RPCServletUtils.java:146)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.readContent
(RemoteServiceServlet.java:343)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
(RemoteServiceServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service
(CoyoteAdapter.java:293)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:
190)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:
291)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
at org.apache.jk.common.ChannelSocket.processConnection
(ChannelSocket.java:698)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt
(ChannelSocket.java:891)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:690)
at java.lang.Thread.run(Thread.java:619)

[t.dave]

there's a bit of content on the web about this problem. if memory
serves it was at least partly blamed on the
RPCServletUtils.readContentAsUtf8() method - that sometimes the
request doesn't make it to the server. this was blamed on the
vagaries of the internet.

i have it all the time in my web app - probably at least once a day,
but have been unable to replicate it or track down the exact cause.
what version of GWT are you running? i'm still on 1.5.3 - my hope is
that once i finally get around to rewriting ALL my listeners into a
handler bus and upgrade to 1.7 (or even 2.0 by the time i get to it),
this problem will be solved.

[Danny]

t.dave,

I am using 1.7. Though it is no solution, your having this same
problem is some comfort. If enough of us are in the same boat, maybe
one of us will eventually find a solution.

Thanks,

Danny