Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0-alpha-10
-
Fix Version/s: None
-
Component/s: Container
-
Labels:None
-
Number of attachments :
Description
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.
Issue Links
- is depended upon by
-
MNG-2879
Thousands of [WARNING] Component returned which is not the same manager.
-
I did some tests by changing the comments. This message is definately coming from the ClassicSingletonComponentManager.java not the KeepAlive.....java file.