[
https://issues.apache.org/jira/browse/UIMA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lou DeGenaro resolved UIMA-4740.
--------------------------------
Resolution: Fixed
Code is tested with 4.job (job with errors) and delivered.
> DUCC Job Driver (JD) neglects to set current thread classloader
> ---------------------------------------------------------------
>
> Key: UIMA-4740
> URL: https://issues.apache.org/jira/browse/UIMA-4740
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Fix For: 2.1.0-Ducc
>
>
> From Burn:
> I think the problem is that when the DUCC JobDriver runs the user's
> Collection Reader code using the user's classpath it does not set the
> thread's context class loader. I suspect that the code you're calling is
> using the thread's classloader to load names.txt.
> A work-around (until the next release) is for you to set it in your CR to
> be the same as the one that loaded your CR before calling the code that
> loads names.txt, e.g.
> Thread.currentThread().setContextClassLoader(this.getClass().getClassLoader());
> Note that if any user code uses the system classloader it may fail since
> that uses the classpath that started the JVM which will be the DUCC
> classpath.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
