Scott In your custom NAR are you extending some other processor/component such as one found in standard processors? You'll really need to break that chain and not pull in the same components.
Can you share the actual error being provided at startup/ Thanks joe On Wed, Jul 5, 2017 at 11:53 AM, Scott Wagner <[email protected]> wrote: > Hey all, > > I have been running on NiFi 1.1.1 for a while, and just started working > on migrating to 1.3.0. However, when I tried starting up, I was getting > unhandled exceptions during startup of Jetty. I have traced this down to > something being wrong with a custom NAR file that we built for 1.1.1. > > The problem is when BundleUtils.findBundleForType is being called, it is > finding 2 bundles for every internal NiFi processor class - the correct NAR > that it comes with in 1.3.0, and my custom NAR file as well. I'm sure that > I have done something wrong in the packaging for my custom NAR file, but I > don't know what it could be. It was originally built from the NiFi NAR > archetype late last year. > > If anyone can point in me in the direction of what I'm doing wrong, I > would greatly appreciate it. I'm not a maven/packaging expert by any means > so no advice is too basic. > > Thanks! > > - Scott
