You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "ASF GitHub Bot (Jira)" <de...@uima.apache.org> on 2019/09/09 20:47:00 UTC

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

     [ https://issues.apache.org/jira/browse/UIMA-5935?focusedWorklogId=309232&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-309232 ]

ASF GitHub Bot logged work on UIMA-5935:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Sep/19 20:46
            Start Date: 09/Sep/19 20:46
    Worklog Time Spent: 10m 
      Work Description: mischor commented on pull request #9: Fix for Bug UIMA-5935
URL: https://github.com/apache/uima-uimaj/pull/9
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 309232)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>            Assignee: Marshall Schor
>            Priority: Major
>             Fix For: 3.0.2SDK, 2.10.4SDK
>
>         Attachments: Screenshot from 2018-12-18 08-34-10.png, UIMA-5935.diff
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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
(v8.3.2#803003)