accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1321) Dynamic Classloader lost jars
Date Tue, 30 Apr 2013 19:20:16 GMT


John Vines commented on ACCUMULO-1321:

So, I tested it and extended VFSClassloader to have a finalize() method which just calls close
(and had PostDelegatingVFSClassloader extend that instead), and it seems to deal with the
file issue. I'm not totally comfortable with relying on finalize(), but it seems to work.
It will still create files with a random identifier incorporated into the name though, so
the possibility of collision is still there, but mitigated since they get cleaned up in a
few minutes (depending on java VM activity of course).
> Dynamic Classloader lost jars
> -----------------------------
>                 Key: ACCUMULO-1321
>                 URL:
>             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:

View raw message