[jira] [Commented] (ACCUMULO-721) Reloading of lib/ext classloader causes LinkageError
[ https://issues.apache.org/jira/browse/ACCUMULO-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553353#comment-13553353 ] Josh Elser commented on ACCUMULO-721: - Eh, I'm apt to just call it a day with this ticket. I only ever saw it under one extremely specific of circumstances that I don't even recall. It's probably just for the best to close it as "can't reproduce" and reopen if anyone ever runs into this again. > Reloading of lib/ext classloader causes LinkageError > > > Key: ACCUMULO-721 > URL: https://issues.apache.org/jira/browse/ACCUMULO-721 > Project: Accumulo > Issue Type: Bug > Components: tserver >Reporter: Josh Elser >Assignee: Keith Turner > Fix For: 1.5.0 > > Attachments: ACCUMULO-721-classpath, ACCUMULO-721-tserver.debug.log > > > I was writing an iterator that takes advantage of some classes in Google's > guava-libraries. I placed my jar and the guava-13.0-rc2.jar into lib/ext. > I then ran a simple Java class which opened a Scanner to a table with my > customer Iterator in Eclipse. The first attempt succeeded. I then changed my > iterator, recompiled the jar, and placed it in lib/ext. The > AccumuloClassLoader message said it picked up the changes. Then, trying to > run my class in the same manner, I got a java.lang.LinkageError relating to > the classloader having two different Class objects for a class defined in the > guava jar (which hadn't changed). > Moving the guava jar from lib/ext to lib/ and retrying this experiment did > not net the same LinkageError. > I'll attach full stack traces and the output of `accumulo classpath` -- 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
[jira] [Commented] (ACCUMULO-721) Reloading of lib/ext classloader causes LinkageError
[ https://issues.apache.org/jira/browse/ACCUMULO-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553341#comment-13553341 ] Dave Marion commented on ACCUMULO-721: -- Curious is this issue is OBE due to ACCUMULO-708. Can you try with the new classloader? > Reloading of lib/ext classloader causes LinkageError > > > Key: ACCUMULO-721 > URL: https://issues.apache.org/jira/browse/ACCUMULO-721 > Project: Accumulo > Issue Type: Bug > Components: tserver >Reporter: Josh Elser >Assignee: Keith Turner > Fix For: 1.5.0 > > Attachments: ACCUMULO-721-classpath, ACCUMULO-721-tserver.debug.log > > > I was writing an iterator that takes advantage of some classes in Google's > guava-libraries. I placed my jar and the guava-13.0-rc2.jar into lib/ext. > I then ran a simple Java class which opened a Scanner to a table with my > customer Iterator in Eclipse. The first attempt succeeded. I then changed my > iterator, recompiled the jar, and placed it in lib/ext. The > AccumuloClassLoader message said it picked up the changes. Then, trying to > run my class in the same manner, I got a java.lang.LinkageError relating to > the classloader having two different Class objects for a class defined in the > guava jar (which hadn't changed). > Moving the guava jar from lib/ext to lib/ and retrying this experiment did > not net the same LinkageError. > I'll attach full stack traces and the output of `accumulo classpath` -- 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
