[jira] [Created] (NIFI-6475) NoClassDefFoundError when running Atlas integration from Docker container

["Justin Flowers (JIRA)" <ji...@apache.org>]

Justin Flowers created NIFI-6475:
------------------------------------

             Summary: NoClassDefFoundError when running Atlas integration from Docker container
                 Key: NIFI-6475
                 URL: https://issues.apache.org/jira/browse/NIFI-6475
             Project: Apache NiFi
          Issue Type: Bug
          Components: Extensions
    Affects Versions: 1.8.0
            Reporter: Justin Flowers


Running the Atlas integration in a Nifi Docker container throws this exception after configuring the Reporting Task and staring it:
{code:java}
2019-07-23 13:00:05,753 ERROR [Timer-Driven Process Thread-3] o.a.n.a.reporting.ReportLineageToAtlas ReportLineageToAtlas[id=1f01a738-016c-1000-ffff-ffffada9f376] Failed to invoke @OnScheduled method due to java.lang.NoClassDefFoundError: Could not initialize class org.apache.nifi.atlas.hook.NiFiAtlasHook: {}
java.lang.NoClassDefFoundError: Could not initialize class org.apache.nifi.atlas.hook.NiFiAtlasHook
        at org.apache.nifi.atlas.reporting.ReportLineageToAtlas.initLineageStrategy(ReportLineageToAtlas.java:453)
        at org.apache.nifi.atlas.reporting.ReportLineageToAtlas.setup(ReportLineageToAtlas.java:448)
        at sun.reflect.GeneratedMethodAccessor366.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:142)
        at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:130)
        at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:75)
        at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:52)
        at org.apache.nifi.controller.scheduling.StandardProcessScheduler$2.run(StandardProcessScheduler.java:214)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748){code}
I tried running on empty standalone Docker deploys and on empty standalone VM filesystem deploys, but I only see this issue running from a container.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)