nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Gilman <matt.c.gil...@gmail.com>
Subject Re: UI can take a very long time to become available
Date Fri, 24 Jun 2016 11:26:17 GMT
Hi,

Thanks for checking out Apache NiFi! In order to prevent components from
automatically resuming after startup you can disable this flag in your
nifi.properties:

nifi.flowcontroller.autoResumeState=true

Matt

On Fri, Jun 24, 2016 at 4:20 AM, ddewaele <ddewaele@gmail.com> wrote:

> I've  added a gist
> <https://gist.github.com/ddewaele/f84c223fff2c18af4efe3b7fabcab946>   to
> show you some logging threaddumps of when the issue occurs. In this
> particular case I was unable to bring up Nifi ....
>
> I had to kill my mqtt broker so that the ConsumeMQTT processor wouldn't be
> picking up any new messages.
> Then I was able to start Nifi and enter the UI. However, I was unable to
> stop the ConsumeMQTT processor. (spinning refresh wheel of death).
>
> There is some activity in the logs but no msgs are processed and ui / api
> is
> unresponsive.
>
> nifi.sh dump also doesn't work due to a socket timeout (probably tries to
> contact the api).
>
>
>
>
>
>
> --
> View this message in context:
> http://apache-nifi-developer-list.39713.n7.nabble.com/UI-can-take-a-very-long-time-to-become-available-tp12201p12204.html
> Sent from the Apache NiFi Developer List mailing list archive at
> Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message