You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2006/10/18 04:26:52 UTC
[jira] Commented: (MNG-2498) Thousands of [WARNING] Component
returned which is not the same manager.
[ http://jira.codehaus.org/browse/MNG-2498?page=comments#action_77906 ]
Brian Fox commented on MNG-2498:
--------------------------------
I did some tests by changing the comments. This message is definately coming from the ClassicSingletonComponentManager.java not the KeepAlive.....java file.
> Thousands of [WARNING] Component returned which is not the same manager.
> -------------------------------------------------------------------------
>
> Key: MNG-2498
> URL: http://jira.codehaus.org/browse/MNG-2498
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.4
> Reporter: Brian Fox
>
> Reported to Jason in IRC. This is starting to happen on more and more machines:
> [WARNING] Component returned which is not the same manager. Ignored. component=o rg.apache.maven.profiles.activation.JdkPrefixProfileActivator@13f304
> It happens when processing resources, mostly for war projects although I'm not 100% positive it's only wars. We see one of these warnings apparently for every file processed because sometimes there are just a few and sometimes there are 1000s correlating to the number of files in the project. So far it only happens on dual-core machines although not every time. It smells of a multithreading issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira