You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Matthias Koch (JIRA)" <de...@uima.apache.org> on 2019/01/16 12:29:00 UTC

[jira] [Updated] (UIMA-5935) Destroy the ResourceManager on destroy of a pear

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

Matthias Koch updated UIMA-5935:
--------------------------------
    Attachment: UIMA-5935.diff

> Destroy the ResourceManager on destroy of a pear 
> -------------------------------------------------
>
>                 Key: UIMA-5935
>                 URL: https://issues.apache.org/jira/browse/UIMA-5935
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.10.3SDK
>            Reporter: Philipp Butz
>            Priority: Major
>         Attachments: Screenshot from 2018-12-18 08-34-10.png, UIMA-5935.diff
>
>
> This bug is related to bug UIMA-5799 . The bug seems not completely fixed, since the files are still being accessed after trying to delete them. This behavior can be shown by the tool 'lsof' (see screenshot). There seems still access to the resources of a pear on the file system, which denies the complete deletion on the file system after uninstalling it (they are marked as deleted but are not actually removed).
>  
> Potential cause:
> The class PearAnalysisEngineWrapper creates and caches resource managers. The elements in that Cache (Java map) are never explicitly removed, not even in the destroy method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)