[
https://issues.apache.org/jira/browse/ACCUMULO-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451282#comment-16451282
]
Christopher Tubbs commented on ACCUMULO-1507:
---------------------------------------------
I'm thinking we should work towards dropping this dynamic class loader feature
entirely. We can't seem to get it right, and it's way out of scope of Accumulo
anyway. If users need a custom class loader with special features, they can
always just set the bootstrap class loader as an argument to the JVM when they
start the Java process (with one that suits their needs). Maybe we can move our
existing class loader to a subproject for such use cases, but it really should
be separated from Accumulo's core code.
> 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
> Fix For: 2.0.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
(v7.6.3#76005)
