It may also be helpful to enable logging to see if there are any exceptions in the execution. The console log only contains output from Maven. Is logging turned off (or a suitable slf4j backend missing)?
On Fri, Jun 2, 2017 at 5:00 PM, Thomas Weise <t...@apache.org> wrote: > Hi Claire, > > The stack traces suggest that the application was launched and the Apex > DAG is deployed and might be running (it runs in embedded mode). > > Do you see any output? In case it writes to files, anything in output or > output staging directories? > > Thanks, > Thomas > > > On Thu, Jun 1, 2017 at 3:18 PM, Claire Yuan <clairey...@yahoo-inc.com> > wrote: > >> Hi Vlad, >> Thanks for replying! Here attached my log and stack trace >> >> >> On Thursday, June 1, 2017 1:31 PM, Vlad Rozov <v.ro...@datatorrent.com> >> wrote: >> >> >> Hi Claire, >> >> Can you provide maven logs? It may also help to obtain stack trace. In a >> separate terminal window, run "jps -lv" and look for the jvm process id >> that executes org.apache.beam.examples.TfIdf. Use jstack <process id> to >> get the stack trace. >> >> Thank you, >> >> Vlad >> >> On 6/1/17 13:00, Claire Yuan wrote: >> >> Hi, >> I am using the Apex runner to execute Apache Beam example pipeline. >> However my terminal always get frozen when running the command: >> >> mvn compile exec:java -Dexec.mainClass=org.apache.beam.examples.TfIdf \ >> -Dexec.args="--inputFile=pom.xml --output=counts --runner=ApexRunner" >> -Papex-runner >> >> Would anyone have solution for this? >> >> Claire >> >> >> >> >> >
