Patrick, You indicated that you implemented the suggestions in the admin guide - did you by chance log out of the session and create a new session before trying to run maven again? That can sometimes be a sticking point, because some of those changes don't take effect until a new session is created.
If so, can you please provide the output of running "ulimit -a"? Thanks -Mark ---------------------------------------- > Date: Fri, 12 Jun 2015 13:38:44 -0700 > From: [email protected] > To: [email protected] > Subject: RE: mvn fail > > Howdy, > > I now have a VM that I have sudo privileges so I comply with the > administration guide. I made the changes suggested and then followed the > quick start. > > I ran mvn in the nifi directory and got errors. > > The 1st error is: > ... > Running org.apache.nifi.processors.standard.TestReplaceText > Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.112 sec - > in org.apache.nifi.processors.standard.TestReplaceText > Running org.apache.nifi.processors.standard.TestReplaceTextLineByLine > Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.136 sec - > in org.apache.nifi.processors.standard.TestReplaceTextLineByLine > Running org.apache.nifi.processors.standard.TestHandleHttpRequest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.675 sec <<< > FAILURE! - in org.apache.nifi.processors.standard.TestHandleHttpRequest > testRequestAddedToService(org.apache.nifi.processors.standard.TestHandleHttpRequest) > Time elapsed: 6.675 sec <<< FAILURE! > java.lang.AssertionError: Could not invoke methods annotated with > @OnScheduled annotation due to: java.lang.reflect.InvocationTargetException > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:199) > at > org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:182) > at > org.apache.nifi.processors.standard.TestHandleHttpRequest.testRequestAddedToService(TestHandleHttpRequest.java:100) > ... > > Running org.apache.nifi.processors.standard.TestMonitorActivity > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.063 sec - > in org.apache.nifi.processors.standard.TestMonitorActivity > Running org.apache.nifi.processors.standard.TestExecuteStreamCommand > Tests run: 7, Failures: 5, Errors: 1, Skipped: 1, Time elapsed: 2.723 sec <<< > FAILURE! - in org.apache.nifi.processors.standard.TestExecuteStreamCommand > testExecuteIngestAndUpdateWithWorkingDir(org.apache.nifi.processors.standard.TestExecuteStreamCommand) > Time elapsed: 0.115 sec <<< FAILURE! > java.lang.AssertionError: java.lang.OutOfMemoryError: unable to create new > native thread > at > org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:219) > at > org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:182) > at > org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:177) > at > org.apache.nifi.processors.standard.TestExecuteStreamCommand.testExecuteIngestAndUpdateWithWorkingDir(TestExecuteStreamCommand.java:150) > Caused by: java.lang.OutOfMemoryError: unable to create new native thread > at java.lang.Thread.start0(Native Method) > at java.lang.Thread.start(Thread.java:714) > at > org.apache.nifi.processors.standard.ExecuteStreamCommand$StdInWriterCallback$1.process(ExecuteStreamCommand.java:376) > at org.apache.nifi.util.MockProcessSession.write(MockProcessSession.java:593) > at org.apache.nifi.util.MockProcessSession.write(MockProcessSession.java:58) > at > org.apache.nifi.processors.standard.ExecuteStreamCommand$StdInWriterCallback.process(ExecuteStreamCommand.java:357) > at org.apache.nifi.util.MockProcessSession.read(MockProcessSession.java:411) > at > org.apache.nifi.processors.standard.ExecuteStreamCommand.onTrigger(ExecuteStreamCommand.java:292) > at > org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27) > at > org.apache.nifi.util.StandardProcessorTestRunner$RunProcessor.call(StandardProcessorTestRunner.java:269) > at > org.apache.nifi.util.StandardProcessorTestRunner$RunProcessor.call(StandardProcessorTestRunner.java:263) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > ... > > > > I modified the MAVEN_OPTS hopping to at least get rid of the out of mem > error. No luck > > export MAVEN_OPTS="-Xms2048m -Xmx6076m -XX:MaxPermSize=512m" > > > Any thoughts? > > Thank you, > > Patrick Jones > > ---- system info ---------- > > $ java -version > java version "1.7.0_79" > OpenJDK Runtime Environment (IcedTea 2.5.5) (7u79-2.5.5-0ubuntu0.14.04.2) > OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode) > > $ mvn -version > Apache Maven 3.0.5 > Maven home: /usr/share/maven > Java version: 1.7.0_79, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.13.0-48-generic", arch: "amd64", family: "unix" > > $ lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description: Ubuntu 14.04.2 LTS > Release: 14.04 > Codename: trusty > > > From: Aldrin Piri [via Apache NiFi (incubating) Developer List] > [mailto:[email protected]] > Sent: Thursday, June 04, 2015 12:10 PM > To: Jones, Patrick L. > Subject: Re: mvn fail > > All, > > Looks like the reported failures were a bit of a red herring, but provides > some interesting points of consideration for our Quickstart guide. > > Pat, > > After some inspection, it seems that the default settings for both open > files and processes in 12.04 LTS is quite low which lead to the test > failures. It was only while watching over the tests running did I see the > notification about too many open files. I would speculate this is the > problem you are experiencing. > > I was able to resolve the issue by applying the best practices laid out in > the administration guide [1] to my VM running the version of Ubuntu in > question. Please give those settings a go when you have the opportunity > and let us know if that resolves your build issues. > > [1] > http://nifi.incubator.apache.org/docs/nifi-docs/html/administration-guide.html#configuration-best-practices > > > On Wed, Jun 3, 2015 at 5:09 PM, Aldrin Piri <[hidden > email]</user/SendEmail.jtp?type=node&node=1739&i=0>> wrote: > >> All, >> >> I was able to recreate the errors reported. My steps are below. Issue >> NIFI-650 has been created [2]. >> >> ======================================= >> >> Performed an install into a VM, but ran into a bug with the 12.04.5 LTS >> release where apt is effectively broken on a clean install [1]. The >> solution provided seems to work for me in getting apt running from a clean >> install in a VM. >> >> From there, installed JDK 7 (version 7u79 was installed for me) and git. >> Installed Maven 3.0.5 separately as that is the minimum we support (my >> install only had 3.0.4-2 in apt). >> >> Checked out the code and switched to develop. >> Installed parent successfully. >> Installed nifi-nar-maven-plugin successfully. >> Installed nifi as per the quick start. Noted that in the build log there >> were interspersed warnings about thread safety in plugins. One such >> example is below: >> >> [WARNING] ***************************************************************** >> [WARNING] * Your build is requesting parallel execution, but project * >> [WARNING] * contains the following plugin(s) that are not marked as * >> [WARNING] * @threadSafe to support parallel building. * >> [WARNING] * While this /may/ work fine, please look for plugin updates * >> [WARNING] * and/or request plugins be made thread-safe. * >> [WARNING] * If reporting an issue, report it against the plugin in * >> [WARNING] * question, not against maven-core * >> [WARNING] ***************************************************************** >> [WARNING] The following plugins are not marked @threadSafe in >> nifi-standard-services-api-nar: >> [WARNING] org.apache.nifi:nifi-nar-maven-plugin:1.0.1-incubating >> [WARNING] ***************************************************************** >> >> [1] https://github.com/mininet/mininet/issues/438 >> [2] https://issues.apache.org/jira/browse/NIFI-650 >> >> On Wed, Jun 3, 2015 at 3:30 PM, Sean Busbey <[hidden >> email]</user/SendEmail.jtp?type=node&node=1739&i=1>> wrote: >> >>> can you run "mvn -version" and include that too? >>> >>> On Wed, Jun 3, 2015 at 1:56 PM, plj <[hidden >>> email]</user/SendEmail.jtp?type=node&node=1739&i=2>> wrote: >>> >>>> Thanks for the quick reply. See below: >>>> >>>> java version "1.7.0_07" >>>> Java(TM) SE Runtime Environment (build 1.7.0_07-b10) >>>> Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode) >>>> >>>> Distributor ID: Ubuntu >>>> Description: Ubuntu 12.04.5 LTS >>>> Release: 12.04 >>>> Codename: precise >>>> >>>> From: Aldrin Piri [via Apache NiFi (incubating) Developer List] [mailto: >>>> [hidden email]</user/SendEmail.jtp?type=node&node=1739&i=3>] >>>> Sent: Wednesday, June 03, 2015 2:51 PM >>>> To: Jones, Patrick L. >>>> Subject: Re: mvn fail >>>> >>>> Sorry to hear you are having troubles with the process in the quick >>> start >>>> guide. >>>> >>>> Could you please provide some additional details such as Linux >>>> distribution/version and Java version you are running the code against? >>>> >>>> Thanks! >>>> >>>> On Wed, Jun 3, 2015 at 2:17 PM, plj <[hidden >>>> email]</user/SendEmail.jtp?type=node&node=1717&i=0>> wrote: >>>> >>>>> >>>>> >>>>> Howdy, >>>>> >>>>> I'm trying to install NiFi on a Linux VM. I have followed the >>>> Quickstart >>>>> build steps. The last step I cd to nifi and then mvn clean install. >>> Any >>>>> thoughts on why I got the following: >>>>> >>>>> ... >>>>> Running org.apache.nifi.processors.standard.TestExecuteStreamCommand >>>>> Tests run: 5, Failures: 4, Errors: 0, Skipped: 1, Time elapsed: 1.144 >>> sec >>>>> <<< FAILURE! - in org.apache.nifi.processors.standard.TestE >>>>> xecuteStreamCommand >>>>> >>>>> >>>> >>> testExecuteIngestAndUpdateWithWorkingDir(org.apache.nifi.processors.standard.TestExecuteStreamCommand) >>>>> Time elapsed: 0.112 sec <<< >>>>> FAILURE! >>>>> java.lang.AssertionError: null >>>>> at org.junit.Assert.fail(Assert.java:86) >>>>> at org.junit.Assert.assertTrue(Assert.java:41) >>>>> at org.junit.Assert.assertTrue(Assert.java:52) >>>>> at >>>>> >>>>> >>>> >>> org.apache.nifi.processors.standard.TestExecuteStreamCommand.testExecuteIngestAndUpdateWithWorkingDir(TestExecuteStreamCommand.java:156) >>>>> >>>>> >>>>> >>>> >>> testExecuteJarWithBadPath(org.apache.nifi.processors.standard.TestExecuteStreamCommand) >>>>> Time elapsed: 0.006 sec <<< FAILURE! >>>>> org.junit.ComparisonFailure: expected:<[Error: Unable to access >>> jarfile]> >>>>> but was:<[Unable to access jarfile /home/]> >>>>> at org.junit.Assert.assertEquals(Assert.java:115) >>>>> at org.junit.Assert.assertEquals(Assert.java:144) >>>>> at >>>>> >>>>> >>>> >>> org.apache.nifi.processors.standard.TestExecuteStreamCommand.testExecuteJarWithBadPath(TestExecuteStreamCommand.java:103) >>>>> >>>>> >>>>> >>>> >>> testExecuteJar(org.apache.nifi.processors.standard.TestExecuteStreamCommand) >>>>> Time elapsed: 0.1 sec <<< FAILURE! >>>>> java.lang.AssertionError: null >>>>> at org.junit.Assert.fail(Assert.java:86) >>>>> at org.junit.Assert.assertTrue(Assert.java:41) >>>>> at org.junit.Assert.assertTrue(Assert.java:52) >>>>> at >>>>> >>>>> >>>> >>> org.apache.nifi.processors.standard.TestExecuteStreamCommand.testExecuteJar(TestExecuteStreamCommand.java:73) >>>>> >>>>> >>>>> >>>> >>> testExecuteIngestAndUpdate(org.apache.nifi.processors.standard.TestExecuteStreamCommand) >>>>> Time elapsed: 0.925 sec <<< FAILURE! >>>>> java.lang.AssertionError: null >>>>> at org.junit.Assert.fail(Assert.java:86) >>>>> at org.junit.Assert.assertTrue(Assert.java:41) >>>>> at org.junit.Assert.assertTrue(Assert.java:52) >>>>> at >>>>> >>>>> >>>> >>> org.apache.nifi.processors.standard.TestExecuteStreamCommand.testExecuteIngestAndUpdate(TestExecuteStreamCommand.java:134) >>>>> >>>>> ... >>>>> >>>>> [INFO] BUILD FAILURE >>>>> [INFO] >>>>> >>> ------------------------------------------------------------------------ >>>>> [INFO] Total time: 7:46.419s >>>>> [INFO] Finished at: Wed Jun 03 14:02:07 EDT 2015 >>>>> [INFO] Final Memory: 141M/1477M >>>>> [INFO] >>>>> >>> ------------------------------------------------------------------------ >>>>> [ERROR] Failed to execute goal >>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test >>> (default-test) >>>> on >>>>> project nifi-standard-processors: There are test failures. >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> >>>> >>> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/mvn-fail-tp1716.html >>>>> Sent from the Apache NiFi (incubating) Developer List mailing list >>>> archive >>>>> at Nabble.com. >>>>> >>>> >>>> ________________________________ >>>> If you reply to this email, your message will be added to the discussion >>>> below: >>>> >>>> >>> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/mvn-fail-tp1716p1717.html >>>> To unsubscribe from mvn fail, click here< >>>> >>>>>. >>>> NAML< >>>> >>> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml >>>>> >>>> >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> >>> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/mvn-fail-tp1716p1718.html >>>> Sent from the Apache NiFi (incubating) Developer List mailing list >>> archive >>>> at Nabble.com. >>>> >>> >>> >>> >>> -- >>> Sean >>> >> >> > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/mvn-fail-tp1716p1739.html > To unsubscribe from mvn fail, click > here<http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1716&code=cGxqQG1pdHJlLm9yZ3wxNzE2fDU1MTMzODA1>. > NAML<http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > > > > -- > View this message in context: > http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/mvn-fail-tp1716p1878.html > Sent from the Apache NiFi (incubating) Developer List mailing list archive at > Nabble.com.
