[ https://issues.apache.org/jira/browse/ACCUMULO-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657096#comment-13657096 ]
John Vines commented on ACCUMULO-1411: -------------------------------------- Apply to Accumulo or to client code? It doesn't work for client code because Mock explicitly uses AccumuloVFSClassLoader.loadClass(); > Cannot use iterators in MockAccumulo running in a secondary classloader > ----------------------------------------------------------------------- > > Key: ACCUMULO-1411 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1411 > Project: Accumulo > Issue Type: Bug > Components: start > Reporter: John Vines > Assignee: John Vines > Priority: Minor > > We have a situation where there is a test client which spins off a Thread > running a MockAccumulo, and then we try to use iterators that are on the > classpath for that Thread. Unfortunately, they CNFE. We've traced it back, > since the ReloadingClassLoader just uses the parent classloader > (AccumuloClassLoader) in absence of configurations. The > AccumuloClassLoader.getClassLoader uses ClassLoader.getSystemClassLoader() as > it's parent, not AccumuloClassLoader.class.getClassLoader(). I believe that > should preserve the way the classloaders work in the standard use cases while > not breaking in any other cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira