You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Simon Gormley (JIRA)" <ji...@apache.org> on 2013/05/13 15:31:16 UTC

[jira] [Created] (ARIES-1068) JNDI lookup performance bad when security enabled

Simon Gormley created ARIES-1068:
------------------------------------

             Summary: 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
            Priority: Critical


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira