Hi,
I am running my application in weblogic server 8.1,when i deploy the application in exploded format i get the following error
Connection reset by peer:Socket write error
However the application seems to work fine.Also, no errors are displayed when the application is packaged as an EAR.
Any help will be appreciated.
Hi,
Thanks for replying.
Following is the eror message i get
<Mar 25, 2006 12:44:42 PM GMT+05:30> <Error> <HTTP> <BEA-101017> <[ServletContex
t(id=442653,name=cssweb,context-path=/cssweb)] Root cause of ServletException.
javax.servlet.jsp.JspException: error in HelloWorld3Tag: java.net.SocketExceptio
n: Connection reset by peer: socket write error
at com.sns.pfk.taglib.PfkBaseTag.handleBodyContentException(PfkBaseTag.j
ava:102)
at com.sns.pfk.taglib.PfkBaseTag.doAfterBody(PfkBaseTag.java:78)
at jsp_servlet._css.__index._jspService(__index.java:364)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6354)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
Hi,
I get the same error when the network connection goes down, since my Backend is hosted on another machine and so is the server. so when the network breaks down in between it gives you an error , but you can reconnect the applcn and it will work fine.
u also get a similar error when u r using toad and the network is disconnected due to some reason.
so i feel it may be due to the DB conncn breaking down.
Hope this helps.
Regards,
Ashaya.
Hi,
I am playing a .wav file in the mediaplayer in my jsp. The URL maps to the servlet where I am reading the .wav file which is in my local. When running the program in my local, I dont get any problems. Everything is working fine. But when I connect to the server of my collegue, who has the same piece of code, he gets exceptions.
[7/07/06 10:34:42:489 CEST] 5adf7d0f SystemOutO Inside the doPost NSPlayer/9.0.0.3250 WMFSDK/9.0
[7/07/06 10:34:42:599 CEST] 5adf7d0f WebGroupE SRVE0026E: [Servlet Error]-[Connection reset by peer: socket write error]: java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java(Compiled Code))
at com.ibm.ws.io.Stream.write(Stream.java(Compiled Code))
at com.ibm.ws.io.WriteStream.flushMyBuf(WriteStream.java(Inlined Compiled Code))
at com.ibm.ws.io.WriteStream.write(WriteStream.java(Compiled Code))
at com.ibm.ws.http.ResponseStream.writeChunk(ResponseStream.java(Compiled Code))
at com.ibm.ws.http.ResponseStream.flushBuffer(ResponseStream.java(Compiled Code))
at com.ibm.ws.http.ResponseStream.write(ResponseStream.java(Compiled Code))
at com.ibm.ws.io.WriteStream.write(WriteStream.java(Compiled Code))
at com.ibm.ws.webcontainer.http.HttpConnection.write(HttpConnection.java:362)
at com.ibm.ws.webcontainer.srp.SRPConnection.write(SRPConnection.java:224)
at com.ibm.ws.webcontainer.srt.SRTOutputStream.write(SRTOutputStream.java:89)
at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.writeOut(BufferedServletOutputStream.java:440)
at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.write(BufferedServletOutputStream.java:306)
at mediaplayer.TestServlet.doPost(TestServlet.java:55)
at mediaplayer.TestServlet.doGet(TestServlet.java:30)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:61)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:939)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:435)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
This could not be due to IE or firefox becoz, he gets the same exception in firefox also. Can anyone help?
What is the sol 4 IE ?
> This happens a lot with IE. It sometimes doesn't shut
> down the socket properly when it's receiving data.
> There's not a whole lot you can do about it and it
> doesn't really hurt anything, it's just noisy in the
> logs.
>
> Try running with Firefox and you should not see that
> error.
