glassfish
  1. glassfish
  2. GLASSFISH-16025

Domain.xml: setting protocol.http-listener-1.http.max-connections set in 1 or -1

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 3.1_b38
    • Fix Version/s: 3.1.1
    • Component/s: grizzly-kernel
    • Labels:
      None
    • Environment:

      Windows XP

      Description

      Hi there,

      with old documentaton for GF 3.0.1 I found that :

      "http.max-connections property (optional) Specifies the maximum number of requests that can be pipelined until the connection is closed by the server. Set this property to 1 to disable HTTP/1.0 keep-alive, as well as HTTP/1.1 keep-alive and pipelined until the connection is closed by the server. A value of 0 means requests are always rejected. A value of -1 sets no limit to the number of keep-alive connections. "

      Now I use the GF 3.1 (build 42) and I set protocol.http-listener-1.http.max-connections set into 1 and seems that connections are not closed(they are keep-alive). Is such behaviour correct?

      When I set into -1, all connections are closed, but I am expecting to see them alive.

      Could anybody explain how this setting works now for version 3.1?

      Thank you

        Activity

        tetyanac created issue -
        Tom Mueller made changes -
        Field Original Value New Value
        Assignee Tom Mueller [ tmueller ] oleksiys [ oleksiys ]
        Component/s grizzly-kernel [ 10632 ]
        Component/s admin [ 10589 ]
        Hide
        oleksiys added a comment -

        it's a bug.

        Workaround is following:

        -1 is not working as unlimited, please use some big number up to Integer.MAX_VALUE.
        1 - will let you process 1 keep-alive request, and close the connection after processing 2nd request on the same connection
        0 - will disable keep-alive for the connection

        Show
        oleksiys added a comment - it's a bug. Workaround is following: -1 is not working as unlimited, please use some big number up to Integer.MAX_VALUE. 1 - will let you process 1 keep-alive request, and close the connection after processing 2nd request on the same connection 0 - will disable keep-alive for the connection
        oleksiys made changes -
        Tags 3_1-release-notes
        Scott Fordin made changes -
        Tags 3_1-release-notes 3_1-release-note-added 3_1-release-notes
        Hide
        Scott Fordin added a comment -

        Added issue to 3.1 Release Notes.

        Show
        Scott Fordin added a comment - Added issue to 3.1 Release Notes.
        Hide
        oleksiys added a comment -

        mark as fixed

        Show
        oleksiys added a comment - mark as fixed
        oleksiys made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 3.1.1 [ 14740 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            oleksiys
            Reporter:
            tetyanac
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: