beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Wegner (JIRA)" <j...@apache.org>
Subject [jira] [Created] (BEAM-330) Maven exec warning message on Dataflow WordCount Example
Date Thu, 09 Jun 2016 15:46:20 GMT
Scott Wegner created BEAM-330:
---------------------------------

             Summary: Maven exec warning message on Dataflow WordCount Example
                 Key: BEAM-330
                 URL: https://issues.apache.org/jira/browse/BEAM-330
             Project: Beam
          Issue Type: Bug
          Components: examples-java
            Reporter: Scott Wegner
            Assignee: Scott Wegner
            Priority: Minor


When running the WordCount example with DataflowPipelineRunner, sometimes the Maven process
will emit a warning when trying to tear down the process:

{quote}{noformat}
[DEBUG] interrupting thread Thread[pool-1-thread-1,5,org.apache.beam.examples.WordCount]
[DEBUG] joining on thread Thread[pool-1-thread-1,5,org.apache.beam.examples.WordCount]
[WARNING] thread Thread[pool-1-thread-1,5,org.apache.beam.examples.WordCount] was interrupted
but is still alive after waiting at least 14999msecs
[WARNING] thread Thread[pool-1-thread-1,5,org.apache.beam.examples.WordCount] will linger
despite being asked to die via interruption
[WARNING] NOTE: 1 thread(s) did not finish despite being asked to  via interruption. This
is not a problem with exec:java, it is a problem with the running code. Although not serious,
it should be remedied.
[WARNING] Couldn't destroy threadgroup org.codehaus.mojo.exec.ExecJavaMojo$IsolatedThreadGroup[name=org.apache.beam.examples.WordCount,maxpri=10]
{noformat}{quote}

This appears to be some bad interaction between exec-maven-plugin and DataflowPipelineRunner,
possibly due to exec-maven-plugin's use of Guice and our shading of it.

The problem doesn't always reproduce, except when executing multiple Maven targets, such as
"mvn install exec:java \[...\]"

Disabling exec:java's cleanupDaemonThreads indeed suppresses the issue.  I recommend we add
this configuration to the root pom.xml.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message