• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.7.1
    • 2.7
    • Database
    • None

      I've reproduced it locally, although it is not deterministic and may require some patience.

      Steps to reproduce

      1. Set up a fresh installation of Crowd 2.7.0, connected to a database (I'm using Postgres 9.1, although there are customer reporting problems with MySQL and SQL Server as well).
      2. Once the set up is completed, log in as 'admin'.
      3. Reload (Cmd-R or similar) the home page repeatedly. Do not wait for it to refresh completely in your browser, just reload as fast as you can.

      Observed outcome

      Eventually, the page does not refresh anymore. Crowd freezes.

      Using the Postgres admin tools, we find that there is a client that is locking the cwd_token table, see attached image.

      WORKAROUND

      At this point the workaround is to switch the session storage to in-memory from database storage:
      Session Configuration

      The in-memory storage is explained in more detail on the page linked above.

      If you cannot keep crowd up long enough to access the Administration console, or crowd will simply not finish starting up, follow these steps to modify the value directly in the database:

      1. Shutdown crowd - ensure the pid is stopped
      2. Perform a database backup
      3. Connect to the database
      4. Execute this sql:
        update cwd_property 
        set property_value='false'
        where property_name='database.token.storage.enabled';
      5. Restart Crowd
      6. Validate the session storage is now in-memory by Navigating to Administration > Session Config

            [CWD-3692] Crowd freezes under heavy load

            Renata Dornelas made changes -
            Remote Link Original: This issue links to "Wiki Page (Atlassian Documentation)" [ 51878 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 - restricted [ 1511203 ] New: JAC Bug Workflow v3 [ 3365364 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            dberrueta The problem exists even with Crowd >=3.1.1, we have the problem with one of our clients recently and has caused a production downtime of 1.5h.

            Filip Minic added a comment - dberrueta The problem exists even with Crowd >=3.1.1, we have the problem with one of our clients recently and has caused a production downtime of 1.5h.
            Owen made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1393633 ] New: Simplified Crowd Development Workflow v2 - restricted [ 1511203 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 577290 ] New: Simplified Crowd Development Workflow v2 [ 1393633 ]
            Ferd made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 139163 ]
            Jonathan G made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 94231 ]
            Jonathan G made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 56914 ] New: This issue links to "Page (Extranet)" [ 56914 ]
            Jonathan G made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 56914 ] New: This issue links to "Page (Extranet)" [ 56914 ]
            JamesA made changes -
            Remote Link New: This issue links to "ADM-50903 (Atlassian JIRA Extranet - Special Projects)" [ 58452 ]

              dberrueta Diego Berrueta
              dberrueta Diego Berrueta
              Affected customers:
              1 This affects my team
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: