accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (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 22:02:50 GMT

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

Josh Elser commented on ACCUMULO-2115:
--------------------------------------

bq. I have copied jars out to lib/ext on numerous occasions without seeing this issue. It
could be a race condition or something added in 1.4.4

Likewise -- I know I've seen my share of weirdness with the 1.4 reloading of classes, but
this one doesn't ring a bell to me. If I use 1.4, it's mostly been 1.4.5-SNAPSHOT, but I can't
say I've run into things recently. Either way, more details would be great if you have them,
[~ivan.bella].

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

Mime
View raw message