Folks,
We have run into a situation where an xml-rpc client makes an invocation on an xml-rpc server and the xml-rpc server times out while reading the payload in...it seems like that anyway. On the client side, we catch an XmlRpcException that looks like it wraps a java.io.InterruptedIOException: throwable=org.apache.xmlrpc.XmlRpcException: java.lang.Exception: java.io.InterruptedIOException: org.apache.xmlrpc.XmlRpcClient$Worker.execute(Unknown Source) org.apache.xmlrpc.XmlRpcClient.execute (Unknown Source) On the server side, our handler is never invoked and the timeout occurs when parse(InputStream) is being invoked. Strangely enough, the server side stack trace looks like the following, but it implies that the time out occurred when it was sending back the response. Fatal error parsing XML: java.io.InterruptedIOException: Read timed out <Feb 25, 2004 10:29:55 AM GMT> <Error> <HTTP> <[WebAppServletContext(3140348,X,/X)] Servlet failed with IOException java.io.InterruptedIOException: Read timed out at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:85) at weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:170) at java.io.InputStream.skip(InputStream.java:214) at weblogic.servlet.internal.ServletInputStreamImpl.skip(ServletInputStream Impl.java:189) at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputSt reamImpl.java:501) at weblogic.servlet.internal.ChunkOutput.commit(ChunkOutput.java:248) at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.ja va:128) at weblogic.servlet.internal.ServletOutputStreamImpl.write(ServletOutputStr eamImpl.java:171) at java.io.OutputStream.write(OutputStream.java:56) at com.my.servlet.XmlRpcServlet.doPost(XmlRpcServlet.java:108) Could it be that when the server is trying to read in the payload it times out and then streams back an XmlRpcException that wraps an IOException? If so, shouldn't the XmlRpcClient.execute throw back an IOException since the invocation did not properly complete? Has anyone run into this before? We are using 1.1. I suspect there is some kind of funky network glitch that is causing this problem and happens sporadically. Thanks in advance..and please let me know if you need more information. Al
