James Server
  1. James Server
  2. JAMES-671

ServerConnection doesn't properly handle the TCP/IP backlog

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.2.0, 2.3.0
    • Fix Version/s: 2.3.1
    • Component/s: James Core
    • Labels:
      None

      Description

      ServerConnection calls accept() even when the configured connection limit has been reached, thereby purging the TCP/IP backlog and expending cycles in the process. This is inefficient, drops connections, and renders the backlog configuration setting largely worthless.

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12566319 ] jira [ 12581684 ]
        Mark Thomas made changes -
        Workflow jira [ 12388544 ] Default workflow, editable Closed status [ 12566319 ]
        Danny Angus made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Norman Maurer made changes -
        Fix Version/s 2.3.1-dev [ 12312150 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Fix Version/s Next Major [ 10427 ]
        Fix Version/s Next Minor [ 12312136 ]
        Stefano Bagnara made changes -
        Field Original Value New Value
        Fix Version/s Trunk [ 12312135 ]
        Noel J. Bergman created issue -

          People

          • Assignee:
            Noel J. Bergman
            Reporter:
            Noel J. Bergman
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development