Troubleshooting Crowd Performance
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 application is slow!
- Ensure you are running the latest version of Crowd.
- 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 matches the version of Crowd you are running (e.g.crowd-integration-client-1.5.jar
). - Confirm that the
crowd-ehcache.xml
file located in theJira/ConfluenceWEB-INF/classes
directory matches the one in theCROWD/client/conf
directory.
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
orstdout.log
. If Confluence, also attach theatlassian-confluence.log
file in the Confluence home directory (specified in theconfluence-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:
ping ad1.mycompany.com
ping ad2.mycompany.au
RELATED TOPICS
Last modified on Sep 14, 2022
Powered by Confluence and Scroll Viewport.