aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1068) JNDI lookup performance bad when security enabled
Date Wed, 21 Feb 2018 09:06:00 GMT

    [ https://issues.apache.org/jira/browse/ARIES-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371113#comment-16371113
] 

ASF subversion and git services commented on ARIES-1068:
--------------------------------------------------------

Commit 1824944 from [~gnt] in branch 'aries/trunk'
[ https://svn.apache.org/r1824944 ]

[jndi] Big refactoring, introducing caching per ARIES-1068

> JNDI lookup performance bad when security enabled
> -------------------------------------------------
>
>                 Key: ARIES-1068
>                 URL: https://issues.apache.org/jira/browse/ARIES-1068
>             Project: Aries
>          Issue Type: Bug
>          Components: JNDI
>            Reporter: Simon Gormley
>            Assignee: Guillaume Nodet
>            Priority: Critical
>         Attachments: servicelookupperf.patch
>
>
> JNDI lookups can be slow if Java security is enabled, specifically the getService methods
take time.
> If the services are cached then the lookup only has to be performed once, but care has
to be taken that the context performing the service lookup has the required permissions to
do so, and so cache buckets for each context will be necessary. 
> Also to prevent a leak, when contexts drop from scope, the associated caches need to
be cleared out.
> The ServiceTrackerCustomizer for JNDI already had some caching ability, and the provided
patch extends this to avoid looking up Services where possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message