4 Replies Latest reply on Oct 11, 2006 3:55 AM by diego.loro

    Double HttpRequest Problem



      I have a problem when I deploy my WebApplication under JBOSS, a problem that seems to be absent deploying the same application under others AppServers.

      Here is the question:
      - it seems that every HttpRequest sent by the browser to the Jboss Server (Post or Get request) is doubled, in other words the server seems to receive two requests from the browser of the webApp user.

      I'm quite sure that the problem is related to the appServer, but at now I don't understant what's going wrong...

      Any ideas?
      Thank's a lot for your answers!

        • 1. Re: Double HttpRequest Problem

          How did you determine that the app server is sending the requests twice? Personally, I have never experienced this behavior.

          • 2. Re: Double HttpRequest Problem

            Hi Peter,

            using TCPMON I can see that the server receives twice all the client requests.
            The first immediately and the second after few seconds.
            It is very strange, because the HTML code is quite simple and with other AppServers like Websphere the problem doesn't exists.
            So I think about some possible configuration problem with JBOSS.

            if you have any ideas..

            • 3. Re: Double HttpRequest Problem

              Sorry, but I don't know why TCPMON would show duplicate transmissions, other than network issues that might cause the server to request a retransmit, or JavaScript in the HTML that does a periodic refresh request. I have never noticed duplicate requests in any of my servlets from plain HTML.

              • 4. Re: Double HttpRequest Problem

                Hi Peter,

                now the problem is more restricted.
                Only the requests sent from a client that is on the same machine of the JBOSS AppServer are duplicated (so calls to localhost).
                If the client and the server are on different machines (or the client invokes the server by its http://ipaddress:port/url instead of http://localhost:8080/url) the problem does not exists.
                So I think that, as you suppose, the problem could be related to some network issues.