Ok, thanks Bryan On Fri, May 12, 2017 at 8:37 AM, Bryan Bende <bbe...@gmail.com> wrote:
> Frank, > > This means there is a stuck thread and there is no way to kill it through > the UI. > > Before restarting the server you may want to take a thread dump and find > out why it was stuck like this. > > You can run bin/nifi.sh dump and the thread dump will print to > nifi-boostrap.log. > > -Bryan > > > On Fri, May 12, 2017 at 11:21 AM, Frank Maritato < > frank.marit...@lootcrate.com> wrote: > >> Hi, >> >> I have a custom processor that appears to be stopped but claims to be >> running a couple of threads? Is there any way to force kill this without >> restarting the server? It's been in this state for a long time. I'm running >> nifi 1.1.1. >> >> [image: Inline image 1] >> >> -- >> Frank Maritato >> Data Architect >> > > -- Frank Maritato Data Architect
