|
»
»
»
Memory issues in 2.0.9
|
View:
New views
12 Messages
—
Rating Filter:
Alert me
|
 |
Memory issues in 2.0.9
by Ryan Moquin
::
Rate this Message:
Hello, I'm not sure what all to submit informationwise about this issue, but
I switched to Maven 2.0.9 and now my builds fail with PermGen errors and on my other build, it complains about being out of heapspace. When I switch back to 2.0.8, I do not get this memory errors during a full build Are there any known memory issues with 2.0.9? Or should I just be increasing my memory settings? It appears to me to be a bug, but I wanted to run it past you all. Has anyone else seen this problem? Thanks, Ryan |
|
|
Re: Memory issues in 2.0.9
by Wayne Fay
::
Rate this Message:
You sure the only difference is 2.0.8 vs 2.0.9? That would mean that
you have all plugins locked down (and same JDK etc), and only the core is changing. Is this the case? Wayne On 5/15/08, Ryan Moquin <fragility2.0@...> wrote: > Hello, I'm not sure what all to submit informationwise about this issue, but > I switched to Maven 2.0.9 and now my builds fail with PermGen errors and on > my other build, it complains about being out of heapspace. When I switch > back to 2.0.8, I do not get this memory errors during a full build Are > there any known memory issues with 2.0.9? Or should I just be increasing my > memory settings? It appears to me to be a bug, but I wanted to run it past > you all. Has anyone else seen this problem? > > Thanks, > > Ryan > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
RE: Memory issues in 2.0.9
by Brian E Fox
::
Rate this Message:
Same thought here, it's more likely that plugins changed. If you go back
to 2.0.8 and run with -U, then you should get the same plugins as 2.0.9 -----Original Message----- From: Wayne Fay [mailto:waynefay@...] Sent: Thursday, May 15, 2008 11:08 AM To: Maven Users List Subject: Re: Memory issues in 2.0.9 You sure the only difference is 2.0.8 vs 2.0.9? That would mean that you have all plugins locked down (and same JDK etc), and only the core is changing. Is this the case? Wayne On 5/15/08, Ryan Moquin <fragility2.0@...> wrote: > Hello, I'm not sure what all to submit informationwise about this issue, but > I switched to Maven 2.0.9 and now my builds fail with PermGen errors and on > my other build, it complains about being out of heapspace. When I switch > back to 2.0.8, I do not get this memory errors during a full build Are > there any known memory issues with 2.0.9? Or should I just be increasing my > memory settings? It appears to me to be a bug, but I wanted to run it past > you all. Has anyone else seen this problem? > > Thanks, > > Ryan > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Memory issues in 2.0.9
by Ryan Moquin
::
Rate this Message:
No, I'm just sure that I changed my path statement and reran it to see what
would happen. It's possible the plugins updated and I didn't realize it. I would hope that's the case. I'm not sure how to lock down the plugins. On Thu, May 15, 2008 at 11:07 AM, Wayne Fay <waynefay@...> wrote: > You sure the only difference is 2.0.8 vs 2.0.9? That would mean that > you have all plugins locked down (and same JDK etc), and only the core > is changing. Is this the case? > > Wayne > > On 5/15/08, Ryan Moquin <fragility2.0@...> wrote: > > Hello, I'm not sure what all to submit informationwise about this issue, > but > > I switched to Maven 2.0.9 and now my builds fail with PermGen errors and > on > > my other build, it complains about being out of heapspace. When I switch > > back to 2.0.8, I do not get this memory errors during a full build Are > > there any known memory issues with 2.0.9? Or should I just be increasing > my > > memory settings? It appears to me to be a bug, but I wanted to run it > past > > you all. Has anyone else seen this problem? > > > > Thanks, > > > > Ryan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > |
|
|
Re: Memory issues in 2.0.9
by Ryan Moquin
::
Rate this Message:
Ah ok. So by using 2.0.9 I will have different versions of plugins
downloaded into my plugins directory, but with 2.0.8 it will use a different set? I figured the behavior of which ones they use would be the same. On Thu, May 15, 2008 at 11:21 AM, Brian E. Fox <brianf@...> wrote: > Same thought here, it's more likely that plugins changed. If you go back > to 2.0.8 and run with -U, then you should get the same plugins as 2.0.9 > > -----Original Message----- > From: Wayne Fay [mailto:waynefay@...] > Sent: Thursday, May 15, 2008 11:08 AM > To: Maven Users List > Subject: Re: Memory issues in 2.0.9 > > You sure the only difference is 2.0.8 vs 2.0.9? That would mean that > you have all plugins locked down (and same JDK etc), and only the core > is changing. Is this the case? > > Wayne > > On 5/15/08, Ryan Moquin <fragility2.0@...> wrote: > > Hello, I'm not sure what all to submit informationwise about this > issue, but > > I switched to Maven 2.0.9 and now my builds fail with PermGen errors > and on > > my other build, it complains about being out of heapspace. When I > switch > > back to 2.0.8, I do not get this memory errors during a full build > Are > > there any known memory issues with 2.0.9? Or should I just be > increasing my > > memory settings? It appears to me to be a bug, but I wanted to run it > past > > you all. Has anyone else seen this problem? > > > > Thanks, > > > > Ryan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > |
|
|
Re: Memory issues in 2.0.9
by Brett Porter
::
Rate this Message:
I think I can confirm this is a problem in 2.0.9. But first things first.
To lock down your plugins, follow the instructions in the enforcer plugin: http://maven.apache.org/plugins/maven-enforcer-plugin/rules/requirePluginVersions.html You'll need the snapshot version of the enforcer plugin for this, however. I had already locked mine down according to this, so I should be getting consistent versions between 2.0.8 and 2.0.9. I had been getting OOME errors recently and blamed it on plugins that I'd meant to track down (and meanwhile had bumped my memory settings up). However, reverting those settings, the same build passes on 2.0.8, but fails on 2.0.9. I know I had similar problems with Maven trunk that not everyone could reproduce, so there might be additional environmental factors. Anyone should be able to test this by building Archiva trunk. I've got to run, but I'll ensure there's an issue in for 2.0.10 on this later. Cheers, Brett 2008/5/16 Ryan Moquin <fragility2.0@...>: > Ah ok. So by using 2.0.9 I will have different versions of plugins > downloaded into my plugins directory, but with 2.0.8 it will use a different > set? I figured the behavior of which ones they use would be the same. > > On Thu, May 15, 2008 at 11:21 AM, Brian E. Fox <brianf@...> > wrote: > >> Same thought here, it's more likely that plugins changed. If you go back >> to 2.0.8 and run with -U, then you should get the same plugins as 2.0.9 >> >> -----Original Message----- >> From: Wayne Fay [mailto:waynefay@...] >> Sent: Thursday, May 15, 2008 11:08 AM >> To: Maven Users List >> Subject: Re: Memory issues in 2.0.9 >> >> You sure the only difference is 2.0.8 vs 2.0.9? That would mean that >> you have all plugins locked down (and same JDK etc), and only the core >> is changing. Is this the case? >> >> Wayne >> >> On 5/15/08, Ryan Moquin <fragility2.0@...> wrote: >> > Hello, I'm not sure what all to submit informationwise about this >> issue, but >> > I switched to Maven 2.0.9 and now my builds fail with PermGen errors >> and on >> > my other build, it complains about being out of heapspace. When I >> switch >> > back to 2.0.8, I do not get this memory errors during a full build >> Are >> > there any known memory issues with 2.0.9? Or should I just be >> increasing my >> > memory settings? It appears to me to be a bug, but I wanted to run it >> past >> > you all. Has anyone else seen this problem? >> > >> > Thanks, >> > >> > Ryan >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> > -- Brett Porter Blog: http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
RE: Memory issues in 2.0.9
by Brian E Fox
::
Rate this Message:
Brett,
I'm all setup with Yourkit lately, do you have a public sample project I can profile? --Brian -----Original Message----- From: Brett Porter [mailto:brett.porter@...] Sent: Thursday, May 15, 2008 8:48 PM To: Maven Users List Subject: Re: Memory issues in 2.0.9 I think I can confirm this is a problem in 2.0.9. But first things first. To lock down your plugins, follow the instructions in the enforcer plugin: http://maven.apache.org/plugins/maven-enforcer-plugin/rules/requirePlugi nVersions.html You'll need the snapshot version of the enforcer plugin for this, however. I had already locked mine down according to this, so I should be getting consistent versions between 2.0.8 and 2.0.9. I had been getting OOME errors recently and blamed it on plugins that I'd meant to track down (and meanwhile had bumped my memory settings up). However, reverting those settings, the same build passes on 2.0.8, but fails on 2.0.9. I know I had similar problems with Maven trunk that not everyone could reproduce, so there might be additional environmental factors. Anyone should be able to test this by building Archiva trunk. I've got to run, but I'll ensure there's an issue in for 2.0.10 on this later. Cheers, Brett 2008/5/16 Ryan Moquin <fragility2.0@...>: > Ah ok. So by using 2.0.9 I will have different versions of plugins > downloaded into my plugins directory, but with 2.0.8 it will use a different > set? I figured the behavior of which ones they use would be the same. > > On Thu, May 15, 2008 at 11:21 AM, Brian E. Fox <brianf@...> > wrote: > >> Same thought here, it's more likely that plugins changed. If you go back >> to 2.0.8 and run with -U, then you should get the same plugins as 2.0.9 >> >> -----Original Message----- >> From: Wayne Fay [mailto:waynefay@...] >> Sent: Thursday, May 15, 2008 11:08 AM >> To: Maven Users List >> Subject: Re: Memory issues in 2.0.9 >> >> You sure the only difference is 2.0.8 vs 2.0.9? That would mean that >> you have all plugins locked down (and same JDK etc), and only the core >> is changing. Is this the case? >> >> Wayne >> >> On 5/15/08, Ryan Moquin <fragility2.0@...> wrote: >> > Hello, I'm not sure what all to submit informationwise about this >> issue, but >> > I switched to Maven 2.0.9 and now my builds fail with PermGen errors >> and on >> > my other build, it complains about being out of heapspace. When I >> switch >> > back to 2.0.8, I do not get this memory errors during a full build >> Are >> > there any known memory issues with 2.0.9? Or should I just be >> increasing my >> > memory settings? It appears to me to be a bug, but I wanted to run it >> past >> > you all. Has anyone else seen this problem? >> > >> > Thanks, >> > >> > Ryan >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> > -- Brett Porter Blog: http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Memory issues in 2.0.9
by Brett Porter
::
Rate this Message:
Yeah, I was going to run yourkit over it myself - but be my guest :)
http://svn.apache.org/repos/asf/archiva/trunk/ Build with mvn clean install -Dmaven.test.skip=true (just to be faster to analyse, it still occurs) It fails in the webapp module on 2.0.9. In the past, I tried commenting out various reporting plugins, and none in particular caused it - but getting rid of a couple stopped it happening. Cheers, Brett 2008/5/16 Brian E. Fox <brianf@...>: > Brett, > I'm all setup with Yourkit lately, do you have a public sample project I > can profile? > > --Brian > > -----Original Message----- > From: Brett Porter [mailto:brett.porter@...] > Sent: Thursday, May 15, 2008 8:48 PM > To: Maven Users List > Subject: Re: Memory issues in 2.0.9 > > I think I can confirm this is a problem in 2.0.9. But first things > first. > > To lock down your plugins, follow the instructions in the enforcer > plugin: > http://maven.apache.org/plugins/maven-enforcer-plugin/rules/requirePlugi > nVersions.html > > You'll need the snapshot version of the enforcer plugin for this, > however. > > I had already locked mine down according to this, so I should be > getting consistent versions between 2.0.8 and 2.0.9. I had been > getting OOME errors recently and blamed it on plugins that I'd meant > to track down (and meanwhile had bumped my memory settings up). > However, reverting those settings, the same build passes on 2.0.8, but > fails on 2.0.9. > > I know I had similar problems with Maven trunk that not everyone could > reproduce, so there might be additional environmental factors. Anyone > should be able to test this by building Archiva trunk. > > I've got to run, but I'll ensure there's an issue in for 2.0.10 on this > later. > > Cheers, > Brett > > 2008/5/16 Ryan Moquin <fragility2.0@...>: >> Ah ok. So by using 2.0.9 I will have different versions of plugins >> downloaded into my plugins directory, but with 2.0.8 it will use a > different >> set? I figured the behavior of which ones they use would be the same. >> >> On Thu, May 15, 2008 at 11:21 AM, Brian E. Fox > <brianf@...> >> wrote: >> >>> Same thought here, it's more likely that plugins changed. If you go > back >>> to 2.0.8 and run with -U, then you should get the same plugins as > 2.0.9 >>> >>> -----Original Message----- >>> From: Wayne Fay [mailto:waynefay@...] >>> Sent: Thursday, May 15, 2008 11:08 AM >>> To: Maven Users List >>> Subject: Re: Memory issues in 2.0.9 >>> >>> You sure the only difference is 2.0.8 vs 2.0.9? That would mean that >>> you have all plugins locked down (and same JDK etc), and only the > core >>> is changing. Is this the case? >>> >>> Wayne >>> >>> On 5/15/08, Ryan Moquin <fragility2.0@...> wrote: >>> > Hello, I'm not sure what all to submit informationwise about this >>> issue, but >>> > I switched to Maven 2.0.9 and now my builds fail with PermGen > errors >>> and on >>> > my other build, it complains about being out of heapspace. When I >>> switch >>> > back to 2.0.8, I do not get this memory errors during a full build >>> Are >>> > there any known memory issues with 2.0.9? Or should I just be >>> increasing my >>> > memory settings? It appears to me to be a bug, but I wanted to run > it >>> past >>> > you all. Has anyone else seen this problem? >>> > >>> > Thanks, >>> > >>> > Ryan >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >> > > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- Brett Porter Blog: http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
RE: Memory issues in 2.0.9
by Brian E Fox
::
Rate this Message:
No, it wasn't until 2.0.9 that we started providing defaults in the
superpom. I wrote about it here: http://blogs.sonatype.com/brian/2008/04/10/1207873624557.html -----Original Message----- From: Ryan Moquin [mailto:fragility2.0@...] Sent: Thursday, May 15, 2008 12:58 PM To: Maven Users List Subject: Re: Memory issues in 2.0.9 Ah ok. So by using 2.0.9 I will have different versions of plugins downloaded into my plugins directory, but with 2.0.8 it will use a different set? I figured the behavior of which ones they use would be the same. On Thu, May 15, 2008 at 11:21 AM, Brian E. Fox <brianf@...> wrote: > Same thought here, it's more likely that plugins changed. If you go back > to 2.0.8 and run with -U, then you should get the same plugins as 2.0.9 > > -----Original Message----- > From: Wayne Fay [mailto:waynefay@...] > Sent: Thursday, May 15, 2008 11:08 AM > To: Maven Users List > Subject: Re: Memory issues in 2.0.9 > > You sure the only difference is 2.0.8 vs 2.0.9? That would mean that > you have all plugins locked down (and same JDK etc), and only the core > is changing. Is this the case? > > Wayne > > On 5/15/08, Ryan Moquin <fragility2.0@...> wrote: > > Hello, I'm not sure what all to submit informationwise about this > issue, but > > I switched to Maven 2.0.9 and now my builds fail with PermGen errors > and on > > my other build, it complains about being out of heapspace. When I > switch > > back to 2.0.8, I do not get this memory errors during a full build > Are > > there any known memory issues with 2.0.9? Or should I just be > increasing my > > memory settings? It appears to me to be a bug, but I wanted to run > past > > you all. Has anyone else seen this problem? > > > > Thanks, > > > > Ryan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Memory issues in 2.0.9
by Asgeir Nilsen-2
::
Rate this Message:
Do you think this is related to MCOMPILER-64 in any way?
We've started experiencing a number of PermGen errors in our build. Most of the time setting PermSize to 128m helps, but not always. Asgeir On Thu, May 15, 2008 at 3:28 PM, Ryan Moquin <fragility2.0@...> wrote: > Hello, I'm not sure what all to submit informationwise about this issue, but > I switched to Maven 2.0.9 and now my builds fail with PermGen errors and on > my other build, it complains about being out of heapspace. When I switch > back to 2.0.8, I do not get this memory errors during a full build Are > there any known memory issues with 2.0.9? Or should I just be increasing my > memory settings? It appears to me to be a bug, but I wanted to run it past > you all. Has anyone else seen this problem? > > Thanks, > > Ryan > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Memory issues in 2.0.9
by Brett Porter
::
Rate this Message:
2008/5/18 Asgeir S. Nilsen <asgeirn@...>:
> Do you think this is related to MCOMPILER-64 in any way? Perhaps - the comments do say 2.0.8 works? I filed this issue to track: MNG-3584 - Brett -- Brett Porter Blog: http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Memory issues in 2.0.9
by Ryan Moquin
::
Rate this Message:
If it at all helps, mine only fails a little over halfway though a
multimodule build (there are probably 12 modules total) with 2.0.9, but makes it all the way with 2.0.8. Obviously that is very vague sine you know nothing about my projects, but what I'm hoping maybe helps a little is that it just doesn't quit on the first module, it does make it through quite a few of the modules before it quits. If that isn't helpful in anyway, just ignore me. :) On Mon, May 19, 2008 at 3:00 AM, Brett Porter <brett.porter@...> wrote: > 2008/5/18 Asgeir S. Nilsen <asgeirn@...>: > > Do you think this is related to MCOMPILER-64 in any way? > > Perhaps - the comments do say 2.0.8 works? > > I filed this issue to track: MNG-3584 > > - Brett > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > |
| Free Forum Powered by Nabble | Forum Help |