Joe, I've noticed some slow UI start-up with master earlier during the week as well. In my case the initialisation would hang around
"No Spring WebApplicationInitializer types detected on classpath" But I haven't had time to be able to troubleshoot/isolate the issue On Sun, Jun 26, 2016 at 10:48 AM, Joe Witt <[email protected]> wrote: > Ok that was definitely good to see (the video). I tried a similar > setup and could not recreate it. > > Let's see if we can get the perspective of a few other folks. > > If you can get a thread dump at all during the spinning that would be > really helpful. > > Thanks > Joe > > On Sat, Jun 25, 2016 at 4:28 PM, ddewaele <[email protected]> wrote: > > Here you can see the 2 crash scenarios mentioned in the previous post : > > https://dl.dropboxusercontent.com/u/13246619/nifi-crash/NifiCrash.mp4 > > > > - First one is deleting a processor with a non-empty queue attached > > - Second one is deleting a processor with a destination that is running > > > > both actions fail (error msgs in a popup). However, any action in the UI > > will now cause the flow to freeze. > > > > Hope this helps.... > > > > > > > > > > > > -- > > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/UI-can-take-a-very-long-time-to-become-available-tp12201p12269.html > > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
