You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kiran Ayyagari (JIRA)" <ji...@apache.org> on 2010/12/04 12:38:11 UTC

[jira] Closed: (DIRKRB-80) InMemoryReplayCache extends Thread

     [ https://issues.apache.org/jira/browse/DIRKRB-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kiran Ayyagari closed DIRKRB-80.
--------------------------------

    Resolution: Fixed

Updated to use Ehcache and renamed the InMemoryReplayCache to ReplayCacheImpl.

Fixed in the kerberos-codec-2.0 branch http://svn.apache.org/viewvc?rev=1042145&view=rev

> InMemoryReplayCache extends Thread
> ----------------------------------
>
>                 Key: DIRKRB-80
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-80
>             Project: Directory Kerberos
>          Issue Type: Bug
>            Reporter: Stefan Seelmann
>            Assignee: Kiran Ayyagari
>
> The class org.apache.directory.server.kerberos.shared.replay.InMemoryReplayCache extends Thread. For each instance the thread is started, its task is to clean expired entries from the cache. The cache is used three times in the server, so three threads are started.
> We should check if this is really required. An alternative would be to use ehcache CacheManager.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.