Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 29 Jul 2015 12:19:04 +0000 (UTC)
From: "Dave Marion (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12686799.1388436561000.318356.1438172344659@Atlassian.JIRA>
In-Reply-To: <JIRA.12686799.1388436561000@Atlassian.JIRA>
References: <JIRA.12686799.1388436561000@Atlassian.JIRA>
 <JIRA.12686799.1388436561454@arcas>
Subject: [jira] [Commented] (ACCUMULO-2115) class loader issues when
 replacing jar that is actively being used
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dave Marion commented on ACCUMULO-2115:
---------------------------------------

Should try this with commons-vfs 2.1 snapshot and see if that fixes the problem

> class loader issues when replacing jar that is actively being used
> ------------------------------------------------------------------
>
>                 Key: ACCUMULO-2115
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2115
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.4.4
>            Reporter: Ivan Bella
>            Priority: Minor
>              Labels: class_loader
>
> When replacing a jar in the lib/ext directory while active iterators are using the previous jar will result is many class loader issues.  New iterators started up may also show class loader issues.  This will probably persist until the previously active iterators complete and release the previous ClassLoader instance, but that is merely a guess.


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