Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-1301

update from 1.1.6 to 1.1.7 version cause "WARNING Couldn't destroy threadgroup" during run by exec-maven-plugin

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 1.1.7
    • logback-classic
    • None

    Description

      There is java maven project that do logging

      ...
      <dependency>
          <groupId>ch.qos.logback</groupId>
          <artifactId>logback-classic</artifactId>
          <version>1.1.6</version>
      </dependency>
      ...
      

      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 (the same problem even with latest version 1.2.3) , following WARNING appear during run by exec-maven-plugin

      ...
      [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
      
      ....
      

      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.

      I even tried to make logback.xml empty(no appenders) - still the same problem

      Attachments

        Activity

          People

            logback-dev Logback dev list
            romanivanov Roman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: