[
https://issues.apache.org/jira/browse/DIRSERVER-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated DIRSERVER-2036:
-------------------------------------------
Attachment: dirserver-2036.patch.2
Hi Stefan,
See a revised patch for this issue which addresses your two concerns. It uses
the UUID in all cases as the CacheManager name. Secondly, it appends the
CacheManager name (the UUID) to the diskstore path. So for example, if I run
the tests I end up with cache files stored in something like:
/tmp/a2985259-73d5-471e-ad19-e4626c8ff2d8
Colm.
> Upgrade EhCache dependency
> --------------------------
>
> Key: DIRSERVER-2036
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2036
> Project: Directory ApacheDS
> Issue Type: Improvement
> Reporter: Colm O hEigeartaigh
> Fix For: 2.0.0-M20
>
> Attachments: dirserver-2036.patch, dirserver-2036.patch.2
>
>
> Apache DS uses a old version of EhCache. This task is to upgrade to a newer
> version. Since EhCache 2.5.x, it is not permitted to create new CacheManagers
> with the same name. The patch attached to this JIRA works around this by
> associating the instanceId with the CacheManager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
