[jira] [Comment Edited] (ACCUMULO-4128) ShellServerIT#scansWithClassLoaderContext fails consistently

["Dave Marion (JIRA)" <ji...@apache.org>]

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

Dave Marion edited comment on ACCUMULO-4128 at 7/18/16 4:37 PM:
----------------------------------------------------------------

I think I know what's going on, but I don't know where to look to fix it. I put in a bunch of debug and found that the classloaders that are loading the iterators for the test are the same (same instance). Furthermore, they are not VFS classloader or URL classloaders, they are of type sun.misc.Launcher$AppClassLoader, which (according to [1]) is the class loader for the application (in this case the TabletServer). Is there a way to print out the classpath of the java process that is started for MAC?

[1] https://blogs.oracle.com/sundararajan/entry/understanding_java_class_loading



was (Author: dlmarion):
I think I know what's going on, but I don't know where to look to fix it. I put in a bunch of debug and found that the classloaders that are loading the iterators for the test are the same (same instance). Furthermore, they are not VFS classloader or URL classloaders, then are of type sun.misc.Launcher$AppClassLoader, which (according to [1]) is the class loader for the application (in this case the TabletServer). Is there a way to print out the classpath of the java process that is started for MAC?

[1] https://blogs.oracle.com/sundararajan/entry/understanding_java_class_loading


> ShellServerIT#scansWithClassLoaderContext fails consistently
> ------------------------------------------------------------
>
>                 Key: ACCUMULO-4128
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4128
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>            Reporter: Eric Newton
>             Fix For: 2.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)