Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Websphere, file upload error: "Read timed out"

 
Ranch Hand
Posts: 427
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using Struts 1.1 in Websphere 5.0.1

I am trying to use Struts' FormFile feature to receive an uploaded file.

The file upload is failing due to a "Read timed out" error. The error
occurs when Struts is trying to read data from the InputStream for the
HttpServletRequest object.

Is this a known issue in Websphere 5.0.1? Is there a solution and/or
workaround?

This is what I see in my log file:


[12/9/04 10:24:44:398 PST] 42ed36e3 WebGroup E SRVE0026E: [Servlet
Error]-[Processing of multipart/form-data request failed. Read timed
out]: org.apache.commons.fileupload.FileUploadException: Processing of
multipart/form-data request failed. Read timed out
at
org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase
.java(Compiled Code))
at
org.apache.struts.upload.CommonsMultipartRequestHandler.handleRequest(Co
mmonsMultipartRequestHandler.java:195)
at
org.apache.struts.util.RequestUtils.populate(RequestUtils.java:445)
at
org.apache.struts.action.RequestProcessor.processPopulate(RequestProcess
or.java:798)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
205)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictSe
rvletInstance.java:110)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLi
fecycleServlet.java:174)
at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycle
Servlet.java:313)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLif
ecycleServlet.java:116)
at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.
java:283)
at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(Vali
dServletReferenceState.java:42)
at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(Servle
tInstanceReference.java(Inlined Compiled Code))
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispa
tch(WebAppRequestDispatcher.java(Compiled Code))
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRe
questDispatcher.java(Compiled Code))
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppReq
uestDispatcher.java(Compiled Code))
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:7
9)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInv
oker.java:201)
at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocati
on(CachedInvocation.java:71)
at
com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invo
ke(CacheableInvocationContext.java:114)
at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(Servle
tRequestProcessor.java:186)
at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSELis
tener.java:334)
at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection
.java:56)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:
516)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:362)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)


[12/9/04 10:24:57:884 PST] 42ed36e3 SRTServletReq E SRVE0120E: IO Error
java.io.InterruptedIOException: Read timed out
at com.ibm.sslite.s.a(Unknown Source)
at com.ibm.sslite.a.read(Unknown Source)
at com.ibm.jsse.a.read(Unknown Source)
at com.ibm.ws.io.Stream.read(Stream.java(Compiled Code))
at com.ibm.ws.io.ReadStream.read(ReadStream.java(Compiled Code))
at
com.ibm.ws.http.ContentLengthInputStream.read(ContentLengthInputStream.j
ava(Compiled Code))
at com.ibm.ws.io.ReadStream.read(ReadStream.java(Compiled Code))
at
com.ibm.ws.webcontainer.http.HttpConnection.read(HttpConnection.java(Inl
ined Compiled Code))
at
com.ibm.ws.webcontainer.srp.SRPConnection.read(SRPConnection.java(Compil
ed Code))
at
com.ibm.ws.webcontainer.srt.SRTInputStream.read(SRTInputStream.java(Comp
iled Code))
at
com.ibm.ws.webcontainer.srt.http.HttpInputStream.read(HttpInputStream.ja
va(Compiled Code))
at java.io.InputStream.read(InputStream.java:105)
at
com.ibm.ws.webcontainer.srt.SRTServletRequest.finish(SRTServletRequest.j
ava:995)
at
com.ibm.ws.webcontainer.srt.SRTConnectionContext.finishConnection(SRTCon
nectionContext.java:86)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:1
32)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInv
oker.java:201)
at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocati
on(CachedInvocation.java:71)
at
com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invo
ke(CacheableInvocationContext.java:114)
at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(Servle
tRequestProcessor.java:186)
at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSELis
tener.java:334)
at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection
.java:56)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:
516)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:362)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
 
Sean Sullivan
Ranch Hand
Posts: 427
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I talked to IBM support.

IBM acknowledged that there is a bug in Websphere 5.0.1's web container.

They referred me to these resources:

PQ82068; 5.1.0.3: ConnectionIOTimeout setting can cause keep alive timeout

http://www-1.ibm.com/support/docview.wss?uid=swg24006790

HTTP transport custom properties

http://publib.boulder.ibm.com/infocenter/ws51help/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/xrun_transport.html
 
What do you have to say for yourself? Hmmm? Anything? And you call yourself a tiny ad.
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic