[
https://issues.apache.org/jira/browse/OAK-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644806#comment-14644806
]
Tobias Bocanegra edited comment on OAK-3146 at 7/28/15 6:30 PM:
----------------------------------------------------------------
I would just remove the performance label and fix the issue w/o benchmark. from
the description and code-flow it is obvious that it can lead to inconsistent
situations when the login module is initialized during the logout phase. so not
directly performance related.
was (Author: tripod):
I would just remove the performance label and fix the issue w/o benchmark. from
the description and code-flow it is obvious that it can inconsistent situations
when the login module is initialized during the logout phase. so not directly
performance related.
> ExternalLoginModuleFactory should inject SyncManager and
> ExternalIdentityProviderManager
> ----------------------------------------------------------------------------------------
>
> Key: OAK-3146
> URL: https://issues.apache.org/jira/browse/OAK-3146
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: security
> Reporter: Chetan Mehrotra
> Priority: Minor
> Labels: performance
> Fix For: 1.3.4
>
> Attachments: OAK-3146.patch
>
>
> {{ExternalLoginModule}} currently performs a lookup of {{SyncManager}} and
> {{ExternalIdentityProviderManager}} in initialize call which performs service
> lookup using ServiceTracker. Doing a service lookup in critical path would
> have adverse performance impact.
> Instead of performing the lookup {{ExternalLoginModuleFactory}} should track
> the two manager instances and pass them to {{ExternalLoginModule}}. This
> would ensure that expensive operation like service lookup is not performed in
> critical path
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
