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

["Josh Elser (JIRA)" <ji...@apache.org>]

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

Josh Elser updated ACCUMULO-1507:
---------------------------------
    Fix Version/s:     (was: 1.5.2)
                   1.5.3

> 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
>             Fix For: 1.5.3, 1.6.1, 1.7.0
>
>
> 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
(v6.3.4#6332)