I've reproduced it locally, although it is not deterministic and may require some patience.
Steps to reproduce
- 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).
- Once the set up is completed, log in as 'admin'.
- 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.
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.
At this point the workaround is to switch the session storage to in-memory from database storage:
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:
- Shutdown crowd - ensure the pid is stopped
- Perform a database backup
- Connect to the database
- Execute this sql:
- Restart Crowd
- Validate the session storage is now in-memory by Navigating to Administration > Session Config