You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/23 12:23:00 UTC

[jira] [Updated] (MNG-5589) Investigate how plugin classloaders are shutdown

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

Elliotte Rusty Harold updated MNG-5589:
---------------------------------------
    Issue Type: Bug  (was: Improvement)

> Investigate how plugin classloaders are shutdown
> ------------------------------------------------
>
>                 Key: MNG-5589
>                 URL: https://issues.apache.org/jira/browse/MNG-5589
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.2.1
>            Reporter: Jason van Zyl
>            Priority: Major
>             Fix For: 3.x / Backlog
>
>
> http://www.mail-archive.com/dev@maven.apache.org/msg99645.html
> Stuart's analysis of the above thread:
> I suspect this is related to the change in Classworlds 2.4.1+ to use the
> new ClassLoader.close() method available in Java7 to forcibly close plugin
> ClassLoaders when the plugin/container realm is disposed. This happens
> after the Maven build is finished, but before JVM shutdown hooks run.
> Any plugin that registers a JVM shutdown hook which tries to load
> classes/resources from the original plugin realm will throw a NCDFE -
> you'll probably see similar issues if a plugin forks threads that are still
> running after the plugin/container realm has been disposed and subsequently
> try to load classes.
> ( note that the same error will likely occur with Maven 3.1.1 since it uses
> the same version of Classworlds )



--
This message was sent by Atlassian Jira
(v8.3.4#803005)