This page last changed on Sep 03, 2008 by donna@atlassian.com.
 | Please note:
This guide assumes you have already opened a Crowd support issue at http://support.atlassian.com and wish to provide additional information about your Crowd configuration in this issue. |
1. The Crowd 1.4.x application is slow!
- Ensure you are running the latest version of Crowd 1.4.x.
- Under Admin -> Logging & Profiling in Crowd:
- Change the com.atlassian.crowd package to DEBUG.
- Enable profiling.
- Replicate the performance issues you are seeing in Crowd (e.g. log out and log in, browse users, etc.)
- Attach the resulting CROWD_DIRECTORY/atlassian-crowd.log file to your support ticket.
- List the directories and applications active in your Crowd instance.
- Provide rough estimates of the number of users and groups that are available in each LDAP directory configuration.
- Provide information about the network location of any LDAP servers in respect to the Crowd server (e.g. same subnet, different networks, different states).
- If using Active Directory, is SSL enabled?
2. JIRA/Confluence is slow!
- Confirm that data caching is enabled in Crowd.
- Confirm that the only crowd-integration-client JAR in the JIRA/Confluence WEB-INF/lib directory is the crowd-integration-client-1.4.4-SNAPSHOT.jar file.
- Confirm that the crowd-ehcache.xml file located in the JIRA/ConfluenceWEB-INF/classes directory matches this one
- If your Crowd installation contains more than 50,000 users, review the guide at Configuring Caching for an Application.
a. JIRA/Confluence still slow?
- Stop JIRA/Confluence.
- Temporarily replace the WEB-INF/lib/crowd-integration-client-1.x.JAR file with the appropriate version from this issue.
- Restart JIRA/Confluence.
- Under Admin -> Logging & Profiling in JIRA/Confluence:
- Change the com.atlassian package to DEBUG.
- Enable profiling.
- Perform actions in JIRA/Confluence that are slow to respond (e.g. log out and log in, browse users, etc).
- Attach the resulting JIRA/Confluence logs/catalina.out or stdout.log. If Confluence, also attach the atlassian-confluence.log file in the Confluence home directory (specified in the confluence-init.properties file at setup).
- List the directories and applications active in your Crowd instance for the JIRA/Confluence application.
- Provide rough estimates of the number of users and groups that are available in each LDAP directory configuration for the JIRA/Confluence application.
- Provide information about the network location of any LDAP servers in respect to the Crowd server (e.g. same subnet, different networks, different states).
b. Using Active Directory?
- Is SSL enabled?
- Are you using nested groups (is the Use Nested Groups box checked in Crowd)?
- If login is slow, please connect to your AD server using Apache Directory Studio and highlight the username used for this login. Provide a screenshot of this user — especially the list of memberOf attributes for this account (should contain full DNs).
- Please also confirm that all domain controllers referenced in these groups are resolvable/reachable from the Crowd server using ping:
|