Details
-
Suggestion
-
Resolution: Obsolete
-
None
-
None
Description
Please note that since 3.0.0 release Crowd can be run in Data Center mode which supports Clustering. This is the supported way of running Crowd in cluster.
Crowd isn't supported in a clustered environment (), but it can work in some configurations.CWD-1053
After configuring Crowd in a Tomcat cluster (Clustering/Session Replication HOW-TO) and pointing all instances at a common database, this is a tracking bug for the remaining issues.
- Crowd's web.xml does not mark it as <distributable/>
- Hibernate's second-level and query caches are enabled, so administration changes to settings are not communicated between instances
- Password reset tokens are not distributed; a password can only be reset against same instance that sent the email
- Synchronisation is not aware of clustering; any cached directories will fail when synchronisation runs at the same time
Attachments
Issue Links
- blocks
-
CWD-1053 Officially support Crowd clustering
- Closed
- is blocked by
-
CWD-4044 Store password reset tokens in the database
- Closed
-
CWD-4046 Import Configuration classes are not serializable
- Closed
- is related to
-
CWD-3783 Invite and Reset Password Tokens should be persisted to database
- Closed
-
CWD-3781 Configuration objects used during imports should be serializable
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...