WSAS 4.0.4 - InterruptedIOException

[gpferro]

Has anyone experienced this error message on WebSphere App Server
4.0.4 on pSeries? It appears at random in the application logs for one
application only. The other applications do not experience these
errors. Also, this only appears on our production system and not on
our staging or development systems running the same applications, so I
don't think it's application related. I've reinstalled the application
thinking it may have been hosing up the sockets, but this hasn't
helped. I'm planning on yanking out the application and rebuilding its
configuration, including the groups and clones. Any insights
appreciated...

[3/31/03 21:30:30:842 EST] 3983e356 SRTServletReq X SRVE0120E: IO
Error java.io.InterruptedIOException: Read timed out
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:113)
at com.ibm.ws.io.Stream.read(Stream.java:17)
at com.ibm.ws.io.ReadStream.read(ReadStream.java:176)
at com.ibm.ws.http.ContentLengthInputStream.read(ContentLengthInputStream.java:34)
at com.ibm.ws.io.ReadStream.read(ReadStream.java:176)
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:301)
at java.io.InputStream.read(InputStream.java:105)
at com.ibm.servlet.engine.srt.SRTServletRequest.finish(SRTServletRequest.java:830)
at com.ibm.servlet.engine.srt.SRTConnectionContext.finishConnection(SRTConnectionContext.java:86)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:194)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:239)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:151)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java: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:137)

[3/31/03 21:30:30:965 EST] 3983e356 WebGroup X Servlet Error:
Error while finishing the connection: java.io.InterruptedIOException:
Read timed out
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:113)
at com.ibm.ws.io.Stream.read(Stream.java:17)
at com.ibm.ws.io.ReadStream.read(ReadStream.java:176)
at com.ibm.ws.http.ContentLengthInputStream.read(ContentLengthInputStream.java:34)
at com.ibm.ws.io.ReadStream.read(ReadStream.java:176)
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:301)
at java.io.InputStream.read(InputStream.java:105)
at com.ibm.servlet.engine.srt.SRTServletRequest.finish(SRTServletRequest.java:830)
at com.ibm.servlet.engine.srt.SRTConnectionContext.finishConnection(SRTConnectionContext.java:86)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:194)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:239)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:151)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java: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:137)

[Mark Watzdorf]

The error message show is a classical example of a user cancelling a
http request. Indeed that's often application related. Assuming this
is a web based application here. The user sees no response or thinks
something is taking too long and hits reload, clicks submit again,
hits the back button or closes the browser. If he/she does that while
websphere was sending stuff to the browser you get this exception.
It's usually not really a problem. You could catch the exception, or
try preventing the user from reposting untill the page is done
processing. For example by making the page block posts after submit is
clicked, and using sequence numbers in the post so the modelmanage can
decide if it's a repost. Also try either shortening the time it takes
for the page to show anything the user can conclude from that
something is still happening: tactile feedback makes users happy.
They're used to the slow internet messing up and retrying so they'll
do the same when you're app isn't snappy in changing the page.
If you can't: it's not a biggy, just anoying clutter in the logs.

[gpferro]

mwwat...@chello.nl (Mark Watzdorf) wrote in message news:<d232dcb6.0304...@posting.google.com>...

Thanks for the response. Yes, it's a web app that connects to the
mainframe through mqseries and more. It can take several seconds to
get a response, but this started showing up in our logs last month.
I'm not overly concerned because no failed transactions, but thought
it could be environmental. I'll pass on your post and suggestions to
the developer.