User Lookup Can Cause Performances Issues


  • Jenkins is getting slow and eventually freezes
  • Many threads WAITING trying to get user information from Security Realm
  • Many threads WAITING trying to get user information from Security Realm (Pipeline Stage View)


  • CloudBees Jenkins Enterprise
  • Jenkins

Related Issue(s)


Since the resolution of SECURITY-243, all the users in the commits of an SCM changeset need to be looked up in the Security Realm to see if they are valid authentication “users”. For more details, please have look at JENKINS-35493.

In general, any process interacting with SCM changesets is impacted (for example viewing a page with changelog). In particular, Pipeline jobs are impacted as the Pipeline Stage View Plugin attempts to resolve authors of ChangeLog entries of the ChangeSet to specific users, and this API is invoked with each page view, so it is hit frequently. For more details, please have look at JENKINS-35484.

This can cause performance issues, especially for large instances. Symptoms are a large number of threads requesting user information to the Security Realm, instance unresponsive, users unable to login. When the Security Realm server is overloaded, Jenkins eventually freezes and needs to be restarted.


The solution is to upgrade to CJP 2.7.19.x or later. A cache has been implemented for User/Groups in the version 2.7.3 of Jenkins Core. For more details, please have a look at the pull request of Jenkins core PR#2446

Before Jenkins 2.7.3 / CJP 2.7.19.x

If upgrading Jenkins is not an option, the workaround is to disable the user lookup behavior using the following system properties:


Have more questions? Submit a request


Please sign in to leave a comment.