[UIMA-4740] DUCC Job Driver (JD) neglects to set current thread classloader

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0-Ducc
• Component/s: DUCC
• Assignee: Lou DeGenaro
• Reporter: Lou DeGenaro
• Created: 13/Jan/16 14:38
• Updated: 14/Jan/16 16:04
• Resolved: 14/Jan/16 16:04

Description

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.