I see there was some discussion in April, but I didn't see
any sign of resolution.
Is there a fix? I'm eventually getting pages that appear
correct,
but I'm concerned that the repeated exceptions will degrade
performance if we upgrade to 5.1.
Thanks,
Jonathan
-brian
"Jonathan Hendry" <jhe...@shrike.depaul.edu> wrote in message
news:396609a9$1...@newsgroups.bea.com...
-Dominic
Dominic Tulley <dom...@qss.co.uk> wrote in message
news:396AF86E...@qss.co.uk...
java.net.SocketException: socket write error (code=10053)
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java,
Compiled Code)
at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java,
Compiled Code)
at
weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
mpl.java, Compiled Code)
at
weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputS
treamImpl.java, Compiled Code)
at weblogic.servlet.FileServlet.sendFile(FileServlet.java, Compiled
Code)
at weblogic.servlet.FileServlet.service(FileServlet.java, Compiled
Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java, Compiled
Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java, Compiled Code)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
Nachiappan A <nachi...@wisorindia.soft.net> wrote in message
news:3973...@newsgroups.bea.com...