4 Replies Latest reply on Jan 18, 2002 9:31 PM by 3004

    basic problem : connection reset by peer

    3004
      Hi everybody,

      I have a problem that I do not manage to solve by myself so I ask to the
      Weblogic Guru :)

      System : win2k sp2, 4 x P3 900 Mhz, 2000 Go ram, Weblogic 5.1 sp9

      I deploy on Weblogic server 14 session stateless EJBs, each one doing a
      particular job. (5 seconds max)
      I also deploy one servlet (frontal), which only forwards the query to the
      EJBs.

      My problem comes from the servlet. When I try to increase the number of
      connections on this servlet,
      I got the following exception :

      mer. janv. 17 17:42:01 CET 2002:<E> <ServletContext-General> Servlet failed
      with Exception
      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(ServletResponseIm
      pl.java:603)
      at
      weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
      mpl.java:101)
      at com.webraska.gns.servlet.MyServlet.doPost(Unknown Source)
      at com.webraska.gns.servlet.MyServlet.doGet(Unknown Source)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
      at
      weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
      :105)
      at
      weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
      l.java:742)
      at
      weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
      l.java:686)
      at
      weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
      Manager.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)


      Weblogic is supposed to support heavy load as web server so I do not
      understand why I get these exception with only a few number of concurent
      connections.

      I try to tune some parameters on the weblogic.properties, but no parameter
      saved me :/

      Help me please !
      Best regards,
      Alexis Berger


        • 1. Re: basic problem : connection reset by peer
          3004
          How are you conducting your load tests? i.e. How do you generate the "many
          users" that are hitting the Servlet?

          Peace,

          --
          Cameron Purdy
          Tangosol, Inc.
          Clustering Weblogic? You're either using Coherence, or you should be!
          Download a Tangosol Coherence eval today at http://www.tangosol.com/



          "Alexis Berger" <alexis.berger@wanadoo.fr> wrote in message
          news:3c47075e@newsgroups.bea.com...
          Hi everybody,

          I have a problem that I do not manage to solve by myself so I ask to the
          Weblogic Guru :)

          System : win2k sp2, 4 x P3 900 Mhz, 2000 Go ram, Weblogic 5.1 sp9

          I deploy on Weblogic server 14 session stateless EJBs, each one doing a
          particular job. (5 seconds max)
          I also deploy one servlet (frontal), which only forwards the query to the
          EJBs.

          My problem comes from the servlet. When I try to increase the number of
          connections on this servlet,
          I got the following exception :

          mer. janv. 17 17:42:01 CET 2002:<E> <ServletContext-General> Servlet
          failed
          with Exception
          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(ServletResponseIm
          pl.java:603)
          at
          weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
          mpl.java:101)
          at com.webraska.gns.servlet.MyServlet.doPost(Unknown Source)
          at com.webraska.gns.servlet.MyServlet.doGet(Unknown Source)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :105)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:742)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:686)
          at
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
          Manager.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)


          Weblogic is supposed to support heavy load as web server so I do not
          understand why I get these exception with only a few number of concurent
          connections.

          I try to tune some parameters on the weblogic.properties, but no parameter
          saved me :/

          Help me please !
          Best regards,
          Alexis Berger

          • 2. Re: basic problem : connection reset by peer
            3004
            Well, I have one client which is trying to query the servlet. (for example I
            use internet explorer and do a lot of refresh).


            "Cameron Purdy" <cpurdy@tangosol.com> a écrit dans le message de news:
            3c470fdd@newsgroups.bea.com...
            How are you conducting your load tests? i.e. How do you generate the "many
            users" that are hitting the Servlet?

            Peace,

            --
            Cameron Purdy
            Tangosol, Inc.
            Clustering Weblogic? You're either using Coherence, or you should be!
            Download a Tangosol Coherence eval today at http://www.tangosol.com/



            "Alexis Berger" <alexis.berger@wanadoo.fr> wrote in message
            news:3c47075e@newsgroups.bea.com...
            Hi everybody,

            I have a problem that I do not manage to solve by myself so I ask to the
            Weblogic Guru :)

            System : win2k sp2, 4 x P3 900 Mhz, 2000 Go ram, Weblogic 5.1 sp9

            I deploy on Weblogic server 14 session stateless EJBs, each one doing a
            particular job. (5 seconds max)
            I also deploy one servlet (frontal), which only forwards the query to
            the
            EJBs.

            My problem comes from the servlet. When I try to increase the number of
            connections on this servlet,
            I got the following exception :

            mer. janv. 17 17:42:01 CET 2002:<E> <ServletContext-General> Servlet
            failed
            with Exception
            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(ServletResponseIm
            pl.java:603)
            at
            weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
            mpl.java:101)
            at com.webraska.gns.servlet.MyServlet.doPost(Unknown Source)
            at com.webraska.gns.servlet.MyServlet.doGet(Unknown Source)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
            at
            weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
            :105)
            at
            weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
            l.java:742)
            at
            weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
            l.java:686)
            at
            weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
            Manager.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)


            Weblogic is supposed to support heavy load as web server so I do not
            understand why I get these exception with only a few number of concurent
            connections.

            I try to tune some parameters on the weblogic.properties, but no
            parameter
            saved me :/

            Help me please !
            Best regards,
            Alexis Berger

            • 3. Re: basic problem : connection reset by peer
              3004
              Well, if you refresh before the last byte is received, that will close the
              socket and you will see the error that you described. Everything is working
              as it should in this case.

              You need to use a load generator, whether you write a multi-threaded one in
              Java or you go buy one (Segue for example ... and they are not cheap).

              Peace,

              --
              Cameron Purdy
              Tangosol, Inc.
              Clustering Weblogic? You're either using Coherence, or you should be!
              Download a Tangosol Coherence eval today at http://www.tangosol.com/



              "Alexis Berger" <alexis.berger@wanadoo.fr> wrote in message
              news:3c47f0ac@newsgroups.bea.com...
              Well, I have one client which is trying to query the servlet. (for example
              I
              use internet explorer and do a lot of refresh).


              "Cameron Purdy" <cpurdy@tangosol.com> a écrit dans le message de news:
              3c470fdd@newsgroups.bea.com...
              How are you conducting your load tests? i.e. How do you generate the
              "many
              users" that are hitting the Servlet?

              Peace,

              --
              Cameron Purdy
              Tangosol, Inc.
              Clustering Weblogic? You're either using Coherence, or you should be!
              Download a Tangosol Coherence eval today at http://www.tangosol.com/



              "Alexis Berger" <alexis.berger@wanadoo.fr> wrote in message
              news:3c47075e@newsgroups.bea.com...
              Hi everybody,

              I have a problem that I do not manage to solve by myself so I ask to
              the
              Weblogic Guru :)

              System : win2k sp2, 4 x P3 900 Mhz, 2000 Go ram, Weblogic 5.1 sp9

              I deploy on Weblogic server 14 session stateless EJBs, each one doing
              a
              particular job. (5 seconds max)
              I also deploy one servlet (frontal), which only forwards the query to
              the
              EJBs.

              My problem comes from the servlet. When I try to increase the number
              of
              connections on this servlet,
              I got the following exception :

              mer. janv. 17 17:42:01 CET 2002:<E> <ServletContext-General> Servlet
              failed
              with Exception
              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(ServletResponseIm
              pl.java:603)
              at
              weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
              mpl.java:101)
              at com.webraska.gns.servlet.MyServlet.doPost(Unknown Source)
              at com.webraska.gns.servlet.MyServlet.doGet(Unknown Source)
              at
              javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
              at
              javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :105)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:742)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:686)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              Manager.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)


              Weblogic is supposed to support heavy load as web server so I do not
              understand why I get these exception with only a few number of
              concurent
              connections.

              I try to tune some parameters on the weblogic.properties, but no
              parameter
              saved me :/

              Help me please !
              Best regards,
              Alexis Berger

              • 4. Re: basic problem : connection reset by peer
                3004
                Or download a free one: http://webtool.rte.microsoft.com/

                Cameron Purdy <cpurdy@tangosol.com> wrote:
                Well, if you refresh before the last byte is received, that will close the
                socket and you will see the error that you described. Everything is working
                as it should in this case.
                You need to use a load generator, whether you write a multi-threaded one in
                Java or you go buy one (Segue for example ... and they are not cheap).
                Peace,
                --
                Cameron Purdy
                Tangosol, Inc.
                Clustering Weblogic? You're either using Coherence, or you should be!
                Download a Tangosol Coherence eval today at http://www.tangosol.com/
                "Alexis Berger" <alexis.berger@wanadoo.fr> wrote in message
                news:3c47f0ac@newsgroups.bea.com...
                Well, I have one client which is trying to query the servlet. (for example
                I
                use internet explorer and do a lot of refresh).


                "Cameron Purdy" <cpurdy@tangosol.com> a écrit dans le message de news:
                3c470fdd@newsgroups.bea.com...
                How are you conducting your load tests? i.e. How do you generate the
                "many
                users" that are hitting the Servlet?

                Peace,

                --
                Cameron Purdy
                Tangosol, Inc.
                Clustering Weblogic? You're either using Coherence, or you should be!
                Download a Tangosol Coherence eval today at http://www.tangosol.com/



                "Alexis Berger" <alexis.berger@wanadoo.fr> wrote in message
                news:3c47075e@newsgroups.bea.com...
                Hi everybody,

                I have a problem that I do not manage to solve by myself so I ask to
                the
                Weblogic Guru :)

                System : win2k sp2, 4 x P3 900 Mhz, 2000 Go ram, Weblogic 5.1 sp9

                I deploy on Weblogic server 14 session stateless EJBs, each one doing
                a
                particular job. (5 seconds max)
                I also deploy one servlet (frontal), which only forwards the query to
                the
                EJBs.

                My problem comes from the servlet. When I try to increase the number
                of
                connections on this servlet,
                I got the following exception :

                mer. janv. 17 17:42:01 CET 2002:<E> <ServletContext-General> Servlet
                failed
                with Exception
                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(ServletResponseIm
                pl.java:603)
                at
                weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
                mpl.java:101)
                at com.webraska.gns.servlet.MyServlet.doPost(Unknown Source)
                at com.webraska.gns.servlet.MyServlet.doGet(Unknown Source)
                at
                javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
                at
                javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
                at
                weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
                :105)
                at
                weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
                l.java:742)
                at
                weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
                l.java:686)
                at
                weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
                Manager.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)


                Weblogic is supposed to support heavy load as web server so I do not
                understand why I get these exception with only a few number of
                concurent
                connections.

                I try to tune some parameters on the weblogic.properties, but no
                parameter
                saved me :/

                Help me please !
                Best regards,
                Alexis Berger

                --
                Dimitri