Uploaded image for project: 'Crowd'
  1. Crowd
  2. CWD-3769

Adding a token to database causes transaction to lock indefinitely

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: 2.7.1
    • Fix Version/s: 2.7.2
    • Component/s: Database
    • Labels:
      None

      Description

      Steps to reproduce

      1. Bring up Crowd using HSQLDB 2.3.0 (this may be reproducible with Postgres 8.4, to be confirmed).
      2. Set up Crowd to use an Embedded database.
      3. Continue through the setup process.

      Expected result

      Crowd setup process completes and user is presented with a login screen.

      Observed result

      Crowd hangs after the last screen of the setup process, and never presents the login screen. Crowd becomes unresponsive.

      Workaround 1

      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

      Workaround 2

      If workaround 1 does not help, you may try this. However, please note that performing this workaround will force users to login again.

      1. Shutdown crowd - ensure the pid is stopped
      2. Perform a database backup
      3. Connect to the database
      4. Execute this sql:
        delete from cwd_token;
      5. Restart Crowd
      6. Validate the session storage is now in-memory by Navigating to Administration > Session Config

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              dberrueta Diego Berrueta
              Votes:
              38 Vote for this issue
              Watchers:
              72 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: