accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2115) class loader issues when replacing jar that is actively being used
Date Mon, 30 Dec 2013 21:03:50 GMT

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

John Vines commented on ACCUMULO-2115:
--------------------------------------

There were classloader behavior changes between 1.4.4 and 1.5.0. So it may not affect the
1.5.0 and 1.6.0. Specifically, now the classloaders don't get changed, but the classloader
gets replaced, so the old threads should have the old classloader bu thte new ones should
have the new one.

> 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, 1.5.0
>            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.1.5#6160)

Mime
View raw message