[
https://issues.apache.org/jira/browse/STANBOL-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-1442.
------------------------------------------
Resolution: Fixed
fixed with http://svn.apache.org/viewvc?rev=1707665&view=rev in 0.12.1 and
http://svn.apache.org/viewvc?rev=1707666&view=rev in trunk
> SolrCore swap support of FSTLinkingEngine does not free old SolrCore
> ---------------------------------------------------------------------
>
> Key: STANBOL-1442
> URL: https://issues.apache.org/jira/browse/STANBOL-1442
> Project: Stanbol
> Issue Type: Bug
> Components: Enhancement Engines
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Fix For: 1.0.0, 0.12.1
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> This feature (and the bug) was introduced with STANBOL-1440. because of a
> equals(..) check with the wrong field of the {{FstLinkingEngineComponent}}
> engine instances registered for unregistered SolrCores are not closed.
> Because of this also the {{SolrCore.close()}} method of the SolrCore used by
> this engine is not called. This causes those SolrCores (that are no longer
> registered with any Solr CoreContainer) not to be closed (as the reference
> count of those core will not reach zero).
> However NOTE if a SolrCore is updated the old one is freed by the FST linking
> engine and closed (as after the switch to the new one the engine
> automatically frees the old). So this only happens if a SolrCore is removed
> (e.g. if it is removed from the ManagedSolrServer or if the SolrServer is
> deactivated as a whole).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
