Socket Thread Affinity Breaks Max Pool Size

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Critical - P2
    • 1.8.2
    • Affects Version/s: 1.8.1
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This issue was introduced into v1.8.1 in a recent change from a pull request on github.

      This change intended to introduce thread affinity to the socket pool but the result was that it caused a failure to issue new sockets to existing threads and fully utilize the maximum socket pool size.

      Threads attempting to checkout sockets from the pool were getting blocked and being forced to wait for an existing socket even when the total pool size was well below the max size value.

            Assignee:
            Brandon Black (Inactive)
            Reporter:
            Brandon Black (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: