[
https://issues.jenkins-ci.org/browse/JENKINS-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163608#comment-163608
]
Thorsten Heit commented on JENKINS-13547:
-----------------------------------------
{quote}It seems like that every request to Jenkins gets authenticated to Crowd
or something like that.{quote}
Indeed. The plugin is implemented as a servlet filter that checks the validity
of the session on each request that is being processed.
{quote}The original Crowd plugin does not have this problem and does not affect
the performance of Jenkins in any visible form.{quote}
The original Crowd plugin contains a hardcoded session validation interval time
of 5 minutes. See
[https://github.com/jenkinsci/crowd-plugin/blob/master/src/main/java/com/ds/tools/hudson/crowd/CrowdSecurityRealm.java],
method "createSecurityComponents()"
> Jenkins runs extremely slow with remote crowd server
> ----------------------------------------------------
>
> Key: JENKINS-13547
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13547
> Project: Jenkins
> Issue Type: Bug
> Components: crowd2
> Environment: Centos/RHEL 6.2
> Jenkins 1.460
> Crowd 2.2.7
> Reporter: Joel Pearson
> Assignee: Thorsten Heit
> Priority: Critical
>
> When Crowd is running on a different continent to Jenkins, the performance of
> Jenkins is drastically affected, to the point that Jenkins is unusable.
> It seems like that every request to Jenkins gets authenticated to Crowd or
> something like that.
> The original Crowd plugin does not have this problem and does not affect the
> performance of Jenkins in any visible form.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
