maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5589) Investigate how plugin classloaders are shutdown
Date Fri, 14 Feb 2014 16:14:57 GMT
Jason van Zyl created MNG-5589:
----------------------------------

             Summary: Investigate how plugin classloaders are shutdown
                 Key: MNG-5589
                 URL: https://jira.codehaus.org/browse/MNG-5589
             Project: Maven 2 & 3
          Issue Type: Improvement
    Affects Versions: 3.2.1
            Reporter: Jason van Zyl


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
(v6.1.6#6162)

Mime
View raw message