You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using prospero in maven exec plugin, the execution reports lingering threads:
[WARNING] thread Thread[JGit-FileStoreAttributeReader-1,5,org.wildfly.prospero.cli.CliMain] was interrupted but is still alive after waiting at least 15000msecs
[WARNING] thread Thread[JGit-FileStoreAttributeReader-1,5,org.wildfly.prospero.cli.CliMain] 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.wildfly.prospero.cli.CliMain,maxpri=10]
java.lang.IllegalThreadStateException
at java.lang.ThreadGroup.destroy (ThreadGroup.java:776)
at org.codehaus.mojo.exec.ExecJavaMojo.execute (ExecJavaMojo.java:331)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
This seems to be caused by jgit executors not being shut down. Part of fix is calling Git.shutdown(), but org.eclipse.jgit.util.FS executors are still not shutting down.
When using prospero in maven exec plugin, the execution reports lingering threads:
This seems to be caused by jgit executors not being shut down. Part of fix is calling
Git.shutdown()
, butorg.eclipse.jgit.util.FS
executors are still not shutting down.Below is an example pom.xml:
The text was updated successfully, but these errors were encountered: