You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2014/01/16 11:51:21 UTC

[jira] [Resolved] (STANBOL-1258) EntityCache of FST Linking Engine is not correctly managed

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

Rupert Westenthaler resolved STANBOL-1258.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.12.0

fixed with http://svn.apache.org/r1558711 in 0.12 and http://svn.apache.org/r1558748 in trunk

> EntityCache of FST Linking Engine is not correctly managed
> ----------------------------------------------------------
>
>                 Key: STANBOL-1258
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1258
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Enhancement Engines
>    Affects Versions: 0.12.0
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>             Fix For: 0.12.0
>
>
> The EntityCache used by the FST Linking engine is not correctly managing the reference count. This can prevent instances to be immediately destroyed when they are no longer used. They will still get destroyed by the GC, but only at a later point in time causing higher memory consumption as needed.
> In addition EntityCacheManager needs a close() method allowing to explicitly close the cache if the Engine is deactivated.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)