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?

Similar Messages

  • 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�

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

  • SocketException - Connection reset by peer

    Hi,
    I'm running a j2ee app on WAS5.0. I get this abrupt exception for no reason. It comes just while the jsp is loading or just moving the mouse around on the page.
    Kindly let me know what the problem could be.
    regards,
    Arif

    Thrown to indicate that there is an error in the underlying protocol, such as a TCP error.
    there is much information about this exceptio...
    Read this article
    Network Programming with J2SE 1.4
    http://java.sun.com/features/2002/08/j2se-network.html
    Other forums with same problem:
    http://forum.java.sun.com/thread.jsp?forum=46&thread=294609&tstart=0&trange=15
    http://forum.java.sun.com/thread.jsp?thread=294609&forum=46&message=1797877

  • 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.

  • Re: Connection reset by peer: Connection reset by peer

              >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.
              Sorry but 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, but every
              attributes set on the request are lost !!
              At first I thought it was related with the NT Muxer, or the NT Performance Pack,
              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)
              

              Yann,
              This is not a J2EE Connector problem. From the stack trace it looks like you might
              have better luck posting this to the Servlet newsgroup.
              Also, just so that you are aware, this newsgroup is not monitored regularly so
              if your issue/question is not getting answered in a timely manner, please send
              a request to BEA Support.
              >
              >>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.
              >
              >--
              >
              >Sorry but 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, but
              >every
              >attributes set on the request are lost !!
              >At first I thought it was related with the NT Muxer, or the NT Performance
              >Pack,
              >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)
              >
              >
              

  • JspException: Input/output errror: SocketException: Connection reset by pee

    In weblogic 8.1, getting below exception often,
              javax.servlet.jsp.JspException: Input/output errror: java.net.SocketException: Connection reset by peer.
              at org.apache.struts.util.ResponseUtils.write method
              Although no problem, but it seems to slow down.
              Technology used is mix of jsp, servlets & struts framework
              Any comments will be highly appreciated

    I also experience this. I have wenlogic 8.1sp6.
              It was affecting one part of my application in that no data is being returned. I had to stop and restart the server to get connection going again. I notice no one with weblogic 9 has the problem. I may upgrade to version 9 soon if that will help to solve this problem.

  • Connection reset by peer issue

    Hello,
    Our application is occasionally getting messages like :
    weblogic java.net.SocketException: Connection reset by peer: JVM_recv
    in socket input stream read
    although it eventually recovers (we have the jdbc refreshTestMinutes
    set to 5). We are using Weblogic 5.1 Service Pack 12 and Jdk1.3.1_04
    connecting to SQL Server 2000 on another machine.
    After scratching our heads with what might be wrong with our
    application, we think it might be a network issue. Theres nothing in
    the SQL Server logs to indicate that there has been a problem on that
    side.
    Has anyone had this problem and resolved it, and if so how? Are we on
    the right track?
    Thanks,
    Caroline Sturtridge

    Thanks for those suggestions, we'll try them and see if they work.
    Strangely, I wrote a small program to keep a socket open between the
    two machines (completely separate from the main application) and we've
    not had a problem since...
    Z
    "Slava Imeshev" <[email protected]> wrote in message news:<[email protected]>...
    Hi Zeetha,
    "zeetha" <[email protected]> wrote in message
    news:[email protected]..
    Hello,
    Our application is occasionally getting messages like :
    weblogic java.net.SocketException: Connection reset by peer: JVM_recv
    in socket input stream read
    although it eventually recovers (we have the jdbc refreshTestMinutes
    set to 5). We are using Weblogic 5.1 Service Pack 12 and Jdk1.3.1_04
    connecting to SQL Server 2000 on another machine.
    After scratching our heads with what might be wrong with our
    application, we think it might be a network issue. Theres nothing in
    the SQL Server logs to indicate that there has been a problem on that
    side.
    Has anyone had this problem and resolved it, and if so how? Are we on
    the right track?It's definitely a network issue. I faced this kind of problem before.
    o You need to use test connections on reserve to true.
    o You need to talk to your network admin and find out
    if there are any firewalls/proxies between the app server
    and the database. They can be dropping connections
    after a period of incativity.
    o Ask the network admin to check error counters on the switch
    ports. Sometimes when the switch port is set to 100Mbit/Firm
    and other side use 100MBit/Auto, the parites can't negotiate
    speed and fall down to speed of 10th of kilobytes, having
    multiple errors etc. Cisco switches like doing this.
    Hope this helps.
    Regards,
    Slava Imeshev

  • 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.

  • Connection reset by peer when I specify port for Callback

    I have a successful rmi callback when it uses annoymous port by using UnicastRemoteObject.exportObject(this) from client. But I get the following messages when I tried to specify port by using UnicastRemoteObject.exportObject(this, port) by client. My understanding is this tells the server to callback using the port specify and the connection should be made. Where it fails is when the server tries to call client.notify() where the callback is taking place I get the errors.
    Am I missing something? I thought that was all I needed to do to specify a port.
    Remote Exception:java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
    java.rmi.MarshalException: Error marshaling transport header; nested exception is:
    java.net.SocketException: Connection reset by peer: Connection reset by peer
    java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
    java.rmi.MarshalException: Error marshaling transport header; nested exception is:
    java.net.SocketException: Connection reset by peer: Connection reset by peer
    at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
    Thanks for the help.

    Hi Esmond, My name is Lee and I work with Joon (hellscream) and this RMI callback problem still persists. We appreciate your help and we know about your expertise in this area. (Great products on your web site by the way).
    The problem environment currently consists of a Unix Solaris server on the backend and windows XP laptops acting as clients. The callback is from the unix server back to the client.
    By looking at the output of netstat -na on the unix server during a normal anonymous port run, we can clearly see that there seem to be 3 sequentially numbered ports involved whenever the anonymous port construct of UnicastRemoteObject is used. This happens with super() or super(0); in our client code. All works very well that way.
    The problem arises when we make changes to the client impl file and specify a port with super(65000) for example.
    There is no firwall involved right now and UnicastRemoteObject doesn't seem to behave as advertised in the sense that
    We can clearly see what's going on with the network using Thread.sleep(10000) within the client app meanwhile executing netstat -na on the unix server and grepping for the client IP address
    We can see that the unix server STILL wants to talk to the client on an arbitrary port while the laptop client is listening on the desired port that we chose (65000) in this case.
    If we attempt to instantiate a port in the server Impl java file, the results are the same with the exception of the choice of the source port on the unix server. We seem to be able to choose and set that at will. Unfortunately, and from the perspective of a future firewall, the source port is irrelevant and the rules normally apply to destination ports in an outgoing connection.
    Anyway, with ports instantiated and everything compiling, the client prints the following stacktrace
    Thanks very much in advance for your help
    Remote Exception:java.rmi.ServerException: RemoteException occurred in server th
    read; nested exception is:
    java.rmi.ConnectIOException: error during JRMP connection establishment;
    nested exception is:
    java.net.SocketException: Connection reset
    java.rmi.ServerException: RemoteException occurred in server thread; nested exce
    ption is:
    java.rmi.ConnectIOException: error during JRMP connection establishment;
    nested exception is:
    java.net.SocketException: Connection reset
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
    at sun.rmi.transport.Transport$1.run(Transport.java:148)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
    60)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
    .java:701)
    at java.lang.Thread.run(Thread.java:534)
    at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Stream
    RemoteCall.java:247)
    at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:
    223)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
    at ids.rmi.ServerJobImpl_Stub.execute(Unknown Source)
    at ids.jobExec.JobThread.run(JobRunner.java:551)
    Caused by: java.rmi.ConnectIOException: error during JRMP connection establishme
    nt; nested exception is:
    java.net.SocketException: Connection reset
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:274
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
    at ids.rmi.JobClientImpl_Stub.message(Unknown Source)
    at ids.rmi.ServerJobImpl.execute(ServerJobImpl.java:60)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
    at sun.rmi.transport.Transport$1.run(Transport.java:148)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
    60)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
    .java:701)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream.java:168)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
    at java.io.DataInputStream.readByte(DataInputStream.java:331)
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215
    ... 15 more
    Job finished. Exit status: -1

  • Connection reset by peer: Connection reset by peer

    hi
    I have been reviewing the weblogic logs on one of the apps servers. Attached
    is that log. There are numerous "connection reset by peer" errors in this log, I
    was wondering if a weblogic smart person could give some explanation for this .
    Any assistance would be appreciated.
    Thu Feb 01 11:35:42 PDT 2001:<E> <Posix Performance Pack> Failure in processSockets()
    java.net.SocketException: Connection reset by peer: Connection reset by peer
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.socketRead(Compiled Code)
         at java.net.SocketInputStream.read(Compiled Code)
         at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
         at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 11:44:33 PDT 2001:<E> <Posix Performance Pack> Failure in processSockets()
    java.net.SocketException: Connection reset by peer: Connection reset by peer
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.socketRead(Compiled Code)
         at java.net.SocketInputStream.read(Compiled Code)
         at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
         at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 11:44:33 PDT 2001:<E> <Posix Performance Pack> Failure in processSockets()
    java.net.SocketException: Connection reset by peer: Connection reset by peer
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.socketRead(Compiled Code)
         at java.net.SocketInputStream.read(Compiled Code)
         at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
         at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 13:48:04 PDT 2001:<E> <Posix Performance Pack> Failure in processSockets()
    java.net.SocketException: Connection reset by peer: Connection reset by peer
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.socketRead(Compiled Code)
         at java.net.SocketInputStream.read(Compiled Code)
         at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
         at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 14:39:21 PDT 2001:<I> <TX> Transaction TxC (30163629, xid = 969404989177_736,
    timeout = 300, txState = Rolledback, root = null rolled back because client is no
    longer alive
    Thu Feb 01 14:42:40 PDT 2001:<I> <EJB JAR deployment /usr/local/weblogic/myserver/serverclasses/SyndicationServerBeans.jar>
    Exception during commit of transaction: '969404989177_736'
    javax.transaction.RollbackException: Transaction TxC (30163629, xid = 969404989177_736,
    timeout = 300, txState = Rolledback, root = null has been rolled back.Reason: Transaction
    rolled back because client disconnected
         at java.lang.Throwable.fillInStackTrace(Native Method)
         at java.lang.Throwable.fillInStackTrace(Compiled Code)
         at java.lang.Throwable.<init>(Compiled Code)
         at java.lang.Exception.<init>(Compiled Code)
         at javax.transaction.RollbackException.<init>(Compiled Code)
         at weblogic.jts.internal.CoordinatorImpl.throwRollbackException(Compiled Code)
         at weblogic.jts.internal.CoordinatorImpl.commit(Compiled Code)
         at weblogic.jts.internal.TxContext.commit(Compiled Code)
         at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(Compiled Code)
         at weblogic.ejb.internal.BaseEJBObject.postInvoke(Compiled Code)
         at iBeam.iSyndicate.server.ContentDirectoryEJBEOImpl.getPlayList(Compiled Code)
         at iBeam.iSyndicate.server.ContentDirectoryEJBEOImpl_WLSkel.invoke(Compiled Code)
         at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(Compiled Code)
         at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(Compiled Code)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(Compiled Code)
         at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 14:42:40 PDT 2001:<E> <ConMan> Attempt to sendMsg using a closed connection
    Thu Feb 01 14:42:40 PDT 2001:<E> <RJVM> Exception on send : weblogic.rmi.ConnectException:
    Attempt to sendMsg using a closed connection
    Thu Feb 01 14:48:10 PDT 2001:<I> <EJB JAR deployment /usr/local/weblogic/myserver/serverclasses/SyndicationServerBeans.jar>
    Transaction: '969404989177_739' rolled back due to EJB exception:
    java.lang.NullPointerException
         at java.lang.String.indexOf(Compiled Code)
         at java.lang.String.indexOf(Compiled Code)
         at iBeam.iSyndicate.server.UserAccountListEJB.findByReferalURL(Compiled Code)
         at iBeam.iSyndicate.server.UserAccountListEJBEOImpl.findByReferalURL(Compiled Code)
         at iBeam.iSyndicate.server.UserAccountListEJBEOImpl_ServiceStub.findByReferalURL(Compiled
    Code)
         at iBeam.iSyndicate.server.SyndicateLinkSessionEJB.getSyndicated(Compiled Code)
         at iBeam.iSyndicate.server.SyndicateLinkSessionEJBEOImpl.getSyndicated(Compiled
    Code)
         at iBeam.iSyndicate.server.SyndicateLinkSessionEJBEOImpl_ServiceStub.getSyndicated(Compiled
    Code)
         at iBeam.iSyndicate.iSynLink.iSyndicateLink.service(Compiled Code)
         at javax.servlet.http.HttpServlet.service(Compiled Code)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
         at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
         at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
         at weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled Code)
         at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
         at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
         at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 14:56:23 PDT 2001:<W> <ListenThread> Connection rejected: 'Login timed
    out after: '5000' ms on socket: 'Socket[addr=208.185.136.127/208.185.136.127,port=3483,localport=7001]''
    Thu Feb 01 14:56:23 PDT 2001:<W> <ListenThread> Connection rejected: 'Login timed
    out after: '5000' ms on socket: 'Socket[addr=208.185.136.127/208.185.136.127,port=3484,localport=7001]''
    Thu Feb 01 14:56:33 PDT 2001:<W> <ListenThread> Connection rejected: 'Login timed
    out after: '5000' ms on socket: 'Socket[addr=208.185.136.127/208.185.136.127,port=3485,localport=7001]''
    Thu Feb 01 14:56:33 PDT 2001:<W> <ListenThread> Connection rejected: 'Login timed
    out after: '5000' ms on socket: 'Socket[addr=208.185.136.127/208.185.136.127,port=3486,localport=7001]''
    Thu Feb 01 14:57:34 PDT 2001:<E> <Posix Performance Pack> Failure in processSockets()
    java.net.SocketException: Connection reset by peer: Connection reset by peer
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.socketRead(Compiled Code)
         at java.net.SocketInputStream.read(Compiled Code)
         at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
         at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Fri Sep 22 12:11:40 PDT 2001:<I> <TX> Transaction TxC (22541288, xid = 969404989177_1317,
    timeout = 300, txState = Rolledback, root = null rolled back because client is no
    longer alive
    Fri Sep 22 12:11:58 PDT 2001:<W> <ListenThread> Connection rejected: 'Login timed
    out after: '5000' ms on socket: 'Socket[addr=208.185.136.93/208.185.136.93,port=4922,localport=7001]''
    Fri Sep 22 12:11:59 PDT 2001:<W> <ListenThread> Connection rejected: 'Login timed
    out after: '5000' ms on socket: 'Socket[addr=208.185.136.93/208.185.136.93,port=4923,localport=7001]''
    Fri Sep 22 12:12:16 PDT 2001:<W> <ListenThread> Connection rejected: 'Login timed
    out after: '5000' ms on socket: 'Socket[addr=208.185.136.93/208.185.136.93,port=4924,localport=7001]''
    Fri Sep 22 12:12:17 PDT 2001:<W> <ListenThread> Connection rejected: 'Login timed
    out after: '5000' ms on socket: 'Socket[addr=208.185.136.93/208.185.136.93,port=4925,localport=7001]''
    Fri Sep 22 12:15:03 PDT 2001:<I> <EJB JAR deployment /usr/local/weblogic/myserver/serverclasses/SyndicationServerBeans.jar>
    Exception during commit of transaction: '969404989177_1317'
    javax.transaction.RollbackException: Transaction TxC (22541288, xid = 969404989177_1317,
    timeout = 300, txState = Rolledback, root = null has been rolled back.Reason: Transaction
    rolled back because client disconnected
         at java.lang.Throwable.fillInStackTrace(Native Method)
         at java.lang.Throwable.fillInStackTrace(Compiled Code)
         at java.lang.Throwable.<init>(Compiled Code)
         at java.lang.Exception.<init>(Compiled Code)
         at javax.transaction.RollbackException.<init>(Compiled Code)
         at weblogic.jts.internal.CoordinatorImpl.throwRollbackException(Compiled Code)
         at weblogic.jts.internal.CoordinatorImpl.commit(Compiled Code)
         at weblogic.jts.internal.TxContext.commit(Compiled Code)
         at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(Compiled Code)
         at weblogic.ejb.internal.BaseEJBObject.postInvoke(Compiled Code)
         at iBeam.iSyndicate.server.ContentDirectoryEJBEOImpl.getDirectoryList(Compiled Code)
         at iBeam.iSyndicate.server.ContentDirectoryEJBEOImpl_WLSkel.invoke(Compiled Code)
         at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(Compiled Code)
         at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(Compiled Code)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(Compiled Code)
         at weblogic.kernel.ExecuteThread.run(Compiled Code)
    .. Krishna

    This is innocuous. You can ignore it.
    Thanks,
    Michael
    Michael Girdley
    BEA Systems
    Learning WebLogic? http://learnweblogic.com
    "krishna" <[email protected]> wrote in message
    news:[email protected]...
    >
    hi
    I have been reviewing the weblogic logs on one of the apps servers.Attached
    is that log. There are numerous "connection reset by peer" errors in thislog, I
    was wondering if a weblogic smart person could give some explanation forthis .
    Any assistance would be appreciated.
    Thu Feb 01 11:35:42 PDT 2001:<E> <Posix Performance Pack> Failure inprocessSockets()
    java.net.SocketException: Connection reset by peer: Connection reset bypeer
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.socketRead(Compiled Code)
    at java.net.SocketInputStream.read(Compiled Code)
    at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
    atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 11:44:33 PDT 2001:<E> <Posix Performance Pack> Failure inprocessSockets()
    java.net.SocketException: Connection reset by peer: Connection reset bypeer
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.socketRead(Compiled Code)
    at java.net.SocketInputStream.read(Compiled Code)
    at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
    atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 11:44:33 PDT 2001:<E> <Posix Performance Pack> Failure inprocessSockets()
    java.net.SocketException: Connection reset by peer: Connection reset bypeer
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.socketRead(Compiled Code)
    at java.net.SocketInputStream.read(Compiled Code)
    at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
    atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 13:48:04 PDT 2001:<E> <Posix Performance Pack> Failure inprocessSockets()
    java.net.SocketException: Connection reset by peer: Connection reset bypeer
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.socketRead(Compiled Code)
    at java.net.SocketInputStream.read(Compiled Code)
    at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
    atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 14:39:21 PDT 2001:<I> <TX> Transaction TxC (30163629, xid =969404989177_736,
    timeout = 300, txState = Rolledback, root = null rolled back becauseclient is no
    longer alive
    Thu Feb 01 14:42:40 PDT 2001:<I> <EJB JAR deployment/usr/local/weblogic/myserver/serverclasses/SyndicationServerBeans.jar>
    Exception during commit of transaction: '969404989177_736'
    javax.transaction.RollbackException: Transaction TxC (30163629, xid =969404989177_736,
    timeout = 300, txState = Rolledback, root = null has been rolledback.Reason: Transaction
    rolled back because client disconnected
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at javax.transaction.RollbackException.<init>(Compiled Code)
    at weblogic.jts.internal.CoordinatorImpl.throwRollbackException(CompiledCode)
    at weblogic.jts.internal.CoordinatorImpl.commit(Compiled Code)
    at weblogic.jts.internal.TxContext.commit(Compiled Code)
    at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(Compiled Code)
    at weblogic.ejb.internal.BaseEJBObject.postInvoke(Compiled Code)
    at iBeam.iSyndicate.server.ContentDirectoryEJBEOImpl.getPlayList(CompiledCode)
    atiBeam.iSyndicate.server.ContentDirectoryEJBEOImpl_WLSkel.invoke(Compiled
    Code)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(Compiled Code)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(CompiledCode)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(Compiled Code)
    at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 14:42:40 PDT 2001:<E> <ConMan> Attempt to sendMsg using aclosed connection
    Thu Feb 01 14:42:40 PDT 2001:<E> <RJVM> Exception on send :weblogic.rmi.ConnectException:
    Attempt to sendMsg using a closed connection
    Thu Feb 01 14:48:10 PDT 2001:<I> <EJB JAR deployment/usr/local/weblogic/myserver/serverclasses/SyndicationServerBeans.jar>
    Transaction: '969404989177_739' rolled back due to EJB exception:
    java.lang.NullPointerException
    at java.lang.String.indexOf(Compiled Code)
    at java.lang.String.indexOf(Compiled Code)
    at iBeam.iSyndicate.server.UserAccountListEJB.findByReferalURL(CompiledCode)
    atiBeam.iSyndicate.server.UserAccountListEJBEOImpl.findByReferalURL(Compiled
    Code)
    atiBeam.iSyndicate.server.UserAccountListEJBEOImpl_ServiceStub.findByReferalUR
    L(Compiled
    Code)
    at iBeam.iSyndicate.server.SyndicateLinkSessionEJB.getSyndicated(CompiledCode)
    atiBeam.iSyndicate.server.SyndicateLinkSessionEJBEOImpl.getSyndicated(Compiled
    Code)
    atiBeam.iSyndicate.server.SyndicateLinkSessionEJBEOImpl_ServiceStub.getSyndica
    ted(Compiled
    Code)
    at iBeam.iSyndicate.iSynLink.iSyndicateLink.service(Compiled Code)
    at javax.servlet.http.HttpServlet.service(Compiled Code)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(CompiledCode)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(CompiledCode)
    at weblogic.servlet.internal.ServletContextManager.invokeServlet(CompiledCode)
    at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
    at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Thu Feb 01 14:56:23 PDT 2001:<W> <ListenThread> Connection rejected:'Login timed
    out after: '5000' ms on socket:'Socket[addr=208.185.136.127/208.185.136.127,port=3483,localport=7001]''
    Thu Feb 01 14:56:23 PDT 2001:<W> <ListenThread> Connection rejected:'Login timed
    out after: '5000' ms on socket:'Socket[addr=208.185.136.127/208.185.136.127,port=3484,localport=7001]''
    Thu Feb 01 14:56:33 PDT 2001:<W> <ListenThread> Connection rejected:'Login timed
    out after: '5000' ms on socket:'Socket[addr=208.185.136.127/208.185.136.127,port=3485,localport=7001]''
    Thu Feb 01 14:56:33 PDT 2001:<W> <ListenThread> Connection rejected:'Login timed
    out after: '5000' ms on socket:'Socket[addr=208.185.136.127/208.185.136.127,port=3486,localport=7001]''
    Thu Feb 01 14:57:34 PDT 2001:<E> <Posix Performance Pack> Failure inprocessSockets()
    java.net.SocketException: Connection reset by peer: Connection reset bypeer
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.socketRead(Compiled Code)
    at java.net.SocketInputStream.read(Compiled Code)
    at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
    atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(Compiled Code)
    Fri Sep 22 12:11:40 PDT 2001:<I> <TX> Transaction TxC (22541288, xid =969404989177_1317,
    timeout = 300, txState = Rolledback, root = null rolled back becauseclient is no
    longer alive
    Fri Sep 22 12:11:58 PDT 2001:<W> <ListenThread> Connection rejected:'Login timed
    out after: '5000' ms on socket:'Socket[addr=208.185.136.93/208.185.136.93,port=4922,localport=7001]''
    Fri Sep 22 12:11:59 PDT 2001:<W> <ListenThread> Connection rejected:'Login timed
    out after: '5000' ms on socket:'Socket[addr=208.185.136.93/208.185.136.93,port=4923,localport=7001]''
    Fri Sep 22 12:12:16 PDT 2001:<W> <ListenThread> Connection rejected:'Login timed
    out after: '5000' ms on socket:'Socket[addr=208.185.136.93/208.185.136.93,port=4924,localport=7001]''
    Fri Sep 22 12:12:17 PDT 2001:<W> <ListenThread> Connection rejected:'Login timed
    out after: '5000' ms on socket:'Socket[addr=208.185.136.93/208.185.136.93,port=4925,localport=7001]''
    Fri Sep 22 12:15:03 PDT 2001:<I> <EJB JAR deployment/usr/local/weblogic/myserver/serverclasses/SyndicationServerBeans.jar>
    Exception during commit of transaction: '969404989177_1317'
    javax.transaction.RollbackException: Transaction TxC (22541288, xid =969404989177_1317,
    timeout = 300, txState = Rolledback, root = null has been rolledback.Reason: Transaction
    rolled back because client disconnected
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at javax.transaction.RollbackException.<init>(Compiled Code)
    at weblogic.jts.internal.CoordinatorImpl.throwRollbackException(CompiledCode)
    at weblogic.jts.internal.CoordinatorImpl.commit(Compiled Code)
    at weblogic.jts.internal.TxContext.commit(Compiled Code)
    at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(Compiled Code)
    at weblogic.ejb.internal.BaseEJBObject.postInvoke(Compiled Code)
    atiBeam.iSyndicate.server.ContentDirectoryEJBEOImpl.getDirectoryList(Compiled
    Code)
    atiBeam.iSyndicate.server.ContentDirectoryEJBEOImpl_WLSkel.invoke(Compiled
    Code)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(Compiled Code)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(CompiledCode)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(Compiled Code)
    at weblogic.kernel.ExecuteThread.run(Compiled Code)
    .. Krishna

Maybe you are looking for

  • Load a vhd on Windows Server 2012?

    All the engines look up the wrong thing. I have a .vhd I want to load on my windows 2012 server(Hyper-V non-gui machine loaded by support co.) so I can run it to demonstrate software contained in the vhd.  The OS of the vhd is Server 2008 r2 but that

  • How to have a custom Item Number in Sales Order Items

    Hello Experts, We are creating a sales order using IDoc, sales order gets created but, its not taking value what we are populating in Item Number field for Item. Defualtly its filling 10,20 and so on... Is there any thing that I need to maintain, so

  • I deleted my icalender, how can I get it back

    I deleted my calender, is there anyway to get it back? Terry

  • Hiding or disabling the check boxes in Tableview  for perticular row

    Hi    I created table view using ITAREATOR, as per my requirement i need to disable or hide the check box (which come by default) for perticular row.    Can any body send me the code thanks in advance B.Umashankar

  • Method redirector is broken with CMP finders

    The class MethodBaseQueryRedirector (or the framework that invokes this class) is broken. Anytime you utilize a CMP finder whose query is redirected (even the in the examples), you get an exception stating that the number or arguments declared does n