[
https://issues.apache.org/jira/browse/DIRSERVER-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132992#comment-17132992
]
Emmanuel Lécharny commented on DIRSERVER-2314:
----------------------------------------------
This is all correct.
The whole point in using a cache is to speed up processing for frequently used
elements. Here, the cache is diverted from it's basic role, and this cause
problems. I do think we should *not* use a cache for aliases, but rather a data
structure that we feed at startup and maintain during the server updates. There
are other places where we use such a 'cache', like the admin interceptor, but
we use another data structure, the {{DnNode}} class, which associates a {{DN}}
with an entry. This is most certainly what we should use for aliases.
> Aliases don't work correctly after a restart
> --------------------------------------------
>
> Key: DIRSERVER-2314
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2314
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: alias, search
> Affects Versions: 2.0.0.AM26
> Reporter: Kaamil Jasani
> Priority: Major
>
> If a server that contains an alias is restarted, the alias is no longer
> followed. This persists until the alias in question is somehow updated,
> either by renaming, moving, or updating the target.
> It seems on initial look that this may be caused by the alias cache not being
> rebuilt on startup. The cache seems to be empty on restart but this looks to
> be interpreted as the alias not pointing to anything.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
