Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 30 Apr 2013 02:40:16 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12643281.1366305564400.245945.1367289616561@arcas>
In-Reply-To: <JIRA.12643281.1366305564400@arcas>
References: <JIRA.12643281.1366305564400@arcas>
Subject: [jira] [Commented] (ACCUMULO-1321) Dynamic Classloader lost jars
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on ACCUMULO-1321:
----------------------------------

Integrated in Accumulo-1.5-Hadoop-2.0 #93 (See [https://builds.apache.org/job/Accumulo-1.5-Hadoop-2.0/93/])
    ACCUMULO-1321 - accidently commit a change to reloader time (Revision 1477404)
ACCUMULO-1321 - temporary fix. This will create a new vfs classloader in place, but it leaves cruft (Revision 1477380)

     Result = SUCCESS
vines : 
Files : 
* /accumulo/branches/1.5/start/src/main/java/org/apache/accumulo/start/classloader/vfs/AccumuloReloadingVFSClassLoader.java

vines : 
Files : 
* /accumulo/branches/1.5/start/src/main/java/org/apache/accumulo/start/classloader/vfs/AccumuloReloadingVFSClassLoader.java
* /accumulo/branches/1.5/start/src/main/java/org/apache/accumulo/start/classloader/vfs/AccumuloVFSClassLoader.java

                
> Dynamic Classloader lost jars
> -----------------------------
>
>                 Key: ACCUMULO-1321
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1321
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: John Vines
>            Assignee: Keith Turner
>            Priority: Blocker
>             Fix For: 1.5.0
>
>         Attachments: ACCUMULO-1321.patch
>
>
> 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