Maven
  1. Maven
  2. MNG-2879

Thousands of [WARNING] Component returned which is not the same manager.

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.0.6
    • Fix Version/s: None
    • Component/s: Plugins and Lifecycle
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      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 issue has already been fixed in PLX-287. This MNG issue is to try and get that fix into 2.0.x

        Issue Links

          Activity

          Hide
          Jason van Zyl added a comment -

          Brian, Andy looked into this and we can't fix it easily without upgrading the container and that's just too much work before the 2.0.6 release. It will take a few days of testing but for 2.0.7 we can try to upgrade the container which will bring people in line with 2.1 but will require much testing.

          Show
          Jason van Zyl added a comment - Brian, Andy looked into this and we can't fix it easily without upgrading the container and that's just too much work before the 2.0.6 release. It will take a few days of testing but for 2.0.7 we can try to upgrade the container which will bring people in line with 2.1 but will require much testing.
          Hide
          Jason van Zyl added a comment -

          Sorry, this one seems to be of limited concern, and again requires more container work then I'd like for this version.

          Show
          Jason van Zyl added a comment - Sorry, this one seems to be of limited concern, and again requires more container work then I'd like for this version.
          Hide
          brianfox brianfox added a comment -

          We aren't seeing this anymore. Leaving it open for now to see if anyone else does. Bumping from 2.0.8, updating the container isn't going to make it here either.

          Show
          brianfox brianfox added a comment - We aren't seeing this anymore. Leaving it open for now to see if anyone else does. Bumping from 2.0.8, updating the container isn't going to make it here either.
          Hide
          jp guguy added a comment -

          FYI, stil getting the issue with 2.0.8,
          [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@

          Show
          jp guguy added a comment - FYI, stil getting the issue with 2.0.8, [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@
          Hide
          Chris Graham added a comment -

          FYI, still there in 2.0.9, and on a pure jar file:

          [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@674c674c

          java -version:

          java version "1.5.0"
          Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20071025 (SR6b))
          IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20071007 (JIT enabled)
          J9VM - 20071004_14218_lHdSMR
          JIT - 20070820_1846ifx1_r8
          GC - 200708_10)
          JCL - 20071025

          Show
          Chris Graham added a comment - FYI, still there in 2.0.9, and on a pure jar file: [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@674c674c java -version: java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20071025 (SR6b)) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20071007 (JIT enabled) J9VM - 20071004_14218_lHdSMR JIT - 20070820_1846ifx1_r8 GC - 200708_10) JCL - 20071025
          Hide
          EJ Ciramella added a comment -

          Are these just warnings or is there damage caused by this (improper processing, skipping of resources or something)?

          Show
          EJ Ciramella added a comment - Are these just warnings or is there damage caused by this (improper processing, skipping of resources or something)?
          Hide
          brianfox brianfox added a comment -

          In the cases where i saw this, the build was horribly slow, like 100x slower, probably due to the component manager not being able to reuse objects. So imo, the warnings are indicative of a real problem.

          Show
          brianfox brianfox added a comment - In the cases where i saw this, the build was horribly slow, like 100x slower, probably due to the component manager not being able to reuse objects. So imo, the warnings are indicative of a real problem.
          Hide
          Dan Sullivan added a comment -

          Still seeing the same thing here, with Maven 2.0.9 and an IBM 1.5 JVM.

          $ mvn -version
          Maven version: 2.0.9
          Java version: 1.5.0
          OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" Family: "dos"

          $ java -version
          java version "1.5.0"
          Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20080303 (SR6b + IZ15865))
          IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223ifx-20080303 (JIT enabled)
          J9VM - 20080228_17641_lHdSMR
          JIT - 20070820_1846ifx1_r8
          GC - 200802_28)
          JCL - 20071025

          When I switch to the Sun JDK, I don't get the error

          $ java -version
          java version "1.5.0_16"
          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
          Java HotSpot(TM) Client VM (build 1.5.0_16-b02, mixed mode)

          So maybe it's only an issue with the IBM JRE?

          Show
          Dan Sullivan added a comment - Still seeing the same thing here, with Maven 2.0.9 and an IBM 1.5 JVM. $ mvn -version Maven version: 2.0.9 Java version: 1.5.0 OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" Family: "dos" $ java -version java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20080303 (SR6b + IZ15865)) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223ifx-20080303 (JIT enabled) J9VM - 20080228_17641_lHdSMR JIT - 20070820_1846ifx1_r8 GC - 200802_28) JCL - 20071025 When I switch to the Sun JDK, I don't get the error $ java -version java version "1.5.0_16" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02) Java HotSpot(TM) Client VM (build 1.5.0_16-b02, mixed mode) So maybe it's only an issue with the IBM JRE?
          Hide
          Dave Meibusch added a comment -

          I can further confirm it is an IBM JVM issue for us. We build on every platform, but IBM JVM only on AIX.

          mvn -version
          Maven version: 2.0.9
          Java version: 1.5.0
          OS name: "aix" version: "5.2" arch: "ppc64" Family: "unix"

          java -version
          java version "1.5.0"
          Java(TM) 2 Runtime Environment, Standard Edition (build pap64dev-20060511 (SR2))
          IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423-20060504 (JIT enabled)
          J9VM - 20060501_06428_BHdSMr
          JIT - 20060428_1800_r8
          GC - 20060501_AA)
          JCL - 20060511a

          Build is very very slow, but haven't noticed any negative effects on build output.

          Show
          Dave Meibusch added a comment - I can further confirm it is an IBM JVM issue for us. We build on every platform, but IBM JVM only on AIX. mvn -version Maven version: 2.0.9 Java version: 1.5.0 OS name: "aix" version: "5.2" arch: "ppc64" Family: "unix" java -version java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pap64dev-20060511 (SR2)) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423-20060504 (JIT enabled) J9VM - 20060501_06428_BHdSMr JIT - 20060428_1800_r8 GC - 20060501_AA) JCL - 20060511a Build is very very slow, but haven't noticed any negative effects on build output.
          Hide
          brianfox brianfox added a comment -

          This was not on IBM jdk when i originally reported it. It mysteriously disappeared so it's dependent on some config in the build that must have changed. We did notice it start to happen on multicore machines but it wasn't exclusively multicore.

          Show
          brianfox brianfox added a comment - This was not on IBM jdk when i originally reported it. It mysteriously disappeared so it's dependent on some config in the build that must have changed. We did notice it start to happen on multicore machines but it wasn't exclusively multicore.
          Hide
          Julian Payne added a comment -

          I have this problem with maven 2.0.10 and IBM JDK 5.

          Show
          Julian Payne added a comment - I have this problem with maven 2.0.10 and IBM JDK 5.
          Hide
          Arne Kepp added a comment -

          I believe I am seeing the same thing while compiling trunk of GeoServer ( running mvn clean install -Pweb2 )

          java -version
          java version "1.5.0_18"
          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_18-b02)
          Java HotSpot(TM) Server VM (build 1.5.0_18-b02, mixed mode)

          mvn -version
          Maven version: 2.0.10
          Java version: 1.5.0_18
          OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"

          (Ubuntu 9.04 i386)

          Show
          Arne Kepp added a comment - I believe I am seeing the same thing while compiling trunk of GeoServer ( running mvn clean install -Pweb2 ) java -version java version "1.5.0_18" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_18-b02) Java HotSpot(TM) Server VM (build 1.5.0_18-b02, mixed mode) mvn -version Maven version: 2.0.10 Java version: 1.5.0_18 OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix" (Ubuntu 9.04 i386)
          Hide
          Justin K added a comment - - edited

          I get the same issue on Suse Linux running the IBM JDK (J9 with Maven 2.2.0. The build works correctly, but hundreds of these messages are given. For example:

          [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.OperatingSystemProfileActivator@1e161e16

          [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.FileProfileActivator@16161616

          [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@153e153e

          Show
          Justin K added a comment - - edited I get the same issue on Suse Linux running the IBM JDK (J9 with Maven 2.2.0. The build works correctly, but hundreds of these messages are given. For example: [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.OperatingSystemProfileActivator@1e161e16 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.FileProfileActivator@16161616 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@153e153e
          Hide
          Marcel Ammerlaan added a comment - - edited

          Also seeing this sometimes on IBM JDK 1.6.0 (sr5).

          [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753
          [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753
          [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753
          [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753

          This is mostly happening during an EAR build.

          I'm running Maven 2.2.1

          Show
          Marcel Ammerlaan added a comment - - edited Also seeing this sometimes on IBM JDK 1.6.0 (sr5). [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753 This is mostly happening during an EAR build. I'm running Maven 2.2.1
          Hide
          Paul Benedict added a comment -

          If Plexus is truly being dumped for Maven 3, this issue will resolve as Won't Fix.

          Show
          Paul Benedict added a comment - If Plexus is truly being dumped for Maven 3, this issue will resolve as Won't Fix.
          Hide
          Jason van Zyl added a comment -

          Plexus will eventually be dropped for Guice, so no active development will be done in Plexus unless it's a blocker.

          Show
          Jason van Zyl added a comment - Plexus will eventually be dropped for Guice, so no active development will be done in Plexus unless it's a blocker.
          Hide
          Dmitry Katsubo added a comment -

          @Paul Benedict: If this warning is an issue to be solved, why not to close it when Maven 3 is released?

          I confirm the problem for IBM JDK (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32) and Maven 2.2.1 (r801777).

          Show
          Dmitry Katsubo added a comment - @Paul Benedict: If this warning is an issue to be solved, why not to close it when Maven 3 is released? I confirm the problem for IBM JDK (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32) and Maven 2.2.1 (r801777).
          Hide
          jieryn added a comment -

          Is Maven-2.2.1 no longer supported when Maven-3 comes along?

          Show
          jieryn added a comment - Is Maven-2.2.1 no longer supported when Maven-3 comes along?
          Hide
          Brett Porter added a comment -

          Maven 2.2.1 will be supported for some time (and for now we still support Maven 2.0.11), but there are unlikely to be new releases unless someone steps up to drive them or there are relevant patches to apply. Non-blocker fixes are unlikely to be backported.

          Show
          Brett Porter added a comment - Maven 2.2.1 will be supported for some time (and for now we still support Maven 2.0.11), but there are unlikely to be new releases unless someone steps up to drive them or there are relevant patches to apply. Non-blocker fixes are unlikely to be backported.

            People

            • Assignee:
              Jason van Zyl
              Reporter:
              brianfox brianfox
            • Votes:
              14 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: