Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-4096

RestCrowdClient http.max.connections doesn't take effect when the base URL doesn't include a port

    XMLWordPrintable

Details

    • Bug
    • Resolution: Deployed
    • Medium
    • 2.8.2
    • 2.8
    • None
    • None

    Description

      In OnDemand, the Crowd Base URL is configured as http://localhost/crowd/service/

      During RestExecutor initialisation the maximum connections per route is configured for the route "http://localhost" to be 20. There's a subtle problem with this though. When actually issuing a request to Horde, the HttpRoute becomes "http://localhost:80", which is treated differently, and falls back to the default maximum connections per route of 2.

      It looks like INST-2 introduced this issue, when they updated the Icebat to explicitly hack the CROWD_SERVER_BASE_URL in each services run file. /cc cchauvet

      Ultimately this looks like it might actually be an Apache HttpClient bug. In debugging I noticed that the outbound request is definitely "http://localhost/crowd/foo", but after it passes through all the various HttpClient "*Exec" steps it ends up as "http://localhost:80/crowd/foo".

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. BSERV-7081 Only 2 concurrent connections allowed to external Crowd server

          • Medium - Medium priority issues
          • Closed
          is caused by

          Suggestion - CWD-2942 Replace commons-httpclient with Apache HttpComponents

          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. CWD-4196 Crowd http-client token validation can trigger a flood of requests

          • High - High priority issues
          • Closed

          KRAK-256 Loading...

          was split into

          Bug - A problem which impairs or prevents the functions of the product. CWD-4337 RestCrowdClient http.max.connections doesn't take effect when the base URL is under https

          • Medium - Medium priority issues
          • Closed
          links to

          Web Link HTTPCLIENT-1575 - PoolingHttpClientConnectionManager.setMaxPerRoute accepts, but ignores, HttpRoutes with default ports

          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Activity

            People

              jwalton joe
              sday@atlassian.com Samuel Day (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: