[
https://issues.apache.org/jira/browse/DIRSERVER-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-210.
---------------------------------------
Closing all issues created in 2005 and before which are marked resolved
> CachingNormalizer exhibits concurrency flaw under load.
> -------------------------------------------------------
>
> Key: DIRSERVER-210
> URL: https://issues.apache.org/jira/browse/DIRSERVER-210
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: pre-1.0
> Reporter: Jacob S. Barrett
> Assigned To: Emmanuel Lecharny
> Fix For: pre-1.0
>
> Attachments: CachingNormalizer-Concurrency.patch
>
>
> CachingNormalizer doesn't have it's cache protected from concurrent
> modifications. Under load a state is reached where cache.containsKey(key) is
> true but the result of cache.get(key) results in an unexpected null value and
> thus a NullPointerException. This is really only reached when you have more
> than threads than the max cache size and therefore items in the cache are
> being purged. The attached path synchronizes the cache. It would be better
> to use a R/W lock from JSR 166 backport or something similar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
