Re: NiFi 1.1.0 stuck starting, no errors

2017-01-27 Thread Joe Witt 
...ok so we definitely want to figure out why there was another nifi
process still lingering around in the background.  Do you have any
idea why that might have been? Perhaps the startup script has some
corner cases not well covered just yet.

On Fri, Jan 27, 2017 at 12:39 PM, Peter Wicks (pwicks)
<pwi...@micron.com> wrote:
> Restarting the box fixed it.
>
>
>
> From: Bryan Rosander [mailto:brosan...@apache.org]
> Sent: Friday, January 27, 2017 8:51 AM
> To: users@nifi.apache.org
> Subject: Re: NiFi 1.1.0 stuck starting, no errors
>
>
>
> Hey Peter,
>
>
>
> The relevant section of the thread dump is below.  It looks like startup is
> blocking while trying to get a file lock for the flowfile repository.  Are
> you positive that there is only one instance of NiFi running with the
> repository directory you've configured?  If so, maybe something failed to
> release the lock in which case a reboot might be worth a try.
>
>
>
> Thanks,
>
> Bryan
>
>
>
> "main" #1 prio=5 os_prio=0 tid=0x7f8da000d000 nid=0xcd68 runnable
> [0x7f8da6daa000]
>
>java.lang.Thread.State: RUNNABLE
>
> at sun.nio.ch.FileDispatcherImpl.lock0(Native Method)
>
> at sun.nio.ch.FileDispatcherImpl.lock(FileDispatcherImpl.java:90)
>
> at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:1073)
>
> at java.nio.channels.FileChannel.lock(FileChannel.java:1053)
>
> at
> org.wali.MinimalLockingWriteAheadLog.(MinimalLockingWriteAheadLog.java:187)
>
> at
> org.wali.MinimalLockingWriteAheadLog.(MinimalLockingWriteAheadLog.java:112)
>
> at
> org.apache.nifi.controller.repository.WriteAheadFlowFileRepository.initialize(WriteAheadFlowFileRepository.java:148)
>
> at
> org.apache.nifi.controller.FlowController.createFlowFileRepository(FlowController.java:638)
>
> - locked <0x0006bfc17cc0> (a
> org.apache.nifi.controller.repository.WriteAheadFlowFileRepository)
>
> at
> org.apache.nifi.controller.FlowController.(FlowController.java:447)
>
> at
> org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:375)
>
> at
> org.apache.nifi.spring.FlowControllerFactoryBean.getObject(FlowControllerFactoryBean.java:74)
>
> at
> org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168)
>
> at
> org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:103)
>
> - locked <0x00067a34fbf8> (a
> java.util.concurrent.ConcurrentHashMap)
>
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1585)
>
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:317)
>
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
>
> at
> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1060)
>
> at
> org.apache.nifi.spring.StandardFlowServiceFactoryBean.getObject(StandardFlowServiceFactoryBean.java:48)
>
> at
> org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168)
>
> at
> org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:103)
>
> - locked <0x00067a34fbf8> (a
> java.util.concurrent.ConcurrentHashMap)
>
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1585)
>
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:317)
>
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
>
> at
> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1060)
>
> at
> org.apache.nifi.web.contextlistener.ApplicationStartupContextListener.contextInitialized(ApplicationStartupContextListener.java:53)
>
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:837)
>
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:533)
>
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler

Re: NiFi 1.1.0 stuck starting, no errors

2017-01-27 Thread Bryan Rosander 
Hey Peter,

Weighing in at 200MB means it is likely a heap dump (all working memory).
A thread dump should be much smaller.  If using jcmd, please try
Thread.print as the command.  Another alternative would be to use jstack
[PID].

Thanks,
Bryan

On Fri, Jan 27, 2017 at 9:24 AM, Peter Wicks (pwicks) <pwi...@micron.com>
wrote:

> It clocked in at around 200MB’s… https://drive.google.com/file/d/
> 0B4yjbe5sOeAuRXAxT3Z6anRRN1k/view?usp=sharing
>
>
>
>
>
> *From:* Andy LoPresto [mailto:alopre...@apache.org]
> *Sent:* Thursday, January 26, 2017 3:06 PM
> *To:* users@nifi.apache.org
> *Subject:* Re: NiFi 1.1.0 stuck starting, no errors
>
>
>
> Hi Peter,
>
> Can you provide a thread dump of the process? You should be able to do
> this via the jcmd tool [1].
>
> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/
> tooldescr006.html#BABEHABG <https://docs.oracle.com/
> javase/8/docs/technotes/guides/troubleshoot/tooldescr006.html#BABEHABG>
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> > On Jan 26, 2017, at 12:42 PM, Peter Wicks (pwicks) <pwi...@micron.com>
> wrote:
> >
> > I’m looking for help in troubleshooting my NiFi 1.1.0 install.  It’s
> been running stably for some time, but I restarted it this morning when I
> deployed an updated custom NAR. Now it gets stuck at startup, see logs at
> the end.
>
> > There are no error messages, and the processes don’t die. The process
> just seems to be hanging waiting for something.
> >
> > · My first thought was to try rolling back the modified nar, and
> even just removing the nar all together since it was custom.  Neither of
> these made any difference.
>
> > · I also tried deleting the “work” folder, which has fixed nar
> versioning issues for me in the past (not really related, but was worth a
> shot). This made no difference.
>
> > · NiFi is set to start with java.arg.2=-Xms4G and
> java.arg.3=-Xmx8G, 22GB’s of free RAM are available on the system (out of
> some 60GB’s total).
>
> > · I’ve checked running processes, and when I stop NiFi no rouge
> instances are left running.
> > · Since NiFi gets stuck right around the JettyServer step I
> checked to see if any processes were using port 8443. No other processes
> are using this port.
>
> > · I thought maybe a key file was being locked, but with NiFi off
> `lsof | grep nifi` returns no locked files.
> >
> > Nifi-app Log:
> > 2017-01-26 20:23:43,359 INFO [main] org.eclipse.jetty.util.log Logging
> initialized @90357ms
> > 2017-01-26 20:23:43,418 INFO [main] org.apache.nifi.web.server.JettyServer
> Configuring Jetty for HTTPs on port: 8443
> > 2017-01-26 20:23:43,691 INFO [main] org.apache.nifi.web.server.JettyServer
> Loading WAR: /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-media-nar-
> 1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-image-viewer-1.1.0.war
> with context path set to /nifi-image-viewer-1.1.0
>
> > 2017-01-26 20:23:43,702 INFO [main] org.apache.nifi.web.server.JettyServer
> Loading WAR: /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-update-
> attribute-nar-1.1.0.nar-unpacked/META-INF/bundled-
> dependencies/nifi-update-attribute-ui-1.1.0.war with context path set to
> /nifi-update-attribute-ui-1.1.0
>
> > 2017-01-26 20:23:43,703 INFO [main] org.apache.nifi.web.server.JettyServer
> Loading UI extension [ProcessorConfiguration, /nifi-update-attribute-ui-1.1.0]
> for [org.apache.nifi.processors.attributes.UpdateAttribute]
>
> > 2017-01-26 20:23:43,713 INFO [main] org.apache.nifi.web.server.JettyServer
> Loading WAR: /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-standard-
> nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-
> standard-content-viewer-1.1.0.war with context path set to
> /nifi-standard-content-viewer-1.1.0
>
> > 2017-01-26 20:23:43,723 INFO [main] org.apache.nifi.web.server.JettyServer
> Loading WAR: /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-standard-
> nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-
> jolt-transform-json-ui-1.1.0.war with context path set to
> /nifi-jolt-transform-json-ui-1.1.0
>
> > 2017-01-26 20:23:43,724 INFO [main] org.apache.nifi.web.server.JettyServer
> Loading UI extension [ProcessorConfiguration, 
> /nifi-jolt-transform-json-ui-1.1.0]
> for [org.apache.nifi.processors.standard.JoltTransformJSON]
>
> > 2017-01-26 20:23:43,729 INFO [main] org.apache.nifi.web.server.JettyServer
> Loading WAR: /data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-
> nar-1.1.0.nar-unpacked/META-INF/bu

RE: NiFi 1.1.0 stuck starting, no errors

2017-01-27 Thread Peter Wicks (pwicks) 
It clocked in at around 200MB’s… 
https://drive.google.com/file/d/0B4yjbe5sOeAuRXAxT3Z6anRRN1k/view?usp=sharing


From: Andy LoPresto [mailto:alopre...@apache.org]
Sent: Thursday, January 26, 2017 3:06 PM
To: users@nifi.apache.org
Subject: Re: NiFi 1.1.0 stuck starting, no errors


Hi Peter,

Can you provide a thread dump of the process? You should be able to do this via 
the jcmd tool [1].

[1] 
https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/tooldescr006.html#BABEHABG
 
<https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/tooldescr006.html#BABEHABG>

Andy LoPresto
alopre...@apache.org<mailto:alopre...@apache.org>
alopresto.apa...@gmail.com<mailto:alopresto.apa...@gmail.com>
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Jan 26, 2017, at 12:42 PM, Peter Wicks (pwicks) 
> <pwi...@micron.com<mailto:pwi...@micron.com>> wrote:
>
> I’m looking for help in troubleshooting my NiFi 1.1.0 install.  It’s been 
> running stably for some time, but I restarted it this morning when I deployed 
> an updated custom NAR. Now it gets stuck at startup, see logs at the end.

> There are no error messages, and the processes don’t die. The process just 
> seems to be hanging waiting for something.
>
> · My first thought was to try rolling back the modified nar, and even 
> just removing the nar all together since it was custom.  Neither of these 
> made any difference.

> · I also tried deleting the “work” folder, which has fixed nar 
> versioning issues for me in the past (not really related, but was worth a 
> shot). This made no difference.

> · NiFi is set to start with java.arg.2=-Xms4G and java.arg.3=-Xmx8G, 
> 22GB’s of free RAM are available on the system (out of some 60GB’s total).

> · I’ve checked running processes, and when I stop NiFi no rouge 
> instances are left running.
> · Since NiFi gets stuck right around the JettyServer step I checked 
> to see if any processes were using port 8443. No other processes are using 
> this port.

> · I thought maybe a key file was being locked, but with NiFi off 
> `lsof | grep nifi` returns no locked files.
>
> Nifi-app Log:
> 2017-01-26 20:23:43,359 INFO [main] org.eclipse.jetty.util.log Logging 
> initialized @90357ms
> 2017-01-26 20:23:43,418 INFO [main] org.apache.nifi.web.server.JettyServer 
> Configuring Jetty for HTTPs on port: 8443
> 2017-01-26 20:23:43,691 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-media-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-image-viewer-1.1.0.war
>  with context path set to /nifi-image-viewer-1.1.0

> 2017-01-26 20:23:43,702 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-update-attribute-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-update-attribute-ui-1.1.0.war
>  with context path set to /nifi-update-attribute-ui-1.1.0

> 2017-01-26 20:23:43,703 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading UI extension [ProcessorConfiguration, 
> /nifi-update-attribute-ui-1.1.0] for 
> [org.apache.nifi.processors.attributes.UpdateAttribute]

> 2017-01-26 20:23:43,713 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-standard-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-standard-content-viewer-1.1.0.war
>  with context path set to /nifi-standard-content-viewer-1.1.0

> 2017-01-26 20:23:43,723 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-standard-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-jolt-transform-json-ui-1.1.0.war
>  with context path set to /nifi-jolt-transform-json-ui-1.1.0

> 2017-01-26 20:23:43,724 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading UI extension [ProcessorConfiguration, 
> /nifi-jolt-transform-json-ui-1.1.0] for 
> [org.apache.nifi.processors.standard.JoltTransformJSON]

> 2017-01-26 20:23:43,729 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-ui-1.1.0.war
>  with context path set to /nifi

> 2017-01-26 20:23:43,733 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-api-1.1.0.war
>  with context path set to /nifi-api

> 2017-01-26 20:23:43,735 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/framework/nif

Re: NiFi 1.1.0 stuck starting, no errors

2017-01-26 Thread Andy LoPresto 
Hi Peter,

Can you provide a thread dump of the process? You should be able to do this via 
the jcmd tool [1].

[1] 
https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/tooldescr006.html#BABEHABG
 


Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Jan 26, 2017, at 12:42 PM, Peter Wicks (pwicks)  wrote:
> 
> I’m looking for help in troubleshooting my NiFi 1.1.0 install.  It’s been 
> running stably for some time, but I restarted it this morning when I deployed 
> an updated custom NAR. Now it gets stuck at startup, see logs at the end.
> There are no error messages, and the processes don’t die. The process just 
> seems to be hanging waiting for something.
> 
> · My first thought was to try rolling back the modified nar, and even 
> just removing the nar all together since it was custom.  Neither of these 
> made any difference.
> · I also tried deleting the “work” folder, which has fixed nar 
> versioning issues for me in the past (not really related, but was worth a 
> shot). This made no difference.
> · NiFi is set to start with java.arg.2=-Xms4G and java.arg.3=-Xmx8G, 
> 22GB’s of free RAM are available on the system (out of some 60GB’s total).
> · I’ve checked running processes, and when I stop NiFi no rouge 
> instances are left running.
> · Since NiFi gets stuck right around the JettyServer step I checked 
> to see if any processes were using port 8443. No other processes are using 
> this port.
> · I thought maybe a key file was being locked, but with NiFi off 
> `lsof | grep nifi` returns no locked files.
> 
> Nifi-app Log:
> 2017-01-26 20:23:43,359 INFO [main] org.eclipse.jetty.util.log Logging 
> initialized @90357ms
> 2017-01-26 20:23:43,418 INFO [main] org.apache.nifi.web.server.JettyServer 
> Configuring Jetty for HTTPs on port: 8443
> 2017-01-26 20:23:43,691 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-media-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-image-viewer-1.1.0.war
>  with context path set to /nifi-image-viewer-1.1.0
> 2017-01-26 20:23:43,702 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-update-attribute-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-update-attribute-ui-1.1.0.war
>  with context path set to /nifi-update-attribute-ui-1.1.0
> 2017-01-26 20:23:43,703 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading UI extension [ProcessorConfiguration, 
> /nifi-update-attribute-ui-1.1.0] for 
> [org.apache.nifi.processors.attributes.UpdateAttribute]
> 2017-01-26 20:23:43,713 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-standard-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-standard-content-viewer-1.1.0.war
>  with context path set to /nifi-standard-content-viewer-1.1.0
> 2017-01-26 20:23:43,723 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-standard-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-jolt-transform-json-ui-1.1.0.war
>  with context path set to /nifi-jolt-transform-json-ui-1.1.0
> 2017-01-26 20:23:43,724 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading UI extension [ProcessorConfiguration, 
> /nifi-jolt-transform-json-ui-1.1.0] for 
> [org.apache.nifi.processors.standard.JoltTransformJSON]
> 2017-01-26 20:23:43,729 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-ui-1.1.0.war
>  with context path set to /nifi
> 2017-01-26 20:23:43,733 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-api-1.1.0.war
>  with context path set to /nifi-api
> 2017-01-26 20:23:43,735 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-content-viewer-1.1.0.war
>  with context path set to /nifi-content-viewer
> 2017-01-26 20:23:43,738 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading WAR: 
> /data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-docs-1.1.0.war
>  with context path set to /nifi-docs
> 2017-01-26 20:23:43,753 INFO [main] org.apache.nifi.web.server.JettyServer 
> Loading documents web app with context path set to /nifi-docs
> 2017-01-26 20:23:43,761 INFO [main]

NiFi 1.1.0 stuck starting, no errors

2017-01-26 Thread Peter Wicks (pwicks) 
I'm looking for help in troubleshooting my NiFi 1.1.0 install.  It's been 
running stably for some time, but I restarted it this morning when I deployed 
an updated custom NAR. Now it gets stuck at startup, see logs at the end.
There are no error messages, and the processes don't die. The process just 
seems to be hanging waiting for something.


* My first thought was to try rolling back the modified nar, and even 
just removing the nar all together since it was custom.  Neither of these made 
any difference.

* I also tried deleting the "work" folder, which has fixed nar 
versioning issues for me in the past (not really related, but was worth a 
shot). This made no difference.

* NiFi is set to start with java.arg.2=-Xms4G and java.arg.3=-Xmx8G, 
22GB's of free RAM are available on the system (out of some 60GB's total).

* I've checked running processes, and when I stop NiFi no rouge 
instances are left running.

* Since NiFi gets stuck right around the JettyServer step I checked to 
see if any processes were using port 8443. No other processes are using this 
port.

* I thought maybe a key file was being locked, but with NiFi off `lsof 
| grep nifi` returns no locked files.

Nifi-app Log:
2017-01-26 20:23:43,359 INFO [main] org.eclipse.jetty.util.log Logging 
initialized @90357ms
2017-01-26 20:23:43,418 INFO [main] org.apache.nifi.web.server.JettyServer 
Configuring Jetty for HTTPs on port: 8443
2017-01-26 20:23:43,691 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading WAR: 
/data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-media-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-image-viewer-1.1.0.war
 with context path set to /nifi-image-viewer-1.1.0
2017-01-26 20:23:43,702 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading WAR: 
/data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-update-attribute-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-update-attribute-ui-1.1.0.war
 with context path set to /nifi-update-attribute-ui-1.1.0
2017-01-26 20:23:43,703 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading UI extension [ProcessorConfiguration, /nifi-update-attribute-ui-1.1.0] 
for [org.apache.nifi.processors.attributes.UpdateAttribute]
2017-01-26 20:23:43,713 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading WAR: 
/data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-standard-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-standard-content-viewer-1.1.0.war
 with context path set to /nifi-standard-content-viewer-1.1.0
2017-01-26 20:23:43,723 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading WAR: 
/data/nifi/nifi-1.1.0/./work/nar/extensions/nifi-standard-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-jolt-transform-json-ui-1.1.0.war
 with context path set to /nifi-jolt-transform-json-ui-1.1.0
2017-01-26 20:23:43,724 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading UI extension [ProcessorConfiguration, 
/nifi-jolt-transform-json-ui-1.1.0] for 
[org.apache.nifi.processors.standard.JoltTransformJSON]
2017-01-26 20:23:43,729 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading WAR: 
/data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-ui-1.1.0.war
 with context path set to /nifi
2017-01-26 20:23:43,733 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading WAR: 
/data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-api-1.1.0.war
 with context path set to /nifi-api
2017-01-26 20:23:43,735 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading WAR: 
/data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-content-viewer-1.1.0.war
 with context path set to /nifi-content-viewer
2017-01-26 20:23:43,738 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading WAR: 
/data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-docs-1.1.0.war
 with context path set to /nifi-docs
2017-01-26 20:23:43,753 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading documents web app with context path set to /nifi-docs
2017-01-26 20:23:43,761 INFO [main] org.apache.nifi.web.server.JettyServer 
Loading WAR: 
/data/nifi/nifi-1.1.0/./work/nar/framework/nifi-framework-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-web-error-1.1.0.war
 with context path set to /
2017-01-26 20:23:43,804 INFO [main] org.eclipse.jetty.server.Server 
jetty-9.3.9.v20160517
2017-01-26 20:23:44,748 INFO [main] o.e.jetty.server.handler.ContextHandler 
Started 
o.e.j.w.WebAppContext@4b511e61{/nifi-image-viewer-1.1.0,file:///data/nifi/nifi-1.1.0/work/jetty/nifi-image-viewer-1.1.0.war/webapp/,AVAILABLE}{./work/nar/extensions/nifi-media-nar-1.1.0.nar-unpacked/META-INF/bundled-dependencies/nifi-image-viewer-1.1.0.war}
2017-01-26 20:23:46,566