[logback-dev] [JIRA] (LOGBACK-1301) update from 1.1.6 to 1.1.7 version cause "WARNING Couldn't destroy threadgroup" during run by exec-maven-plugin

[QOS.CH (JIRA)]

Roman created LOGBACK-1301:
------------------------------

             Summary: update from 1.1.6 to 1.1.7 version cause "WARNING Couldn't destroy threadgroup" during run by exec-maven-plugin
                 Key: LOGBACK-1301
                 URL: https://jira.qos.ch/browse/LOGBACK-1301
             Project: logback
          Issue Type: Bug
          Components: logback-classic
    Affects Versions: 1.1.7
         Environment: $ mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00)
Maven home: /opt/maven/default
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /opt/jdk1.8.0_121/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-101-generic", arch: "amd64", family: "unix"
            Reporter: Roman
            Assignee: Logback dev list


There is java maven project that do logging
{code}
...
<dependency>
    <groupId>ch.qos.logback</groupId>
    <artifactId>logback-classic</artifactId>
    <version>1.1.6</version>
</dependency>
...
{code}
it works fine by itself, and it is executed by exec-maven-plugin in another project, works fine. 

On upgrade of project to 1.1.7 version , following WARNING appear during run by exec-maven-plugin

{code}
...
[INFO] --- exec-maven-plugin:1.4.0:java (default-cli) @ rdbds-xe-builder ---
[WARNING] thread Thread[logback-1,5,com.mycompany.job.ApplyMultipleScriptsRunner] was interrupted but is still alive after waiting at least 15000msecs
[WARNING] thread Thread[logback-1,5,com.mycompany.job.ApplyMultipleScriptsRunner] 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=com.mycompany.job.ApplyMultipleScriptsRunner,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:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS

....
{code}

Unfortunately I can not share projects, but I could provide more details on request.

It is not clear why version bump cause such problem, any advices on how to investigate problem or what could cause it are appreciated. 




--
This message was sent by Atlassian JIRA
(v7.3.1#73012)