Do you get a bunch of other INFO-level output from `backtype.storm.daemon.executor` prior to the exception? If you do, that means everything is running for 10s properly, and the exception is thrown at the very end when the cluster is shut down. There's a recent Stack Overflow post that mentions this same exception <https://stackoverflow.com/questions/26568767/storm-starter-example-topologies-crash> .
One possible workaround is to remove the call to `cluster.shutdown()` and kill the java process manually when you want to stop running the local cluster. On Mon, Feb 9, 2015 at 5:30 PM, Jon Gregg <[email protected]> wrote: > OK Mike's suggestion seemed to work, but on the very next line in the > tutorial I ran mvn compile exec:java > -Dstorm.topology=storm.starter.WordCountTopology from storm-starter and > got his error: > > > [ERROR] Failed to execute goal > org.codehaus.mojo:exec-maven-plugin:1.2.1:java (d > efault-cli) on project storm-starter: An exception occured while executing > the J > ava class. instance must be started before calling this method -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e swit > ch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please rea > d the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE > xception > > > I also tried with quotes around the final argument (I'm using Windows) and > got the following: > > [ERROR] Failed to execute goal > org.codehaus.mojo:exec-maven-plugin:1.2.1:java (d > efault-cli) on project storm-starter: An exception occured while executing > the J > ava class. java.lang.InterruptedException -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e swit > ch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please rea > d the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE > xception > > > On Mon, Feb 9, 2015 at 7:30 PM, Andrew Xor <[email protected]> > wrote: > >> No, this is actually one of the most common pitfalls (and subsequently >> question) that we see here; you have to actually go to the pom.xml that is >> located in storm-starter folder and change the dependency scope of >> storm-core (which is the <scope> </scope> tag) from whatever it is to >> "compile" (without the ""). This should (hopefully) solve your problem... >> >> Regards, >> >> A. >> >> On Tue, Feb 10, 2015 at 2:02 AM, Mike Clarke <[email protected]> >> wrote: >> >>> It's likely you didn't run the mvn command from the top level "storm" >>> directory, as it notes in the readme: >>> >>> ``` >>> # Must be run from the top-level directory of the Storm code repository >>> $ mvn clean install -DskipTests=true >>> ``` >>> >>> Try re-running the `mvn clean install` command from the top-level of >>> your checkout. Then, future `mvn` commands should be run from the >>> examples/storm-starter directory if you're looking to try the example word >>> count topologies. >>> >>> On Mon, Feb 9, 2015 at 3:52 PM, Jon Gregg <[email protected]> wrote: >>> >>>> I cloned storm-starter from >>>> https://github.com/apache/storm/tree/master/examples/storm-starter, >>>> then went to build my jar locally using "mvn clean install >>>> -DskipTests=true" >>>> >>>> Here's the error I got: >>>> >>>> [ERROR] Failed to execute goal on project storm-starter: Could not >>>> resolve depen >>>> dencies for project org.apache.storm:storm-starter:jar:0.10.0-SNAPSHOT: >>>> Could no >>>> t find artifact org.apache.storm:storm-core:jar:0.10.0-SNAPSHOT in >>>> clojars (http >>>> s://clojars.org/repo/) -> [Help 1] >>>> >>>> Maybe I'm looking at the wrong location, but I don't see "storm" listed >>>> at https://clojars.org/repo/org/apache/ >>>> >>>> How can I make this work? >>>> >>>> Jon >>>> >>>> >>> >> >
