You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Andrew Williams <an...@handyande.co.uk> on 2007/03/13 12:17:20 UTC
Re: "Component returned which is not the same manager" ?
I fixed this last week, and is now released in plexus-containers 1.0-
alpha-19.
This fix is present in maven-2.1-SNAPSHOT also.
Andy
On 27 Feb 2007, at 14:47, Brian E. Fox wrote:
> I've been seeing this forever, it's very annoying. It significantly
> slows down our build when this happens, something along the lines
> of 20
> -> 40 minutes (100% increase). I thought it was because of all the
> logging so I recompiled that jar to remove the warning but it is still
> slow when it happens. I think it could be that since the object isn't
> returned to the correct manager, it isn't able to reuse them correctly
> and results in an explosion of object creation. The original issue is:
> http://jira.codehaus.org/browse/PLX-287
>
> -----Original Message-----
> From: Andrew Williams [mailto:andy@handyande.co.uk]
> Sent: Tuesday, February 27, 2007 6:21 AM
> To: Maven Developers List
> Subject: Re: "Component returned which is not the same manager" ?
>
> This is a plexus bug, registered on JIRA already.
> Not sure if anyone knows what is causing it, but there is one possible
> related change being looked into I believe.
>
> A
>
> On 27 Feb 2007, at 02:39, Jason Dillon wrote:
>
>> Anyone know what this means?
>>
>> <snip>
>> [WARNING] Component returned which is not the same manager.
>> Ignored.
>> component=org.apache.maven.profiles.activation.JdkPrefixProfileActiva
>> t
>
>> or@b113c7
>> </snip>
>>
>> I'm seeing a tone of these in the Geronimo build... seems to happen
>> randomly from build to build. I ran one build and did not see
>> this, then I started up a new build and I see like 1000x of these?
>>
>> Anyone know?
>>
>> --jason
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: "Component returned which is not the same manager" ?
Posted by Andrew Williams <an...@handyande.co.uk>.
Hmm, yes there is a good chance I could fix it on the branch, I will
get that sorted.
Andy
On 13 Mar 2007, at 15:07, Jason van Zyl wrote:
>
> On 13 Mar 07, at 6:53 AM 13 Mar 07, Andrew Williams wrote:
>
>> It is possible that the error was slowing things down, as
>> returning the wrong manager could cause a tree to be traversed
>> rather than returning the first leaf.
>>
>> Getting it into 2.0.6 is not very likely, as it is cutting edge
>> container which I don't think is slated to move to the 2.0.x
>> branch. I will investigate further and see what can be done.
>>
>
> I create a 1.0-alpha-9-stable branch so maybe we could slip it in
> there. I just wanted to use the exact same container with a
> detailed errata of what we fixed. The properties converter is the
> only thing that's different right now, any change we could wedge
> this fix in there too?
>
> Jason.
>
>> Andy
>>
>> On 13 Mar 2007, at 12:58, Brian E. Fox wrote:
>>
>>> Thanks Andy! When you found the problem, does it make sense that
>>> it was
>>> causing my builds to slow down even when I disabled the warning
>>> output?
>>>
>>> Is there any chance we can get this in 2.0.6?
>>>
>>> -----Original Message-----
>>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>>> Sent: Tuesday, March 13, 2007 7:17 AM
>>> To: Maven Developers List
>>> Subject: Re: "Component returned which is not the same manager" ?
>>>
>>> I fixed this last week, and is now released in plexus-containers
>>> 1.0-
>>> alpha-19.
>>> This fix is present in maven-2.1-SNAPSHOT also.
>>>
>>> Andy
>>>
>>> On 27 Feb 2007, at 14:47, Brian E. Fox wrote:
>>>
>>>> I've been seeing this forever, it's very annoying. It significantly
>>>> slows down our build when this happens, something along the lines
>>>> of 20
>>>> -> 40 minutes (100% increase). I thought it was because of all the
>>>> logging so I recompiled that jar to remove the warning but it is
>>>> still
>>>> slow when it happens. I think it could be that since the object
>>>> isn't
>>>> returned to the correct manager, it isn't able to reuse them
>>>> correctly
>>>> and results in an explosion of object creation. The original
>>>> issue is:
>>>> http://jira.codehaus.org/browse/PLX-287
>>>>
>>>> -----Original Message-----
>>>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>>>> Sent: Tuesday, February 27, 2007 6:21 AM
>>>> To: Maven Developers List
>>>> Subject: Re: "Component returned which is not the same manager" ?
>>>>
>>>> This is a plexus bug, registered on JIRA already.
>>>> Not sure if anyone knows what is causing it, but there is one
>>>> possible
>>>> related change being looked into I believe.
>>>>
>>>> A
>>>>
>>>> On 27 Feb 2007, at 02:39, Jason Dillon wrote:
>>>>
>>>>> Anyone know what this means?
>>>>>
>>>>> <snip>
>>>>> [WARNING] Component returned which is not the same manager.
>>>>> Ignored.
>>>>> component=org.apache.maven.profiles.activation.JdkPrefixProfileAct
>>>>> iva
>>>
>>>>> t
>>>>
>>>>> or@b113c7
>>>>> </snip>
>>>>>
>>>>> I'm seeing a tone of these in the Geronimo build... seems to
>>>>> happen
>>>>> randomly from build to build. I ran one build and did not see
>>>>> this, then I started up a new build and I see like 1000x of these?
>>>>>
>>>>> Anyone know?
>>>>>
>>>>> --jason
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: "Component returned which is not the same manager" ?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Some of these repressed memories are flooding back... It definitely has
something to do with the preprocessing maven does in a reactor. Here's
why I think that:
I have a build with several high level parents containing many children
like this:
Root
/services
/appliations
/ui
/data
/assemblies
I was able to reproduce the problem fairly readily from the parent and
it would occur first in /data/childx. The logical thing to do was start
removing things from other folders like /services. As soon as I did
that, it stopped happening. This is even though nothing in /services had
compiled prior to the error in /data (I seem to recall that I modified
the jar to throw an exception instead of a warning so I could detect
exactly when it occurred)
This problem seems to be some how related to processing of files because
when it does throw warnings, it seems to scale based on the number of
files in a project, be it things packaged into wars or files packed or
unpacked into zips via assembly.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Tuesday, March 13, 2007 2:33 PM
To: Maven Developers List
Subject: RE: "Component returned which is not the same manager" ?
That's the whole problem. Once I start paring down my build to something
I can give out publically, it stops occuring.
-----Original Message-----
From: Andrew Williams [mailto:andy@handyande.co.uk]
Sent: Tuesday, March 13, 2007 1:22 PM
To: Maven Developers List
Subject: Re: "Component returned which is not the same manager" ?
I have looked at the code for the 1.0-alpha-9-stable and it is
considerably different. In fact the bug that I fixed is not present (as
far as I can see) in that version...
If perhaps someone could replicate it in that version then I could look
into it.
Andy
On 13 Mar 2007, at 15:07, Jason van Zyl wrote:
>
> On 13 Mar 07, at 6:53 AM 13 Mar 07, Andrew Williams wrote:
>
>> It is possible that the error was slowing things down, as returning
>> the wrong manager could cause a tree to be traversed rather than
>> returning the first leaf.
>>
>> Getting it into 2.0.6 is not very likely, as it is cutting edge
>> container which I don't think is slated to move to the 2.0.x branch.
>> I will investigate further and see what can be done.
>>
>
> I create a 1.0-alpha-9-stable branch so maybe we could slip it in
> there. I just wanted to use the exact same container with a detailed
> errata of what we fixed. The properties converter is the only thing
> that's different right now, any change we could wedge this fix in
> there too?
>
> Jason.
>
>> Andy
>>
>> On 13 Mar 2007, at 12:58, Brian E. Fox wrote:
>>
>>> Thanks Andy! When you found the problem, does it make sense that it
>>> was causing my builds to slow down even when I disabled the warning
>>> output?
>>>
>>> Is there any chance we can get this in 2.0.6?
>>>
>>> -----Original Message-----
>>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>>> Sent: Tuesday, March 13, 2007 7:17 AM
>>> To: Maven Developers List
>>> Subject: Re: "Component returned which is not the same manager" ?
>>>
>>> I fixed this last week, and is now released in plexus-containers
>>> 1.0-
>>> alpha-19.
>>> This fix is present in maven-2.1-SNAPSHOT also.
>>>
>>> Andy
>>>
>>> On 27 Feb 2007, at 14:47, Brian E. Fox wrote:
>>>
>>>> I've been seeing this forever, it's very annoying. It significantly
>>>> slows down our build when this happens, something along the lines
>>>> of 20
>>>> -> 40 minutes (100% increase). I thought it was because of all the
>>>> logging so I recompiled that jar to remove the warning but it is
>>>> still slow when it happens. I think it could be that since the
>>>> object isn't returned to the correct manager, it isn't able to
>>>> reuse them correctly and results in an explosion of object
>>>> creation. The original issue is:
>>>> http://jira.codehaus.org/browse/PLX-287
>>>>
>>>> -----Original Message-----
>>>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>>>> Sent: Tuesday, February 27, 2007 6:21 AM
>>>> To: Maven Developers List
>>>> Subject: Re: "Component returned which is not the same manager" ?
>>>>
>>>> This is a plexus bug, registered on JIRA already.
>>>> Not sure if anyone knows what is causing it, but there is one
>>>> possible related change being looked into I believe.
>>>>
>>>> A
>>>>
>>>> On 27 Feb 2007, at 02:39, Jason Dillon wrote:
>>>>
>>>>> Anyone know what this means?
>>>>>
>>>>> <snip>
>>>>> [WARNING] Component returned which is not the same manager.
>>>>> Ignored.
>>>>> component=org.apache.maven.profiles.activation.JdkPrefixProfileAct
>>>>> iva
>>>
>>>>> t
>>>>
>>>>> or@b113c7
>>>>> </snip>
>>>>>
>>>>> I'm seeing a tone of these in the Geronimo build... seems to
>>>>> happen randomly from build to build. I ran one build and did not
>>>>> see this, then I started up a new build and I see like 1000x of
>>>>> these?
>>>>>
>>>>> Anyone know?
>>>>>
>>>>> --jason
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>>>> additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>>> additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>>> additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>> additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>> additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: "Component returned which is not the same manager" ?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
That's the whole problem. Once I start paring down my build to something
I can give out publically, it stops occuring.
-----Original Message-----
From: Andrew Williams [mailto:andy@handyande.co.uk]
Sent: Tuesday, March 13, 2007 1:22 PM
To: Maven Developers List
Subject: Re: "Component returned which is not the same manager" ?
I have looked at the code for the 1.0-alpha-9-stable and it is
considerably different. In fact the bug that I fixed is not present (as
far as I can see) in that version...
If perhaps someone could replicate it in that version then I could look
into it.
Andy
On 13 Mar 2007, at 15:07, Jason van Zyl wrote:
>
> On 13 Mar 07, at 6:53 AM 13 Mar 07, Andrew Williams wrote:
>
>> It is possible that the error was slowing things down, as returning
>> the wrong manager could cause a tree to be traversed rather than
>> returning the first leaf.
>>
>> Getting it into 2.0.6 is not very likely, as it is cutting edge
>> container which I don't think is slated to move to the 2.0.x branch.
>> I will investigate further and see what can be done.
>>
>
> I create a 1.0-alpha-9-stable branch so maybe we could slip it in
> there. I just wanted to use the exact same container with a
> detailed errata of what we fixed. The properties converter is the
> only thing that's different right now, any change we could wedge
> this fix in there too?
>
> Jason.
>
>> Andy
>>
>> On 13 Mar 2007, at 12:58, Brian E. Fox wrote:
>>
>>> Thanks Andy! When you found the problem, does it make sense that
>>> it was
>>> causing my builds to slow down even when I disabled the warning
>>> output?
>>>
>>> Is there any chance we can get this in 2.0.6?
>>>
>>> -----Original Message-----
>>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>>> Sent: Tuesday, March 13, 2007 7:17 AM
>>> To: Maven Developers List
>>> Subject: Re: "Component returned which is not the same manager" ?
>>>
>>> I fixed this last week, and is now released in plexus-containers
>>> 1.0-
>>> alpha-19.
>>> This fix is present in maven-2.1-SNAPSHOT also.
>>>
>>> Andy
>>>
>>> On 27 Feb 2007, at 14:47, Brian E. Fox wrote:
>>>
>>>> I've been seeing this forever, it's very annoying. It significantly
>>>> slows down our build when this happens, something along the lines
>>>> of 20
>>>> -> 40 minutes (100% increase). I thought it was because of all the
>>>> logging so I recompiled that jar to remove the warning but it is
>>>> still
>>>> slow when it happens. I think it could be that since the object
>>>> isn't
>>>> returned to the correct manager, it isn't able to reuse them
>>>> correctly
>>>> and results in an explosion of object creation. The original
>>>> issue is:
>>>> http://jira.codehaus.org/browse/PLX-287
>>>>
>>>> -----Original Message-----
>>>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>>>> Sent: Tuesday, February 27, 2007 6:21 AM
>>>> To: Maven Developers List
>>>> Subject: Re: "Component returned which is not the same manager" ?
>>>>
>>>> This is a plexus bug, registered on JIRA already.
>>>> Not sure if anyone knows what is causing it, but there is one
>>>> possible
>>>> related change being looked into I believe.
>>>>
>>>> A
>>>>
>>>> On 27 Feb 2007, at 02:39, Jason Dillon wrote:
>>>>
>>>>> Anyone know what this means?
>>>>>
>>>>> <snip>
>>>>> [WARNING] Component returned which is not the same manager.
>>>>> Ignored.
>>>>> component=org.apache.maven.profiles.activation.JdkPrefixProfileAct
>>>>> iva
>>>
>>>>> t
>>>>
>>>>> or@b113c7
>>>>> </snip>
>>>>>
>>>>> I'm seeing a tone of these in the Geronimo build... seems to
>>>>> happen
>>>>> randomly from build to build. I ran one build and did not see
>>>>> this, then I started up a new build and I see like 1000x of these?
>>>>>
>>>>> Anyone know?
>>>>>
>>>>> --jason
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: "Component returned which is not the same manager" ?
Posted by Andrew Williams <an...@handyande.co.uk>.
I have looked at the code for the 1.0-alpha-9-stable and it is
considerably different. In fact the bug that I fixed is not present
(as far as I can see) in that version...
If perhaps someone could replicate it in that version then I could
look into it.
Andy
On 13 Mar 2007, at 15:07, Jason van Zyl wrote:
>
> On 13 Mar 07, at 6:53 AM 13 Mar 07, Andrew Williams wrote:
>
>> It is possible that the error was slowing things down, as
>> returning the wrong manager could cause a tree to be traversed
>> rather than returning the first leaf.
>>
>> Getting it into 2.0.6 is not very likely, as it is cutting edge
>> container which I don't think is slated to move to the 2.0.x
>> branch. I will investigate further and see what can be done.
>>
>
> I create a 1.0-alpha-9-stable branch so maybe we could slip it in
> there. I just wanted to use the exact same container with a
> detailed errata of what we fixed. The properties converter is the
> only thing that's different right now, any change we could wedge
> this fix in there too?
>
> Jason.
>
>> Andy
>>
>> On 13 Mar 2007, at 12:58, Brian E. Fox wrote:
>>
>>> Thanks Andy! When you found the problem, does it make sense that
>>> it was
>>> causing my builds to slow down even when I disabled the warning
>>> output?
>>>
>>> Is there any chance we can get this in 2.0.6?
>>>
>>> -----Original Message-----
>>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>>> Sent: Tuesday, March 13, 2007 7:17 AM
>>> To: Maven Developers List
>>> Subject: Re: "Component returned which is not the same manager" ?
>>>
>>> I fixed this last week, and is now released in plexus-containers
>>> 1.0-
>>> alpha-19.
>>> This fix is present in maven-2.1-SNAPSHOT also.
>>>
>>> Andy
>>>
>>> On 27 Feb 2007, at 14:47, Brian E. Fox wrote:
>>>
>>>> I've been seeing this forever, it's very annoying. It significantly
>>>> slows down our build when this happens, something along the lines
>>>> of 20
>>>> -> 40 minutes (100% increase). I thought it was because of all the
>>>> logging so I recompiled that jar to remove the warning but it is
>>>> still
>>>> slow when it happens. I think it could be that since the object
>>>> isn't
>>>> returned to the correct manager, it isn't able to reuse them
>>>> correctly
>>>> and results in an explosion of object creation. The original
>>>> issue is:
>>>> http://jira.codehaus.org/browse/PLX-287
>>>>
>>>> -----Original Message-----
>>>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>>>> Sent: Tuesday, February 27, 2007 6:21 AM
>>>> To: Maven Developers List
>>>> Subject: Re: "Component returned which is not the same manager" ?
>>>>
>>>> This is a plexus bug, registered on JIRA already.
>>>> Not sure if anyone knows what is causing it, but there is one
>>>> possible
>>>> related change being looked into I believe.
>>>>
>>>> A
>>>>
>>>> On 27 Feb 2007, at 02:39, Jason Dillon wrote:
>>>>
>>>>> Anyone know what this means?
>>>>>
>>>>> <snip>
>>>>> [WARNING] Component returned which is not the same manager.
>>>>> Ignored.
>>>>> component=org.apache.maven.profiles.activation.JdkPrefixProfileAct
>>>>> iva
>>>
>>>>> t
>>>>
>>>>> or@b113c7
>>>>> </snip>
>>>>>
>>>>> I'm seeing a tone of these in the Geronimo build... seems to
>>>>> happen
>>>>> randomly from build to build. I ran one build and did not see
>>>>> this, then I started up a new build and I see like 1000x of these?
>>>>>
>>>>> Anyone know?
>>>>>
>>>>> --jason
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: "Component returned which is not the same manager" ?
Posted by Jason van Zyl <ja...@maven.org>.
On 13 Mar 07, at 6:53 AM 13 Mar 07, Andrew Williams wrote:
> It is possible that the error was slowing things down, as returning
> the wrong manager could cause a tree to be traversed rather than
> returning the first leaf.
>
> Getting it into 2.0.6 is not very likely, as it is cutting edge
> container which I don't think is slated to move to the 2.0.x
> branch. I will investigate further and see what can be done.
>
I create a 1.0-alpha-9-stable branch so maybe we could slip it in
there. I just wanted to use the exact same container with a detailed
errata of what we fixed. The properties converter is the only thing
that's different right now, any change we could wedge this fix in
there too?
Jason.
> Andy
>
> On 13 Mar 2007, at 12:58, Brian E. Fox wrote:
>
>> Thanks Andy! When you found the problem, does it make sense that
>> it was
>> causing my builds to slow down even when I disabled the warning
>> output?
>>
>> Is there any chance we can get this in 2.0.6?
>>
>> -----Original Message-----
>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>> Sent: Tuesday, March 13, 2007 7:17 AM
>> To: Maven Developers List
>> Subject: Re: "Component returned which is not the same manager" ?
>>
>> I fixed this last week, and is now released in plexus-containers 1.0-
>> alpha-19.
>> This fix is present in maven-2.1-SNAPSHOT also.
>>
>> Andy
>>
>> On 27 Feb 2007, at 14:47, Brian E. Fox wrote:
>>
>>> I've been seeing this forever, it's very annoying. It significantly
>>> slows down our build when this happens, something along the lines
>>> of 20
>>> -> 40 minutes (100% increase). I thought it was because of all the
>>> logging so I recompiled that jar to remove the warning but it is
>>> still
>>> slow when it happens. I think it could be that since the object
>>> isn't
>>> returned to the correct manager, it isn't able to reuse them
>>> correctly
>>> and results in an explosion of object creation. The original
>>> issue is:
>>> http://jira.codehaus.org/browse/PLX-287
>>>
>>> -----Original Message-----
>>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>>> Sent: Tuesday, February 27, 2007 6:21 AM
>>> To: Maven Developers List
>>> Subject: Re: "Component returned which is not the same manager" ?
>>>
>>> This is a plexus bug, registered on JIRA already.
>>> Not sure if anyone knows what is causing it, but there is one
>>> possible
>>> related change being looked into I believe.
>>>
>>> A
>>>
>>> On 27 Feb 2007, at 02:39, Jason Dillon wrote:
>>>
>>>> Anyone know what this means?
>>>>
>>>> <snip>
>>>> [WARNING] Component returned which is not the same manager.
>>>> Ignored.
>>>> component=org.apache.maven.profiles.activation.JdkPrefixProfileActi
>>>> va
>>
>>>> t
>>>
>>>> or@b113c7
>>>> </snip>
>>>>
>>>> I'm seeing a tone of these in the Geronimo build... seems to happen
>>>> randomly from build to build. I ran one build and did not see
>>>> this, then I started up a new build and I see like 1000x of these?
>>>>
>>>> Anyone know?
>>>>
>>>> --jason
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: "Component returned which is not the same manager" ?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Hrm, that's a bummer. Thanks for looking into it. Is there any
possibility of patching a version that can run on 2.0.x? I'd be willing
to take something and use it internally if needed, if a patch is
possible.
-----Original Message-----
From: Andrew Williams [mailto:andy@handyande.co.uk]
Sent: Tuesday, March 13, 2007 9:54 AM
To: Maven Developers List
Subject: Re: "Component returned which is not the same manager" ?
It is possible that the error was slowing things down, as returning the
wrong manager could cause a tree to be traversed rather than returning
the first leaf.
Getting it into 2.0.6 is not very likely, as it is cutting edge
container which I don't think is slated to move to the 2.0.x branch.
I will investigate further and see what can be done.
Andy
On 13 Mar 2007, at 12:58, Brian E. Fox wrote:
> Thanks Andy! When you found the problem, does it make sense that it
> was causing my builds to slow down even when I disabled the warning
> output?
>
> Is there any chance we can get this in 2.0.6?
>
> -----Original Message-----
> From: Andrew Williams [mailto:andy@handyande.co.uk]
> Sent: Tuesday, March 13, 2007 7:17 AM
> To: Maven Developers List
> Subject: Re: "Component returned which is not the same manager" ?
>
> I fixed this last week, and is now released in plexus-containers 1.0-
> alpha-19.
> This fix is present in maven-2.1-SNAPSHOT also.
>
> Andy
>
> On 27 Feb 2007, at 14:47, Brian E. Fox wrote:
>
>> I've been seeing this forever, it's very annoying. It significantly
>> slows down our build when this happens, something along the lines of
>> 20
>> -> 40 minutes (100% increase). I thought it was because of all the
>> logging so I recompiled that jar to remove the warning but it is
>> still slow when it happens. I think it could be that since the object
>> isn't returned to the correct manager, it isn't able to reuse them
>> correctly and results in an explosion of object creation. The
>> original issue
>> is:
>> http://jira.codehaus.org/browse/PLX-287
>>
>> -----Original Message-----
>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>> Sent: Tuesday, February 27, 2007 6:21 AM
>> To: Maven Developers List
>> Subject: Re: "Component returned which is not the same manager" ?
>>
>> This is a plexus bug, registered on JIRA already.
>> Not sure if anyone knows what is causing it, but there is one
>> possible related change being looked into I believe.
>>
>> A
>>
>> On 27 Feb 2007, at 02:39, Jason Dillon wrote:
>>
>>> Anyone know what this means?
>>>
>>> <snip>
>>> [WARNING] Component returned which is not the same manager.
>>> Ignored.
>>> component=org.apache.maven.profiles.activation.JdkPrefixProfileActiv
>>> a
>
>>> t
>>
>>> or@b113c7
>>> </snip>
>>>
>>> I'm seeing a tone of these in the Geronimo build... seems to happen
>>> randomly from build to build. I ran one build and did not see this,
>>> then I started up a new build and I see like 1000x of these?
>>>
>>> Anyone know?
>>>
>>> --jason
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>> additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: "Component returned which is not the same manager" ?
Posted by Andrew Williams <an...@handyande.co.uk>.
It is possible that the error was slowing things down, as returning
the wrong manager could cause a tree to be traversed rather than
returning the first leaf.
Getting it into 2.0.6 is not very likely, as it is cutting edge
container which I don't think is slated to move to the 2.0.x branch.
I will investigate further and see what can be done.
Andy
On 13 Mar 2007, at 12:58, Brian E. Fox wrote:
> Thanks Andy! When you found the problem, does it make sense that it
> was
> causing my builds to slow down even when I disabled the warning
> output?
>
> Is there any chance we can get this in 2.0.6?
>
> -----Original Message-----
> From: Andrew Williams [mailto:andy@handyande.co.uk]
> Sent: Tuesday, March 13, 2007 7:17 AM
> To: Maven Developers List
> Subject: Re: "Component returned which is not the same manager" ?
>
> I fixed this last week, and is now released in plexus-containers 1.0-
> alpha-19.
> This fix is present in maven-2.1-SNAPSHOT also.
>
> Andy
>
> On 27 Feb 2007, at 14:47, Brian E. Fox wrote:
>
>> I've been seeing this forever, it's very annoying. It significantly
>> slows down our build when this happens, something along the lines
>> of 20
>> -> 40 minutes (100% increase). I thought it was because of all the
>> logging so I recompiled that jar to remove the warning but it is
>> still
>> slow when it happens. I think it could be that since the object isn't
>> returned to the correct manager, it isn't able to reuse them
>> correctly
>> and results in an explosion of object creation. The original issue
>> is:
>> http://jira.codehaus.org/browse/PLX-287
>>
>> -----Original Message-----
>> From: Andrew Williams [mailto:andy@handyande.co.uk]
>> Sent: Tuesday, February 27, 2007 6:21 AM
>> To: Maven Developers List
>> Subject: Re: "Component returned which is not the same manager" ?
>>
>> This is a plexus bug, registered on JIRA already.
>> Not sure if anyone knows what is causing it, but there is one
>> possible
>> related change being looked into I believe.
>>
>> A
>>
>> On 27 Feb 2007, at 02:39, Jason Dillon wrote:
>>
>>> Anyone know what this means?
>>>
>>> <snip>
>>> [WARNING] Component returned which is not the same manager.
>>> Ignored.
>>> component=org.apache.maven.profiles.activation.JdkPrefixProfileActiv
>>> a
>
>>> t
>>
>>> or@b113c7
>>> </snip>
>>>
>>> I'm seeing a tone of these in the Geronimo build... seems to happen
>>> randomly from build to build. I ran one build and did not see
>>> this, then I started up a new build and I see like 1000x of these?
>>>
>>> Anyone know?
>>>
>>> --jason
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: "Component returned which is not the same manager" ?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Thanks Andy! When you found the problem, does it make sense that it was
causing my builds to slow down even when I disabled the warning output?
Is there any chance we can get this in 2.0.6?
-----Original Message-----
From: Andrew Williams [mailto:andy@handyande.co.uk]
Sent: Tuesday, March 13, 2007 7:17 AM
To: Maven Developers List
Subject: Re: "Component returned which is not the same manager" ?
I fixed this last week, and is now released in plexus-containers 1.0-
alpha-19.
This fix is present in maven-2.1-SNAPSHOT also.
Andy
On 27 Feb 2007, at 14:47, Brian E. Fox wrote:
> I've been seeing this forever, it's very annoying. It significantly
> slows down our build when this happens, something along the lines
> of 20
> -> 40 minutes (100% increase). I thought it was because of all the
> logging so I recompiled that jar to remove the warning but it is still
> slow when it happens. I think it could be that since the object isn't
> returned to the correct manager, it isn't able to reuse them correctly
> and results in an explosion of object creation. The original issue is:
> http://jira.codehaus.org/browse/PLX-287
>
> -----Original Message-----
> From: Andrew Williams [mailto:andy@handyande.co.uk]
> Sent: Tuesday, February 27, 2007 6:21 AM
> To: Maven Developers List
> Subject: Re: "Component returned which is not the same manager" ?
>
> This is a plexus bug, registered on JIRA already.
> Not sure if anyone knows what is causing it, but there is one possible
> related change being looked into I believe.
>
> A
>
> On 27 Feb 2007, at 02:39, Jason Dillon wrote:
>
>> Anyone know what this means?
>>
>> <snip>
>> [WARNING] Component returned which is not the same manager.
>> Ignored.
>> component=org.apache.maven.profiles.activation.JdkPrefixProfileActiva
>> t
>
>> or@b113c7
>> </snip>
>>
>> I'm seeing a tone of these in the Geronimo build... seems to happen
>> randomly from build to build. I ran one build and did not see
>> this, then I started up a new build and I see like 1000x of these?
>>
>> Anyone know?
>>
>> --jason
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org