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

Resolve issues running Crowd in a cluster

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Obsolete
    • Fix Version/s: 3.0.0
    • Component/s: None
    • Labels:
      None
    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      Note

      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 (CWD-1053), but it can work in some configurations.

      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

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              jwalton joe
              Votes:
              20 Vote for this issue
              Watchers:
              23 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: