Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

java.net.SocketException: Connection reset by peer

2 views
Skip to first unread message

Yann

unread,
Jul 26, 2002, 4:37:45 AM7/26/02
to

Hi,

I found a related article on weblogic.developer.interest.connector :
>This is not a problem. It is an error message that you can safely ignore (that
we should not be printing) and have fixed in version 6.0.

--

Unfortunately we are upgrading from 5.1 to 6.1sp2 and this became a problem for
us. Indeed we just ignored this exception in 5.1, but today with 6.1sp2, we get
it each time we do a RequestDispatcher.forward(). The forward is done, we come
on the target JSP, but every attributes set on the request are lost !!

At first I thought it was related with the NTSocketMuxer (NT Performance Pack
?) : I got a (french = network name not available anymore):

java.net.SocketException: ReadFile failed: Le nom réseau spécifié n'est plus disponible.
(error 64, fd 1224)
at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
at weblogic.socket.NTSocketMuxer.read(NTSocketMuxer.java:410)
at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java:217)
at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:992)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2209)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

I removed the property NativeIOEnabled but I still get a :

ven. 20020726 09:11:31 CEST <0> java.net.SocketException: Connection reset by
peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:83) at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:380)
at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:827)
at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:222)
at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:113)
at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:446)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.forwardScreen(TeamsWebScreenBuilder.java:155)
at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.build(TeamsWebScreenBuilder.java:98)
at cegedim.tvf.koala.servlet.GlobalServlet.callResultBuilder(GlobalServlet.java:365)
at cegedim.tvf.teamsweb.servlet.ConnectionServlet.doPost(ConnectionServlet.java:112)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Thanks for any ideas

Nagesh Susarla

unread,
Jul 29, 2002, 2:50:24 PM7/29/02
to
What exactly is the client doing in this case ?
i.e. was it refreshed. Did it abort the socket without reading all the
data. A socketWrite error typically means that the client abnormally
terminated the socket.
e.g. client might have aborted by not reading all data from the
inputStream

-nagesh

0 new messages