SocketException: Connection aborted/reset by peer

Hi all,
I get the below exception sometimes.
What I want to learn is: what is the difference between Connection aborted by peer and Connection reset by peer and in which condition do they occur?
java.net.SocketException: Connection aborted by peer: socket write error
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(Unknown Source)

My understanding is that "Connection reset by peer" occurs on a read. A "Connection aborted by peer" occurs on a write. The former is more common and typically occurs when the connection is lost in the middle of a read or a write and is thus an unexpected event. i.e. The connection is not closed after a point where is might be expected to be closed.

Similar Messages

WEBDB network connection error - reset by peer

I'm experiencing a network connection error when connecting and
querying a database by way the WEBDB.
I got a pc running Oracle 8i on a RedHat Linux 6,, and on the
same
machine it's running webdb.
When i make a heavy query i got the connection error described on
the top (and in the subject).
null

Did you ever get a solution to this problem?
Patrick (guest) wrote:
: Fabrizio Guarino (guest) wrote:
: : I'm experiencing a network connection error when connecting
: and
: : querying a database by way the WEBDB.
: : I got a pc running Oracle 8i on a RedHat Linux 6,, and on the
: : same
: : machine it's running webdb.
: : When i make a heavy query i got the connection error
described
: on
: : the top (and in the subject).
: I'm having the same problem when working from any machine
other
: than the db server machine. It happens consistently from a
: parameter form for a report, or a query form for a table. Any
: query that takes more than a half or three quarters of a
second
: gets interupted with the "Connection to server was reset"
: error. Any help would be greatly appreciated.
null

Connection Reset by peer errors in Weblogic

Hi,
The weblogic server is throwing the following error , Any inputs to solve this will be highly appreciated.
####<Feb 2, 2006 3:43:11 PM CST> <Error> <HTTP> <xdaawsf001> <AWSServer> <ExecuteThread: '21' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-101017> <[ServletContext(id=20362550,name=eboq,context-path=/eboq)] Root cause of ServletException.
javax.servlet.jsp.JspException: Input/output error: java.net.SocketException: Connection aborted by peer
     at org.apache.struts.taglib.logic.IterateTag.doAfterBody()I(Optimized Method)
     at jsp_servlet._nse.__nse_edit_boq._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(__nse_edit_boq.java:2343)
     at weblogic.servlet.jsp.JspBase.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(Optimized Method)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(Optimized Method)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(Optimized Method)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ServletStubImpl.java:315)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(RequestDispatcherImpl.java:328)
     at org.apache.struts.action.RequestProcessor.doForward(Ljava.lang.String;Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(RequestProcessor.java:1069)
     at org.apache.struts.action.RequestProcessor.processForwardConfig(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;Lorg.apache.struts.config.ForwardConfig;)V(RequestProcessor.java:455)
     at org.apache.struts.action.RequestProcessor.process(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Optimized Method)
     at org.apache.struts.action.ActionServlet.process(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doGet(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ActionServlet.java:507)
     at javax.servlet.http.HttpServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(Optimized Method)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(Optimized Method)
     at weblogic.servlet.internal.TailFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(Optimized Method)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27)
     at com.nokia.ebom.auth.LoginFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(LoginFilter.java:64)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6724)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Optimized Method)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Optimized Method)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(Optimized Method)
     at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(Optimized Method)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(Optimized Method)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
can someone help?
Thanks
Zia.

hi,I meet the same problem now . My Weblogic edtion is 8.1.4. Have you solved this problem?
Can you tell me how ot solve this problem.
I from China. My EMAIL is : [email protected]
Thank you very much!

Rmi - connection aborted:socket write error

Weblogic 5.1 is running on my localhost and a remote object successfully registered on the weblogic. There is an applet trying to establish a connection and after the client is registered in the client list I get the following exception
Thu Jan 25 11:29:06 PST 2001:<E> <ServletContext-General> Servlet failed with Ex
ception
java.net.SocketException: Connection aborted 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.writeChunks(ChunkUtils.java:88)
at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutput
StreamImpl.java:121)
at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(Servlet
OutputStreamImpl.java:444)
at weblogic.servlet.ClasspathServlet.sendResource(ClasspathServlet.java:
114)
at weblogic.servlet.ClasspathServlet.doGet(ClasspathServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:105)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
textImpl.java:742)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
textImpl.java:686)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
ContextManager.java:247)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
a:361)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
And the java console shows this message:
java.lang.NoClassDefFoundError
at weblogic/rmi/extensions/BasicRequest.init (BasicRequest.java)
at weblogic/rmi/extensions/BasicRequest.<init> (BasicRequest.java:18)
at weblogic/rmi/extensions/AbstractRemoteObjectReference.getRequest (AbstractRemoteObjectReference.java:71)
at weblogic/jndi/internal/RemoteContextFactoryImpl_WLStub.getContext (RemoteContextFactoryImpl_WLStub.java:77)
at weblogic/jndi/WLInitialContextFactoryDelegate.newRemoteContext (WLInitialContextFactoryDelegate.java:316)
at weblogic/jndi/WLInitialContextFactoryDelegate.newContext (WLInitialContextFactoryDelegate.java:242)
at weblogic/jndi/WLInitialContextFactoryDelegate.getInitialContext (WLInitialContextFactoryDelegate.java:205)
at weblogic/jndi/Environment.getContext (Environment.java:122)
at weblogic/jndi/Environment.getInitialContext (Environment.java:105)
at weblogic/rmi/Naming.getContext (Naming.java:225)
at weblogic/rmi/Naming.lookup (Naming.java:67)
at AppletTest.init (AppletTest.java:30)
at com/ms/applet/AppletPanel.securedCall0 (AppletPanel.java)
at com/ms/applet/AppletPanel.securedCall (AppletPanel.java)
at com/ms/applet/AppletPanel.processSentEvent (AppletPanel.java)
at com/ms/applet/AppletPanel.processSentEvent (AppletPanel.java)
at com/ms/applet/AppletPanel.run (AppletPanel.java)
at java/lang/Thread.run (Thread.java
Can someone help solve this problem.
Thansk in advance,
Nirmal R.

The point where the failure occurs in in the initialization of the transaction framework, so I would guess that you do not have the plug-in for the applet.
Nirmal R wrote:
Weblogic 5.1 is running on my localhost and a remote object successfully registered on the weblogic. There is an applet trying to establish a connection and after the client is registered in the client list I get the following exception
Thu Jan 25 11:29:06 PST 2001:<E> <ServletContext-General> Servlet failed with Ex
ception
java.net.SocketException: Connection aborted 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.writeChunks(ChunkUtils.java:88)
at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutput
StreamImpl.java:121)
at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(Servlet
OutputStreamImpl.java:444)
at weblogic.servlet.ClasspathServlet.sendResource(ClasspathServlet.java:
114)
at weblogic.servlet.ClasspathServlet.doGet(ClasspathServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:105)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
textImpl.java:742)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
textImpl.java:686)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
ContextManager.java:247)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
a:361)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
And the java console shows this message:
java.lang.NoClassDefFoundError
at weblogic/rmi/extensions/BasicRequest.init (BasicRequest.java)
at weblogic/rmi/extensions/BasicRequest.<init> (BasicRequest.java:18)
at weblogic/rmi/extensions/AbstractRemoteObjectReference.getRequest (AbstractRemoteObjectReference.java:71)
at weblogic/jndi/internal/RemoteContextFactoryImpl_WLStub.getContext (RemoteContextFactoryImpl_WLStub.java:77)
at weblogic/jndi/WLInitialContextFactoryDelegate.newRemoteContext (WLInitialContextFactoryDelegate.java:316)
at weblogic/jndi/WLInitialContextFactoryDelegate.newContext (WLInitialContextFactoryDelegate.java:242)
at weblogic/jndi/WLInitialContextFactoryDelegate.getInitialContext (WLInitialContextFactoryDelegate.java:205)
at weblogic/jndi/Environment.getContext (Environment.java:122)
at weblogic/jndi/Environment.getInitialContext (Environment.java:105)
at weblogic/rmi/Naming.getContext (Naming.java:225)
at weblogic/rmi/Naming.lookup (Naming.java:67)
at AppletTest.init (AppletTest.java:30)
at com/ms/applet/AppletPanel.securedCall0 (AppletPanel.java)
at com/ms/applet/AppletPanel.securedCall (AppletPanel.java)
at com/ms/applet/AppletPanel.processSentEvent (AppletPanel.java)
at com/ms/applet/AppletPanel.processSentEvent (AppletPanel.java)
at com/ms/applet/AppletPanel.run (AppletPanel.java)
at java/lang/Thread.run (Thread.java
Can someone help solve this problem.
Thansk in advance,
Nirmal R.

JCOM throwing SocketException: Connection reset by peer: socket write error

I have an ejb which is calling a simple ActiveX component using JCOM.
Ocassionally the ejb loses the ability to connect to the ActiveX component. Any attempt to call a method results in a java.net.SocketException: Connection reset by peer: socket write error.
However the ActiveX component continues to run correctly. I can still connect to it using a vb test client. This is using com to connect, not DCOM as used by JCOM(JIntegra).
The application server and the ActiveX component are running on the same server.
Any suggestions as to why the JIntegra DCOM request could be failing?
Thanks,
Greg.

I have an ejb which is calling a simple ActiveX component using JCOM.
Ocassionally the ejb loses the ability to connect to the ActiveX component. Any attempt to call a method results in a java.net.SocketException: Connection reset by peer: socket write error.
However the ActiveX component continues to run correctly. I can still connect to it using a vb test client. This is using com to connect, not DCOM as used by JCOM(JIntegra).
The application server and the ActiveX component are running on the same server.
Any suggestions as to why the JIntegra DCOM request could be failing?
Thanks,
Greg.

How to avoid a SocketException: Connection reset by peer

Hi,
My problem sounds very simple at first, but I couldn't figure out how to get out of it. It's tricky.
A have a JSP page which makes some processing and yields output to the user. Everything runs OK, until the user decide to stop the window (or to close the window) before the results render to the browser. When the next browser tries to load this page, the right page is loaded, but before it, the error garbage (error page, stack trace) from the previous user is showed in the browser...the exception is SocketException: Connection Reset by Peer.
As I could see in the error log for the web server, the server flushes the page to the client browser, but the browser closed the HTTP connection, then this error is returned. That's OK, but this error output that was not sent appears to be "stored" somewhere in the server, and then is sent to the next client that requests the page. I tried to clear the buffer with out.clearBuffer() in the beginning of the page, but it didn't work.
The solution would simply be to ignore this error output, i.e., to clean the output before the next user try to load the page. but I don't know how to do that.
Sorry about the long posting, I hope I was clear in my explanation. I am using Websphere Studio Testing Web Server...and this situation happens on any browser (the problem seems to be in the server).
Thanks in advance,
Tiago.

try using out.flush() in your code, use finalize ??
out.flush();
out.close();
all the best !

Recurring Page Exception - 'SocketException: Connection reset by peer'

I have implemented a popup calendar that is implemented as an include of a file in a lower directory (i.e. 'script/calendar.jsp') that uses an iframe. This calendar is only in a few of my pages, but I get the below exception in each page which implements it.
Is this happening after the page is sent? It's after the afterRenderResponse() method. Any thoughts? Thanks.
[#|2005-06-30T21:44:37.593-0500|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web
     |_ThreadID=19;|org.apache.catalina.core.StandardHostValve@1a70476: Exception Processing ErrorPage[errorCode=404, location=/faces/error.jsp]
     ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error
     at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:378)
     at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:401)
     at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:320)
     at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:302)
     at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java:512)
     at org.apache.coyote.tomcat5.CoyoteResponseFacade$1.run(CoyoteResponseFacade.java:212)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteResponseFacade.java:207)
     at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:306)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
     at java.lang.Thread.run(Thread.java:534)References: http://forum.java.sun.com/thread.jspa?messageID=3767674&#56698;

Hi,
Please go throught the following link:
http://www.websina.com/bugzero/errors/http-connection-reset.html
Hope this helps
Cheers
Giri :-)

RE: SocketException: Connection reset by peer

I am getting a same exception in WebLogic6.1 SP1.
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.ChunkOutput.flush(ChunkOutput.java:241)
     at weblogic.servlet.internal.ChunkOutput.checkForFlush(ChunkOutput.java:306)
     at weblogic.servlet.internal.MultibyteOutput.write(ChunkOutput.java:413)
     at weblogic.servlet.internal.MultibyteOutput.print(ChunkOutput.java:389)
     at weblogic.servlet.internal.ChunkOutputWrapper.print(ChunkOutputWrapper.java:134)
     at weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:111)
Anybody has any idea?

Connection reset by peer: socket write error

Anybody can help me?
I run vdbench to test our NAS server, but it always failed with "
Slave localhost-0 aborting: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
Error:         Windows System Error code: 64: ", how to solve this fail ?
conf file:
fsd=fsd,anchor=Y:\dir,count=(11,15),depth=10,width=2,files=1,size=(10k,20,100k,20,160k,20,8m,20,10m,10,1g,5,2g,5)
fwd=fwd1,fsd=(fsd11,fsd12,fsd13,fsd14,fsd15),rdpct=85,xfersize=(10k,22,100k,22,160k,22,8m,22,10m,12),fileio=random,fileselect=random,threads=5
rd=rd1,fwd=fwd1,operations=read,fwdrate=max,format=yes,elapsed=10,interval=1
logfile.html:
14:22:49.510 Vdbench distribution: vdbench50401
14:22:49.510
14:22:49.526 input argument scanned: '-fcifs'
14:22:49.526 java.vendor                   Sun Microsystems Inc.
14:22:49.526 java.home                     C:\Program Files\Java\jre6
14:22:49.526 java.vm.specification.version 1.0
14:22:49.526 java.vm.version               16.3-b01
14:22:49.526 java.vm.vendor                Sun Microsystems Inc.
14:22:49.526 java.specification.version    1.6
14:22:49.526 java.class.version            50.0
14:22:49.526 user.name                     zcuser1002
14:22:49.526 user.dir                      C:\Users\zcuser1002\Desktop\Y-vdbench-1021
14:22:49.526 java.class.path               C:\Users\zcuser1002\Desktop\Y-vdbench-1021\;C:\Users\zcuser1002\Desktop\Y-vdbench-1021\classes;C:\Users\zcuser1002\Desktop\Y-vdbench-1021\vdbench.jar
14:22:49.526 os.name                       Windows Server 2008 R2
14:22:49.526 os.arch                       amd64
14:22:49.526 os.version                    6.1
14:22:49.526 sun.arch.data.model           64
14:22:49.557 'fsd=fsd,count=(start,count)' added fsd11 Y:\dir11
15:08:57.031       2704    0.0 0.00   0.9 4.42   0.0    0.0 0.00    0.0 0.00 0.00 0.00   0.00       0   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00
15:08:58.030       2705 343.0 386.6   8.5 4.36   0.0    0.0 0.00 343.0 386.6 0.00 42.22 42.22 129071   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00
15:08:59.031       2706   15.0 983.4   0.0 3.41   0.0    0.0 0.00   15.0 983.4 0.00 1.85   1.85 129160   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00
15:09:51.406 localhost-0: anchor=Y:\dir15: Created 420 of 1024 files (41.02%)
15:10:02.202       2707 12143 31.35   8.0 6.25   0.0    0.0 0.00 12143 31.35 0.00 1513 1513.9 130736   0.0 0.00   0.0 0.00 65.0 59795 65.0 202.8 67.0 44969   0.0 0.00   0.0 0.00   0.0 0.00
15:10:02.234       2708    0.0 0.00   8.6 8.40   0.0    0.0 0.00    0.0 0.00 0.00 0.00   0.00       0   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00
15:10:02.249       2709    0.0 0.00 43.7 37.5   0.0    0.0 0.00    0.0 0.00 0.00 0.00   0.00       0   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00 27.0 4268   0.0 0.00   0.0 0.00   0.0 0.00
15:10:02.265       2710    0.0 0.00   0.0 0.00   0.0    0.0 0.00    0.0 0.00 0.00 0.00   0.00       0   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00
15:10:02.296       2711    0.0 0.00 100.0 81.2   0.0    0.0 0.00    0.0 0.00 0.00 0.00   0.00       0   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00
15:10:02.312       2712    0.0 0.00   0.0 0.00   0.0    0.0 0.00    0.0 0.00 0.00 0.00   0.00       0   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00
15:10:02.312 localhost-0: 15:10:02.218 op: write lun: Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file lba:   1484652544 0x587E0000 xfer:   131072 errno: Windows System Error code: 64: ??¡§????????????
15:10:02.327 localhost-0: 15:10:02.234 op: write lun: Y:\dir14\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file lba:   1971847168 0x75880000 xfer:   131072 errno: Windows System Error code: 64: ??¡§????????????
15:10:02.343       2713    0.0 0.00 100.0 74.9   0.0    0.0 0.00    0.0 0.00 0.00 0.00   0.00       0   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00   0.0 0.00
15:10:02.343
15:10:02.343 **********************************************************
15:10:02.343 Slave localhost-0 aborting: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
Error:         Windows System Error code: 64: ??¡§????????????
lba:           1484652544
xfersize:      131072
blocks_done:   11327
bytes_done:    1484652544
open_for_read: false
15:10:02.343 **********************************************************
15:10:02.343
15:10:18.013 Exception from slave: localhost-0
15:10:18.013
15:10:18.013 common.failure():
java.net.SocketException: Connection reset by peer: socket write error
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source)
at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknown Source)
at java.io.ObjectOutputStream.reset(Unknown Source)
at Vdb.SlaveSocket.putMessage(SlaveSocket.java:277)
at Vdb.CollectSlaveStats.<init>(CollectSlaveStats.java:121)
at Vdb.Reporter.run(Reporter.java:183)
localhost-0.stdout.html:
stdout/stderr for slave=localhost-0
14:22:50.072 14:22:50.072 SlaveJvm execution parameter: '-m localhost'
14:22:50.072 14:22:50.072 SlaveJvm execution parameter: '-n localhost-10-141104-14.22.49.432'
14:22:50.072 14:22:50.072 SlaveJvm execution parameter: '-l localhost-0'
14:22:50.072 14:22:50.072 SlaveJvm execution parameter: '-p 5570'
14:22:50.072 14:22:50.072 SlaveJvm positional parameter: 'SlaveJvm'
14:22:50.118 14:22:50.118 successfully connected to master localhost
14:22:50.118 14:22:50.118 Connection to localhost using port 5570 successful
14:22:50.571 14:22:50.571 execute(): ls -l Y:\dir11
14:22:50.618 14:22:50.618 execute(): ls -l Y:\dir12
14:22:50.633 14:22:50.633 execute(): ls -l Y:\dir13
14:22:50.664 14:22:50.664 execute(): ls -l Y:\dir14
14:22:50.680 14:22:50.680 execute(): ls -l Y:\dir15
14:22:50.711 14:22:50.711 Configuration interpretation took 0.45 seconds
Link to Run Definitions:         <A HREF="#_225912260">format_for_rd1 For loops: None</A>
                                 <A HREF="#_156265924">rd1 For loops: None</A>
14:22:50.852 14:22:50.852 Beginning of run setup
14:22:50.852 14:22:50.852 **********************
14:22:50.852
14:22:50.852
14:22:51.538 14:22:51.538 Completed the creation of the directory list for Y:\dir11: 2046 directories.
14:22:56.811 14:22:56.811 Memory total Java heap:   77.438 MB; Free:   32.782 MB; Used:   44.655 MB;
14:22:56.874 14:22:56.874 checkMemory()
14:22:56.874 14:22:56.874 Memory total Java heap:   77.438 MB; Free:   52.364 MB; Used:   25.074 MB;
14:23:03.426 14:23:03.426 Generated     1024 file names; total anchor size: 130.841g
14:23:03.426 14:23:03.426 Writing control file for anchor=Y:\dir11 at start of run.
14:23:03.457 14:23:03.441 Completed control file for anchor=Y:\dir11 at start of run. dirs: 2046/2046 files: 1024/88 sizes: 130.841g/8.721g/0/0.0
14:23:03.457 14:23:03.441 During anchor creation for anchor=Y:\dir11 there were 2046 directories and 88 files
14:23:03.551 14:23:03.551 Completed the creation of the directory list for Y:\dir12: 2046 directories.
14:23:08.902 14:23:08.902 Memory total Java heap:   77.438 MB; Free:   24.149 MB; Used:   53.288 MB;
14:23:08.964 14:23:08.964 checkMemory()
14:23:08.964 14:23:08.964 Memory total Java heap:   77.438 MB; Free:   50.640 MB; Used:   26.798 MB;
14:23:15.579 14:23:15.579 Generated     1024 file names; total anchor size: 130.841g
14:23:15.579 14:23:15.579 Writing control file for anchor=Y:\dir12 at start of run.
14:23:15.594 14:23:15.594 Completed control file for anchor=Y:\dir12 at start of run. dirs: 2046/2046 files: 1024/74 sizes: 130.841g/7.092g/0/0.0
14:23:15.594 14:23:15.594 During anchor creation for anchor=Y:\dir12 there were 2046 directories and 74 files
14:23:15.688 14:23:15.688 Completed the creation of the directory list for Y:\dir13: 2046 directories.
14:23:21.210 14:23:21.210 Memory total Java heap:   74.688 MB; Free:   19.725 MB; Used:   54.963 MB;
14:23:21.273 14:23:21.273 checkMemory()
14:23:21.273 14:23:21.273 Memory total Java heap:   76.562 MB; Free:   48.176 MB; Used:   28.386 MB;
14:23:28.168 14:23:28.168 Generated     1024 file names; total anchor size: 130.841g
14:23:28.168 14:23:28.168 Writing control file for anchor=Y:\dir13 at start of run.
14:23:28.184 14:23:28.184 Completed control file for anchor=Y:\dir13 at start of run. dirs: 2046/2046 files: 1024/84 sizes: 130.841g/8.886g/0/0.0
14:23:28.184 14:23:28.184 During anchor creation for anchor=Y:\dir13 there were 2046 directories and 84 files
14:23:28.262 14:23:28.262 Completed the creation of the directory list for Y:\dir14: 2046 directories.
14:23:33.785 14:23:33.785 Memory total Java heap:   74.250 MB; Free:   17.213 MB; Used:   57.037 MB;
14:23:33.863 14:23:33.863 checkMemory()
14:23:33.863 14:23:33.863 Memory total Java heap:   72.812 MB; Free:   42.829 MB; Used:   29.983 MB;
14:23:40.976 14:23:40.976 Generated     1024 file names; total anchor size: 130.841g
14:23:40.976 14:23:40.976 Writing control file for anchor=Y:\dir14 at start of run.
14:23:40.976 14:23:40.976 Completed control file for anchor=Y:\dir14 at start of run. dirs: 2046/2046 files: 1024/87 sizes: 130.841g/8.778g/0/0.0
14:23:40.976 14:23:40.976 During anchor creation for anchor=Y:\dir14 there were 2046 directories and 87 files
14:23:41.054 14:23:41.054 Completed the creation of the directory list for Y:\dir15: 2046 directories.
14:23:46.296 14:23:46.296 Memory total Java heap:   74.062 MB; Free:   42.390 MB; Used:   31.672 MB;
14:23:46.374 14:23:46.374 checkMemory()
14:23:46.374 14:23:46.374 Memory total Java heap: 101.000 MB; Free:   68.809 MB; Used:   32.191 MB;
14:23:52.958 14:23:52.958 Generated     1024 file names; total anchor size: 130.841g
14:23:52.958 14:23:52.958 Writing control file for anchor=Y:\dir15 at start of run.
14:23:52.989 14:23:52.973 Completed control file for anchor=Y:\dir15 at start of run. dirs: 2046/2046 files: 1024/96 sizes: 130.841g/8.995g/0/0.0
14:23:52.989 14:23:52.973 During anchor creation for anchor=Y:\dir15 there were 2046 directories and 96 files
14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd11,operation=read:    20.0
14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd12,operation=read:    20.0
14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd13,operation=read:    20.0
14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd14,operation=read:    20.0
14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd15,operation=read:    20.0
14:23:53.051 14:23:53.051 Started 8 threads for fwd=format,fsd=fsd11
14:23:53.114 14:23:53.114 Started 8 threads for fwd=format,fsd=fsd12
14:23:53.161 14:23:53.161 Started 8 threads for fwd=format,fsd=fsd13
14:23:53.207 14:23:53.207 Started 8 threads for fwd=format,fsd=fsd14
14:23:53.270 14:23:53.270 Started 8 threads for fwd=format,fsd=fsd15
14:23:53.270 14:23:53.270 Started 40 FwgThreads
14:23:53.270 14:23:53.270 Waiting for task synchronization
14:23:53.270 14:23:53.270 task_wait_start_complete() end
<a name="_225912260"></a><i><b>14:23:53.971 Starting RD=format_for_rd1</b></i>
14:23:54.002 14:23:54.002 task_run_all(): 41 tasks
14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir15 mkdir complete.
14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir11 mkdir complete.
14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir13 mkdir complete.
14:23:54.066 14:23:54.066 Message to master: anchor=Y:\dir14 mkdir complete.
14:23:54.066 14:23:54.066 Message to master: anchor=Y:\dir12 mkdir complete.
14:24:24.685 14:24:24.685 Message to master: anchor=Y:\dir14: Created 130 of 1024 files (12.70%)
14:24:56.311 14:24:56.311 Message to master: anchor=Y:\dir12: Created 130 of 1024 files (12.70%)
14:25:40.473 14:25:40.464 Message to master: anchor=Y:\dir13: Created 140 of 1024 files (13.67%)
14:32:52.125 14:32:52.125 Message to master: anchor=Y:\dir12: Created 140 of 1024 files (13.67%)
14:33:30.374 14:33:30.374 Message to master: anchor=Y:\dir12: Created 160 of 1024 files (15.63%)
14:34:33.842 14:34:33.842 Message to master: anchor=Y:\dir14: Created 170 of 1024 files (16.60%)
14:35:49.810 14:35:49.810 Message to master: anchor=Y:\dir14: Created 180 of 1024 files (17.58%)
14:36:34.451 14:36:34.451 Message to master: anchor=Y:\dir14: Created 190 of 1024 files (18.55%)
14:38:13.437 14:38:13.437 Message to master: anchor=Y:\dir14: Created 200 of 1024 files (19.53%)
14:39:01.966 14:39:01.966 Message to master: anchor=Y:\dir11: Created 210 of 1024 files (20.51%)
14:39:57.837 14:39:57.837 Message to master: anchor=Y:\dir15: Created 220 of 1024 files (21.48%)
14:41:51.763 14:41:51.763 Message to master: anchor=Y:\dir13: Created 220 of 1024 files (21.48%)
14:42:31.156 14:42:31.156 Message to master: anchor=Y:\dir14: Created 240 of 1024 files (23.44%)
14:45:32.607 14:45:32.607 Message to master: anchor=Y:\dir15: Created 260 of 1024 files (25.39%)
14:46:44.611 14:46:44.611 Message to master: anchor=Y:\dir11: Created 270 of 1024 files (26.37%)
14:47:53.707 14:47:53.707 Message to master: anchor=Y:\dir14: Created 280 of 1024 files (27.34%)
14:48:25.032 14:48:25.032 Message to master: anchor=Y:\dir12: Created 280 of 1024 files (27.34%)
14:48:56.946 14:48:56.946 Message to master: anchor=Y:\dir13: Created 290 of 1024 files (28.32%)
14:50:40.869 14:50:40.868 Message to master: anchor=Y:\dir11: Created 300 of 1024 files (29.30%)
14:51:22.062 14:51:22.062 Message to master: anchor=Y:\dir15: Created 330 of 1024 files (32.23%)
14:53:55.390 14:53:55.390 Message to master: anchor=Y:\dir14: Created 350 of 1024 files (34.18%)
14:56:20.897 14:56:20.897 Message to master: anchor=Y:\dir14: Created 360 of 1024 files (35.16%)
14:58:08.513 14:58:08.513 Message to master: anchor=Y:\dir11: Created 360 of 1024 files (35.16%)
14:59:34.933 14:59:34.933 Message to master: anchor=Y:\dir12: Created 360 of 1024 files (35.16%)
15:02:15.234 15:02:15.234 Message to master: anchor=Y:\dir13: Created 370 of 1024 files (36.13%)
15:02:48.482 15:02:48.482 Message to master: anchor=Y:\dir14: Created 380 of 1024 files (37.11%)
15:04:27.359 15:04:27.359 Message to master: anchor=Y:\dir13: Created 380 of 1024 files (37.11%)
15:05:57.406 15:05:57.406 Message to master: anchor=Y:\dir15: Created 390 of 1024 files (38.09%)
15:07:18.982 15:07:18.982 Message to master: anchor=Y:\dir11: Created 390 of 1024 files (38.09%)
15:08:15.419 15:08:15.419 Message to master: anchor=Y:\dir11: Created 410 of 1024 files (40.04%)
15:08:50.624 15:08:50.624 Message to master: anchor=Y:\dir13: Created 410 of 1024 files (40.04%)
15:09:51.406 15:09:51.406 Message to master: anchor=Y:\dir15: Created 420 of 1024 files (41.02%)
15:10:02.202 15:10:02.202 file_write error2: 64
15:10:02.202 15:10:02.202 file_write error2: 64
15:10:02.202 15:10:02.202 handle: 0000000000000B38
15:10:02.202 15:10:02.202 seek:   0000000075880000
15:10:02.202 15:10:02.202 handle: 0000000000000BC0
15:10:02.202 15:10:02.202 length: 0000000000020000
15:10:02.202 15:10:02.202 seek:   00000000587E0000
15:10:02.202 15:10:02.202 buffer: 0000000034430000
15:10:02.202 15:10:02.202 length: 0000000000020000
15:10:02.202 15:10:02.202 buffer: 000000002E3E0000
15:10:02.234 15:10:02.234
15:10:02.234 15:10:02.234 Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
15:10:02.234 15:10:02.234 Error:         Windows System Error code: 64: ??¡§????????????
15:10:02.234 15:10:02.234 lba:           1484652544
15:10:02.234 15:10:02.234 xfersize:      131072
15:10:02.234 15:10:02.234 blocks_done:   11327
15:10:02.234 15:10:02.234 bytes_done:    1484652544
15:10:02.234 15:10:02.234 open_for_read: false
15:10:02.234 15:10:02.234
15:10:02.234 java.lang.RuntimeException: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
15:10:02.234 Error:         Windows System Error code: 64: ??¡§????????????
15:10:02.234 lba:           1484652544
15:10:02.234 xfersize:      131072
15:10:02.234 blocks_done:   11327
15:10:02.234 bytes_done:    1484652544
15:10:02.234 open_for_read: false
15:10:02.234 at Vdb.common.failure(common.java:308)
15:10:02.234 at Vdb.ActiveFile.writeError(ActiveFile.java:611)
15:10:02.234 at Vdb.ActiveFile.writeBlock(ActiveFile.java:458)
15:10:02.234 at Vdb.FwgThread.doSequentialWrite(FwgThread.java:327)
15:10:02.234 at Vdb.OpCreate.doOperation(OpCreate.java:51)
15:10:02.234 at Vdb.OpFormat.doOperation(OpFormat.java:91)
15:10:02.234 at Vdb.FwgThread.run(FwgThread.java:157)

'Socket write error' is merely the master finding out that the slave aborted unexpectedly.
It it the '64' you have to worry about.
Windows system error code 64:
(It appears that the Vdbench translation from number to text may have some language issues and therefore can not properly print it).
ERROR_NETNAME_DELETED
64 (0x40)
The specified network name is no longer available.

Socket read error: connection reset by peer

Hi.
Has anybody experienced the error message �Socket read error: connection reset by peer�
Please see below for detailed information.
Appreciate your help
Regards
RT
Enviroment specification
Server: HP/UX 11.00 64-bit, Oracle RDBMS 8.1.6.0.0 64-bit
2 firewalls between client and db.
Client:
Win 2000,
SP3,
Oracle Client 8.1.7.0.0 ,JDBC OCI (thin JDBC driver,class12.zip)
JDK 1.3
JRUN3.0
The TCP protocol is being used in the communication
Error messages
Web Users receive: Socket read error: connection reset by peer
Trace files on the sever: Read unexpected EOF ERROR on 18.
Explanation: The error in the server sqlnet trace file, suggests that a client connection has terminated abnormally, i.e. client machine powered off, a cable removed or a network connection aborted without warning. No user has complained of such a problem and there is no client trace with an error.
The problem
The users of the java web application, experiencing an exception almost once or twice a day.
The JRUN web-server reports broken connections to the db and client are receiving "connection reset by peer".
At the moment when the errors occurs the users just have to wait a while(2-10 min) and then they can use the web application again.(no action is taken)
This problem can not be reproduced. The problem happens only occasionally when the network is under heavy load and new DB connection is being created.
The application
The java web-application uses a customized connection pooling against the database. This pool is shared among all the users of the website. whenever a user process needs to fetch data from the database, a free connection from this pool is allocated. The application is testing if the connection is valid before making a transaction (select '1' from dual). When the error occurs a ORA-3113 end-of-file on communication channel is returned to the application.
The path between the client and db involves at least two firewalls. The firewalls are opened for sql*net traffic. The network group can tell that enquiries from the app.server is not getting feedback from the db. They have not however, identified if the enquiries are reaching the db-srever, or if they are stopped earlier in the network.
Around 1000 users, are using other applications which uses dedicated sqlnet connections against the db and they have not experienced any problems.
Issues considered
Connection pooling
It is a customized connection pooling, developed by Lindorff developers.
I have read through the source code for the connection pooling and it does the job as it should, and in case of bad connection, it tries to create a new connection.
The log file shows that the call to the method DriverManager.getConnection() hangs until the server goes down, which is probably because of the fact that the method DriverManager.setLoginTimeout(), does not take effect and timeout value is Zero. ( According to oracle , Oracle JDBC does not support login timeouts and calling the static DriverManager.setLoginTimeout() method will have no effect).
Firewall
One thing to consider is when the firewall may decide to shut down the socket due to long inactivity of a connection. This will cause problems to JDBC Connection Pool because the pool is not aware of this disconnection at the TCP/IP level; until someone checks out the connection from the pool and tries to use it. The user will get a Socket read error: connection reset by peer.
Jrun timeout paramter is less than the firewall�s timeout so the firewall will not close a connection before Jrun does.
Number of processes the DB can handle
Processes parameter is 1300, , they have not experienced the Oracle error msg �max # of processes reached�.
Port redirection through a firewall:
Since the firewall has a sql net proxy Port redirection through a firewall is not a problem. Problems with port redirection only appear at connect time, but in this situation the connections fail long after the connection is established.
The network group
The network people who investigaged the problem at Lindorff report that there are a significant amount of "dropped packages" between the database server and the jdbc client (web-application) 24 hrs. The reason for this is "unknown established TCP packet" which means that the firewall does not consider these packages to be part of an already established session. The network group believes this happen because one of the hosts send a RESET or FIN signal which the firewall have noticed but are not received by the other host.
It seems like the firewall are dropping packages bacause of "Unknown
established TCP packet" from both the JDBC client and the TNSLISTENER on the database server. The dropped packages are SQL*Net v2 traffic so clearly Oracle products are involved

Presumably something is working.
Thus the problem is not with your code. At least not the database part that you have control over.
That error occurs when the other side closes the socket. Presumably you are catching lost connection exceptions and trying to restore it.

XI 2.0 Inbound file adapter : Connection reset by peer

I am using XI 2.0 and have an inbound file adapter. It polls every 5 minutes. But at least 1 or twice a day the file adapter stops with the following error message.
"java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read" occurred \par
There have been times when this runs for days or weeks without any problems.
Has anyone else seen this issue and how do your correct it?
Currently I have to go into the file adpaters and restart them manually. It would be nice if there was some way to automate this function. Any ideas?
Regards,
Jim

With JDK 5.0 use ojdbc5.jar instead of ojdbc14.jar.

JDBC Connection reset by peer: JVM_recv in socket input stream read

Hey Guys,
Has anyone seen this issue? We get this error in our Weblogic app logs at times and no one is able to login to our application. Our database server and SQL server seem fine at a high level. Any ideas what is causing this?
com.s1.arch.persistence.exception.PersistenceException weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the server, java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
Thanks

please make sure that there is no Firewall between your servers and DB server. this message usually happen when there is a fire wall between the servers. if yes please make sure that the connection time on fire wall is longer than the time needed to complete an operation another thing that you need to check if you have a fire wall which is to make sure that Oracle DBMS return the request to the same port that it is listening to (1521 default).

Connection reset by peer.

I recently started getting following exception. I use Windows 2000
          with weblogic 5.1 service pack 12. This problem does not effect the
          functionality, and happens randomly.
          Thank you,
          berker(at)optonline.net
          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.writeChunks(ChunkUtils.java:88)
               at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:336)
               at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:603)
               at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:101)
               at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:430)
               at weblogic.servlet.FileServlet.sendFile(FileServlet.java:199)
               at weblogic.servlet.FileServlet.service(FileServlet.java:56)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
               at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
               at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
               at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


Looks like the browser user is closing the browser or moving on to a new url before the response comes back.
          Search the newsgroup, as there are a number of posts concerning this.
          Bill
          berker wrote:
          > I recently started getting following exception. I use Windows 2000
          > with weblogic 5.1 service pack 12. This problem does not effect the
          > functionality, and happens randomly.
          >
          > Thank you,
          > berker(at)optonline.net
          >
          > 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.writeChunks(ChunkUtils.java:88)
          > at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:336)
          > at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:603)
          > at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:101)
          > at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:430)
          > at weblogic.servlet.FileServlet.sendFile(FileServlet.java:199)
          > at weblogic.servlet.FileServlet.service(FileServlet.java:56)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
          > at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
          > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
          > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Connection reset by peer problem

I have the following code, and every time I run it i get a "java.net.SocketException: Connection reset by peer: socket write error" exception. Why is that? This is the first time I'm writing a network client application, so please help :)
Socket s = new Socket("127.0.0.1",8080);
OutputStream out = new BufferedOutputStream(s.getOutputStream());
InputStream in = new BufferedInputStream(s.getInputStream());
out.write("server status\r\n".getBytes());
//out.flush();
StringBuffer responseLine = new StringBuffer();
int c;
while(in.available() > 0) {
c = in.read();
responseLine.append((char)c);
//out.close();
//in.close();
//s.close();
System.out.println(responseLine.toString());P.S. It's the same problem with or wothout the out.flush(), and with or wothout closing my streams and socket.

InputStream = new BufferedReader
Um..just look at that code, oh boy.
InputStream is a class and so is
BufferedReader
Two different classes (event if they are subclasses)
cant be directly assigned to each other.The human eye sometimes sees what it wants to see and not what it is... :-)
I think the problem is with the protocol and the timing. The while loop may never execute due to timing:
1. Client's "server status" request takes a few ms to arrive in the server.
2. In the meanwhile, in.available is zero and the client does not enter the loop and does not append any characters to the string buffer.
3. Server writes its status on the socket which arrives at the client which is no longer reading it a few ms later.
Which brings us to the protocol:
If the server status is a fixed length block of data, try reading it into a single byte buffer.
If it is variable length or text, use a BufferedReader on the socket, read the response a line at a time and make the server end the report with a token (like a last line of "END_OF_SERVER_STATUS_REPORT" or "01234567890123456789012345678901234567890123456789", whatever).
Don't check if data is available on a socket if you know it should be, sooner or later, and you don't want to multiplex your flow on data availability.

Com.evermind.server.http.HttpIOException: Connection aborted by peer: socke

Hi
I get an this stack on the server side while doing a forward using RequestDispatcher.
com.evermind.server.http.HttpIOException: Connection aborted by peer: socket write error
at com.evermind.server.http.EvermindServletOutputStream.flushBuffer(EvermindServletOutputStream.java:81)
at com.evermind.server.http.EvermindHttpServletResponse.flushBuffer(EvermindHttpServletResponse.java:1818)
at javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:52)
The funniest part is, i get this exception while i submit the request second time i get this error.. First time it works fine. :)
ANy solution on this would be greatly appreciated.
Thanks
Manju

Hi!
I posted a TAR on metalink for this "read timed out" problem. This is the answer I got:
apparently the messages that you listed seem refer to a problem in reading request data from the client - so the HttpIOException is triggered.
I have made a little research on HttpIOException in request-reading context. There are only
two situations in which HttpIOException can be raised without an causing IOExce
ption, and I think none of them applies. So we'd have some kind of IOException t
hat causes the HttpIOException. It might well be a SocketException, because the
text "Read timed out" is as far as I know the standard text for SocketException
if the socket's SoTimeout has been reached.
In fact there is a configuration parameter for OC4J (though undocumented), which allows you to set the Socket's SoT
imeout -- and the default is 15000 (measured in milliseconds). The name is "orac
le.j2ee.http.socket.timeout", and it should be available in OC4J 9.0.3.1 and hig
her (I am definitely sure that it exists in OC4J 9.0.4.1).
So can you please add something like "-Doracle.j2ee.http.socket.timeout=120000" to the startup comma
nd for your standalone OC4J container to increase the timeout from 15 seconds to
2 minutes?
It helped us, although some requests time out "normally" instead.
/jonas

SocketException: Connection aborted/reset by peer

Similar Messages

Maybe you are looking for