About java.net.SocketException
Richard De Falco
i'm currently evaluating wl 7.0 sp1. I've seen many posts speaking
about this exception relating to previous versions of weblogic (since
V5!) and obviously it's still there in weblogic 7. Below is the stack
trace i have when i hit "refresh" two times in a row with my IE 6
browser. What's the current status of this issue on weblogic 7 sp1
(which is the latest version available i think..)? Is this a bug, or
not, harmless or not, may be something wrong in the app i try to run
(currently running juniteeservlet with empty tests)? Are there any
means to get rid of this message, which could lead our clients to
think there is something wrong with us or with weblogic server ?
Richard
<25 fÚvr. 03 17:39:36 CET> <Error> <HTTP> <101083> <Connection failure
java.net.SocketException: ReadFile failed: Le nom rÚseau spÚcifiÚ
n'est plus disponible.
(error 64, fd 2396)
at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
at weblogic.socket.NTSocketMuxer.initiateIO(NTSocketMuxer.java:463)
at weblogic.socket.NTSocketMuxer.read(NTSocketMuxer.java:429)
at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java:292)
at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1188)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2549)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
>
Mark Griffith
This is analogous to broken pipe. Ie. something went wrong when reading
from the socket. In otherwords the connection between client and server was
interrupted. It could be for a variety of reasons, in your case its because
you reset it when you hit refresh. We log it because it also could be
because some other error in the network between the client and server.
cheers
mbg
"Richard De Falco" <rdef...@icominfo.fr> wrote in message
news:c16491fe.0302...@posting.google.com...