accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1507) Dynamic Classloader still can't keep proper track of jars
Date Tue, 29 Oct 2013 21:07:25 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808453#comment-13808453
] 

ASF subversion and git services commented on ACCUMULO-1507:
-----------------------------------------------------------

Commit ebbedb4fe3cf90460e31657b5f8872a9d296bed6 in branch refs/heads/master from [~jvines@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=ebbedb4 ]

ACCUMULO-1507 - adding a (nonfunctional/commented out) test for the monitor issue


> 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
>            Reporter: John Vines
>            Assignee: John Vines
>             Fix For: 1.5.1, 1.6.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.1#6144)

Mime
View raw message