Mailing-List: contact commits-help@beam.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.incubator.apache.org
Date: Sat, 25 Jun 2016 16:53:37 +0000 (UTC)
From: "Daniel Halperin (JIRA)" <jira@apache.org>
To: commits@beam.incubator.apache.org
Message-ID: <JIRA.12977267.1465487124000.719.1466873617246@Atlassian.JIRA>
In-Reply-To: <JIRA.12977267.1465487124000@Atlassian.JIRA>
References: <JIRA.12977267.1465487124000@Atlassian.JIRA> <JIRA.12977267.1465487124243@arcas>
Subject: [jira] [Updated] (BEAM-330) Maven exec warning message on Dataflow
 WordCount Example
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 25 Jun 2016 16:53:42 -0000


     [ https://issues.apache.org/jira/browse/BEAM-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Halperin updated BEAM-330:
---------------------------------
    Fix Version/s: 0.2.0-incubating

> 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
>             Fix For: 0.2.0-incubating
>
>
> 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)