You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2020/07/10 13:22:00 UTC
[jira] [Commented] (HDDS-3954) Recon IllegalThreadStateException
when destroy thread group
[ https://issues.apache.org/jira/browse/HDDS-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155466#comment-17155466 ]
Attila Doroszlai commented on HDDS-3954:
----------------------------------------
[~maobaolong], which git revision do you see this warning with? It should have been fixed in HDDS-3910.
> Recon IllegalThreadStateException when destroy thread group
> -----------------------------------------------------------
>
> Key: HDDS-3954
> URL: https://issues.apache.org/jira/browse/HDDS-3954
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Recon
> Affects Versions: 0.5.0
> Reporter: maobaolong
> Priority: Major
>
> [INFO] --- maven-jar-plugin:2.5:test-jar (default) @ hadoop-ozone-tools ---
> [INFO] Building jar: /Users/mbl/projects/github/hadoop-ozone/hadoop-ozone/tools/target/hadoop-ozone-tools-0.6.0-SNAPSHOT-tests.jar
> [WARNING] thread Thread[Timer-0,5,org.hadoop.ozone.recon.codegen.JooqCodeGenerator] was interrupted but is still alive after waiting at least 15000msecs
> [WARNING] thread Thread[Timer-0,5,org.hadoop.ozone.recon.codegen.JooqCodeGenerator] will linger despite being asked to die via interruption
> [WARNING] thread Thread[derby.rawStoreDaemon,5,derby.daemons] will linger despite being asked to die via interruption
> [WARNING] NOTE: 2 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.hadoop.ozone.recon.codegen.JooqCodeGenerator,maxpri=10]
> java.lang.IllegalThreadStateException
> at java.lang.ThreadGroup.destroy (ThreadGroup.java:778)
> at org.codehaus.mojo.exec.ExecJavaMojo.execute (ExecJavaMojo.java:328)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:190)
> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
> at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
> at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
> at java.lang.Thread.run (Thread.java:748)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org