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

Default value of 0 for session.validationinterval leads to poor performance

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 2.3.4
    • None
    • None
    • None

      The default value of 0 for session.validationinterval leads to poor performance. As the documentation says, it means that every single incoming request to the application will need to make at least one request out to Crowd. Currently when using SSO (i.e. the Crowd authenticator) it makes 2 connections to Crowd per request. One to validate the SSO token and one to get the SSO cookie configuration (see CrowdHttpAuthenticatorImpl#isAuthenticated) Since Confluence does this in a filter, it means even requests to fetch CSS, JS and other resource files make 2 requests. I measured the dashboard in Confluence 3.3 make 38 requests to Crowd in a single page load.

      We should really change the default value in the bundled properties file (and update the documentation) to a non-zero value so it looks up the user from the session until the validation interval is reached.

            [CWD-2647] Default value of 0 for session.validationinterval leads to poor performance

            Robert Chang added a comment - A relevant KB has been created: https://confluence.atlassian.com/crowdkb/applications-connected-with-crowd-sso-sending-huge-amount-of-requests-to-crowd-827343714.html

            Hi intersol_OLD, which product are you trying to integrate with Crowd? Note that the fix was to modify the crowd.properties in the integrated products (Confluence, Bamboo, etc.).

            Diego Berrueta added a comment - Hi intersol_OLD , which product are you trying to integrate with Crowd? Note that the fix was to modify the crowd.properties in the integrated products (Confluence, Bamboo, etc.).

            intersol_old added a comment -

            Please reopen this bug, this was not fixed in Crowd and we are using version 2.7.2. Crowd was using value 0 even if this was not configured. We had to override the default in crowd.properties and setup of value of 60 (minutes, I supposed as nobody documented it).

            intersol_old added a comment - Please reopen this bug, this was not fixed in Crowd and we are using version 2.7.2. Crowd was using value 0 even if this was not configured. We had to override the default in crowd.properties and setup of value of 60 (minutes, I supposed as nobody documented it).

            This was fixed for Confluence some time ago (CONF-23362), but it still needs to be fixed in Bamboo. I've raised BAM-13560 to track the fix in Bamboo.

            Diego Berrueta added a comment - This was fixed for Confluence some time ago ( CONF-23362 ), but it still needs to be fixed in Bamboo. I've raised BAM-13560 to track the fix in Bamboo.

            mbeccati added a comment -

            The same issue happens on new installs of Crowd 2.6.4 and Bamboo 5.0.0.

            mbeccati added a comment - The same issue happens on new installs of Crowd 2.6.4 and Bamboo 5.0.0.

            joe added a comment -

            Change the value in the Crowd distributions so users taking a copy of the configuration will get better performance. The linked issue will fix the value in the Confluence distribution.

            joe added a comment - Change the value in the Crowd distributions so users taking a copy of the configuration will get better performance. The linked issue will fix the value in the Confluence distribution.

            Raising to blocker as this is a cause of extreme performance degradation.

            Scott Farquhar added a comment - Raising to blocker as this is a cause of extreme performance degradation.

              jwalton joe
              nbhawnani Niraj Bhawnani
              Affected customers:
              0 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  Remaining Estimate - 4h
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified