[
https://issues.apache.org/jira/browse/DIRSERVER-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130621#comment-17130621
]
Kaamil Jasani commented on DIRSERVER-2314:
------------------------------------------
Wanted to highlight another related issue:
Seems that the expiry of 20 minutes also means that aliases stop working 20
minutes after they were last accessed/updated. There should probably either be
some check for if the cache is expired to re-feed it, or to have the alias
cache not expire.
Also, and I have not tested this one, but for the same reason the maximum cache
size seems to be a problem if a lot of aliases exist since some of them would
not be present in the cache and, as it stands, the code would not look to the
index in that case, which means some of the aliases would work and others would
not.
> 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]
