You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Ferdy Galema (Closed) (JIRA)" <ji...@apache.org> on 2011/11/16 14:04:51 UTC

[jira] [Closed] (NUTCH-1148) Nutchgora job jar functionalilty is broken: PluginManifestParser cannot load plugins from system classloader.

     [ https://issues.apache.org/jira/browse/NUTCH-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ferdy Galema closed NUTCH-1148.
-------------------------------

    Resolution: Cannot Reproduce

Wow this really boggles my mind: I tried to do a final check with and without patch, but I cannot reproduce the error anymore.

I must have had a different issue back then, which I accidentally repaired, tricking me into thinking changing the classloader fixed it. Apparently it didn't.

Well, that's another way to resolve an issue. :)
                
> Nutchgora job jar functionalilty is broken: PluginManifestParser cannot load plugins from system classloader.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: NUTCH-1148
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1148
>             Project: Nutch
>          Issue Type: Bug
>    Affects Versions: nutchgora
>            Reporter: Ferdy Galema
>            Priority: Critical
>         Attachments: NUTCH-1148-v1.patch
>
>
> This affects running nutchgora using Hadoop it's RunJar mechanism (hadoop jar ...). The mr tasks are perfectly able to load the plugins (please note NUTCH-937). But, when the plugins are loaded from the *job submitter* process itself, loading plugins might fail due to classloading issues. This is caused by the fact that PluginManifestParser does not use the contextClassLoader that is set by RunJar. This classloader contains the plugins folder. At least the FetcherJob is affected by this, because the job submitter uses getFields of Protocol implementations, therefore loading the plugins.
> The current 1.x is not affected because it does not load plugins at any point during the job submission. This might of course change so I propose to 'fix' the issue in the 1.x branch as well.
> The solution is fairly simple, PluginManifestParser should use the contextClassLoader of the current thread instead of using the system classloader. I will attach patch right away. It currently works but it still needs some further testing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira