accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1321) Dynamic Classloader lost jars
Date Thu, 25 Apr 2013 18:44:16 GMT

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

Keith Turner commented on ACCUMULO-1321:
----------------------------------------

If I regenerate the jar with the same code and copy in the jar I did not see a problem.  I
tried this 5 or 6 times w/o issue.  When I changed the source code, generated the jar, and
copied it in I immediately saw the issue. MAybe this is a factor.  I think the unit test use
the same class file to test reloading.  I am going to add a case where the class file has
changed.
                
> Dynamic Classloader lost jars
> -----------------------------
>
>                 Key: ACCUMULO-1321
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1321
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: John Vines
>             Fix For: 1.5.0
>
>
> We have a table setup that uses some custom iterators. We ran an MR job against it without
issues. We then ran the job immediately after the first one wrapped and 2 of my tservers errored
with ClassNotFoundException, even though it ran just fine before.
> Unfortunately we don't have a stack trace (to see if it was breaking differently in the
VFSClassLoader), nor a convenient way to recreate currently. We're working on reproducing
it in order to get more information.

--
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

Mime
View raw message