[jira] [Resolved] (ACCUMULO-1507) Dynamic Classloader still can't keep proper track of jars

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

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

Christopher Tubbs resolved ACCUMULO-1507.
-----------------------------------------
       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 2.0.0)

The master branch was recently updated to VFS 2.3. Hopefully that fixes it. If not, we can re-open at https://github.com/apache/accumulo/issues , but I think it'd be better to work towards pushing the classloader stuff out to a user-pluggable thing (already available for the system class loader, but we could make the context class loader also pluggable).

> Dynamic Classloader still can't keep proper track of jars
> ---------------------------------------------------------
>
>                 Key: ACCUMULO-1507
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1507
>             Project: Accumulo
>          Issue Type: Bug
>          Components: start
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: John Vines
>            Assignee: John Vines
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> From ACCUMULO-1321-
> It was never quite fixed, it seems. There are two standing issues with the Dynamic Classloader
> # if you delete and drop in a new jar, it's possible that the delete only triggers, causing any classes in the new jar to fail to load unless the file gets renamed in the ext directory
> # if you rename the file in the ext directory, it's still possible that the class files fail to load
> I'm speculating there are race conditions around the Monitor being used to watch the file system, but that is just speculation.



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