file upload, java.io.InterruptedIOException, read timed out

[Anony]

My situation:

Websphere 4.0.5 and IBM's HTTP server

File upload via HTTP POST

multipart/form-data

Content-length=4261138

Here is the stack trace:

error: ControlServlet: java.io.InterruptedIOException: Read timed out

null

java.io.InterruptedIOException: Read timed out

at java.net.SocketInputStream.socketRead(Native Method)

at java.net.SocketInputStream.read(Unknown Source)

at com.ibm.ws.io.Stream.read(Stream.java:17)

at com.ibm.ws.io.ReadStream.read(ReadStream.java:183)

at
com.ibm.ws.http.ContentLengthInputStream.read(ContentLengthInputStream.java:
34)

at com.ibm.ws.io.ReadStream.read(ReadStream.java:183)

at
com.ibm.servlet.engine.http11.HttpConnection.read(HttpConnection.java:344)

at
com.ibm.servlet.engine.srp.SRPConnection.read(SRPConnection.java:200)

at
com.ibm.servlet.engine.srt.SRTInputStream.read(SRTInputStream.java:74)

at
com.ibm.servlet.engine.srt.http.HttpInputStream.read(HttpInputStream.java:30
1)

at
com.oreilly.servlet.multipart.BufferedServletInputStream.fill(BufferedServle
tInputStream.java:64)

at
com.oreilly.servlet.multipart.BufferedServletInputStream.readLine(BufferedSe
rvletInputStream.java:108)

at
com.oreilly.servlet.multipart.LimitedServletInputStream.readLine(LimitedServ
letInputStream.java:60)

at
com.oreilly.servlet.multipart.PartInputStream.fill(PartInputStream.java:93)

at
com.oreilly.servlet.multipart.PartInputStream.read(PartInputStream.java:191)

at
com.oreilly.servlet.multipart.PartInputStream.read(PartInputStream.java:152)

at
com.oreilly.servlet.multipart.FilePart.write(FilePart.java:201)

at
com.oreilly.servlet.multipart.FilePart.writeTo(FilePart.java:160)

at
com.oreilly.servlet.MultipartRequest.<init>(MultipartRequest.java:314)

at
com.oreilly.servlet.MultipartRequest.<init>(MultipartRequest.java:211)

at foobar.ControlServlet.doPost(ControlServlet.java:229)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:827)

at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:167)

at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:297)

at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:110)

at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:47
2)

at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:1012)

at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:913)

at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java:721)

at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java:374)

at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.java:118)

at
com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)

at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java:239)

at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)

at
com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(Cacheabl
eInvocationContext.java:106)

at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:154)

at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:315)

at
com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.ja
va:60)

at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:323)

at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:252)

at com.ibm.ws.util.CachedThread.run(ThreadPool.java:138)

[art s]

I suggest changing "Error" to "Trace" in the HTTP server plugin's plugin-cfg.xml
file to see what may be happening at that level. I'm guessing the content
length header specified on the POST (4261138 bytes) is not being sent by the
plugin for some reason or in a timely manner. Maybe the client is physically
short some bytes, or maybe the client is taking a while sending it to the HTTP
server, etc. See if you can figure out from the plugin trace what's happening
there.

[Swamy]

We had similar issue. Cummulative fixpack fixed this problem.
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q=fixpack+4.0.6&uid=swg24004769&loc=en_US&cs=utf-8&lang=en

Swamy

"Anony" <anon_...@notahost.org> wrote in message
news:bgv6vq$3ov8$1...@news.boulder.ibm.com...