[
https://issues.apache.org/jira/browse/ACCUMULO-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888929#comment-13888929
]
Ivan Bella commented on ACCUMULO-2115:
--------------------------------------
This has been seen again. In this case a new jar was added that depended on
several of the other jars already in the lib/ext directory. Attempting to use
the classes in the new jar resulted in class not found exceptions. After
waiting overnight the situation persisted. Touching the new jar helped quite a
bit after that but it still took some time before the older class loader
instance was removed. Again this is only a problem when we have consistent
activity on the system which I presume does not allow the previous class loader
instance to go away. We hope to upgrade in the near future which would make
this issue OBE for us so I am not raising the priority.
> 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)
