You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by Kristine Weissbarth <kr...@sourcepark.de> on 2003/06/26 11:31:10 UTC

maven hangs

hi,

my projects structure looks something like that with a lot of
subprojects:

project
|
|--subproject 1
|
|--subproject 2
|    |--subsubproject 2.1
|    |--subsubprojects 2.2
|
|--subproject 3
|
|--subproject 4
|    |--subsubproject 4.1
|...

using the reactor I'm generating the maven documentation website and if
I don't process all the subprojects this works fine. But if I try to run
the reactor for all the subprojects it hangs somewhere (after having
processed most of the subprojects) and doesn't 'move' any further. It
seems as if it was overloaded or something.
Does anybody know where the problem is?

Thanks.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: maven hangs

Posted by Kristine Weissbarth <kr...@sourcepark.de>.

Thanks for the reply. 

But what exactly are the reactor memory read outs? Where can I find
them? And how can I get the thread dump of the jvm under Linux? I tried
ctrl \ but nothing happened.

Thanks.




Am Don, 2003-06-26 um 11.32 schrieb Ben Walding:
> It's overloaded.
> 
> Probably...  there is about a 3-4M / project leak in the reactor.  Jason 
> has fixed it, but the changes aren't checked in yet.  It is the major 
> blocker which is holding up rc1.
> 
> What do the reactor memory read outs look like?
> 
> (That all being said, it shouldn't hang... can you get the thread dump 
> of the jvm?   ctrl-break on windows will produce it)
> 
> Kristine Weissbarth wrote:
> 
> >hi,
> >
> >my projects structure looks something like that with a lot of
> >subprojects:
> >
> >project
> >|
> >|--subproject 1
> >|
> >|--subproject 2
> >|    |--subsubproject 2.1
> >|    |--subsubprojects 2.2
> >|
> >|--subproject 3
> >|
> >|--subproject 4
> >|    |--subsubproject 4.1
> >|...
> >
> >using the reactor I'm generating the maven documentation website and if
> >I don't process all the subprojects this works fine. But if I try to run
> >the reactor for all the subprojects it hangs somewhere (after having
> >processed most of the subprojects) and doesn't 'move' any further. It
> >seems as if it was overloaded or something.
> >Does anybody know where the problem is?
> >
> >Thanks.
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >  
> >
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: maven hangs

Posted by Kristine Weissbarth <kr...@sourcepark.de>.

I think I got the thread dump of the jvm, I just had to wait. But it
doesn't tell me anything I understand either that help me. 
What do you think?



-----------start--------

Full thread dump Java HotSpot(TM) Client VM (1.4.0_03-b04 mixed mode):
 
"process forker" daemon prio=1 tid=0x0x857e6f0 nid=0x39a waiting on
monitor [be7ff000..be7ff87c]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x45d82580> (a java.lang.Object)
        at java.lang.UNIXProcessForker.run(Native Method)
        at java.lang.Thread.run(Thread.java:536)
 
"process reaper" daemon prio=1 tid=0x0x857e358 nid=0x399 runnable
[be9ff000..be9ff87c]
        at java.lang.UNIXProcessReaper.run(Native Method)
        at java.lang.Thread.run(Thread.java:536)
 
"Signal Dispatcher" daemon prio=1 tid=0x0x8082ae8 nid=0x397 waiting on
monitor [0..0]
 
"Finalizer" daemon prio=1 tid=0x0x807cb28 nid=0x394 waiting on monitor
[bf3ff000..bf3ff87c]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x455cea48> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
        - locked <0x455cea48> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
        at
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
 
"Reference Handler" daemon prio=1 tid=0x0x807bf58 nid=0x393 runnable
[bf5ff000..bf5ff87c]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x455ceab0> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:426)
        at
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:113)
        - locked <0x455ceab0> (a java.lang.ref.Reference$Lock)
 
"main" prio=1 tid=0x0x8051d10 nid=0x390 runnable [bfffb000..bfffd428]
        at java.lang.String.toCharArray(String.java:2159)
        at
org.apache.tools.ant.types.selectors.SelectorUtils.match(SelectorUtils.java:361)
        at
org.apache.tools.ant.types.selectors.SelectorUtils.matchPath(SelectorUtils.java:258)
        at
org.apache.tools.ant.DirectoryScanner.matchPath(DirectoryScanner.java:327)
        at
org.apache.tools.ant.DirectoryScanner.isExcluded(DirectoryScanner.java:773)
        at
org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:710)
        at
org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:571)
        at
org.apache.commons.jelly.tags.ant.FileIterator.setNextObject(FileIterator.java:164)
        at
org.apache.commons.jelly.tags.ant.FileIterator.hasNext(FileIterator.java:127)
        at
org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:137)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:113)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
        at
org.apache.commons.jelly.tags.util.AvailableTag.doTag(AvailableTag.java:110)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
        at
com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
        at com.werken.werkz.Goal.fire(Goal.java:639)
        at com.werken.werkz.Goal.attain(Goal.java:575)
        at
com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
        at
com.werken.werkz.jelly.AttainGoalTag.doTag(AttainGoalTag.java:106)
        at
org.apache.maven.jelly.tags.werkz.LazyAttainGoalTag.doTag(LazyAttainGoalTag.java:107)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
        at
com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
        at com.werken.werkz.Goal.fire(Goal.java:639)
        at com.werken.werkz.Goal.attain(Goal.java:575)
        at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
        at com.werken.werkz.Goal.attain(Goal.java:573)
        at
com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
        at
com.werken.werkz.jelly.AttainGoalTag.doTag(AttainGoalTag.java:106)
        at
org.apache.maven.jelly.tags.werkz.LazyAttainGoalTag.doTag(LazyAttainGoalTag.java:107)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
        at
com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
        at com.werken.werkz.Goal.fire(Goal.java:639)
        at com.werken.werkz.Goal.attain(Goal.java:575)
        at
com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
        at
com.werken.werkz.jelly.AttainGoalTag.doTag(AttainGoalTag.java:106)
        at
org.apache.maven.jelly.tags.werkz.LazyAttainGoalTag.doTag(LazyAttainGoalTag.java:107)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
        at
com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
        at com.werken.werkz.Goal.fire(Goal.java:639)
        at com.werken.werkz.Goal.attain(Goal.java:575)
        at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
        at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:369)
        at
org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:374)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
        at
com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
        at com.werken.werkz.Goal.fire(Goal.java:639)
        at com.werken.werkz.Goal.attain(Goal.java:575)
        at
com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
        at
com.werken.werkz.jelly.AttainGoalTag.doTag(AttainGoalTag.java:106)
        at
org.apache.maven.jelly.tags.werkz.LazyAttainGoalTag.doTag(LazyAttainGoalTag.java:107)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
        at
com.werken.werkz.jelly.PreGoalTag$1.firePreGoal(PreGoalTag.java:87)
        at com.werken.werkz.Goal.firePreGoalCallbacks(Goal.java:691)
        at com.werken.werkz.Goal.fire(Goal.java:616)
        at com.werken.werkz.Goal.attain(Goal.java:575)
        at
com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
        at
com.werken.werkz.jelly.AttainGoalTag.doTag(AttainGoalTag.java:106)
        at
org.apache.maven.jelly.tags.werkz.LazyAttainGoalTag.doTag(LazyAttainGoalTag.java:107)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
        at
com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
        at com.werken.werkz.Goal.fire(Goal.java:639)
        at com.werken.werkz.Goal.attain(Goal.java:575)
        at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
        at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:369)
        at
org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:374)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
        at
com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
        at com.werken.werkz.Goal.fire(Goal.java:639)
        at com.werken.werkz.Goal.attain(Goal.java:575)
        at
com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
        at
com.werken.werkz.jelly.AttainGoalTag.doTag(AttainGoalTag.java:106)
        at
org.apache.maven.jelly.tags.werkz.LazyAttainGoalTag.doTag(LazyAttainGoalTag.java:107)
        at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
        at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
        at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
        at
com.werken.werkz.jelly.PreGoalTag$1.firePreGoal(PreGoalTag.java:87)
        at com.werken.werkz.Goal.firePreGoalCallbacks(Goal.java:691)
        at com.werken.werkz.Goal.fire(Goal.java:616)
        at com.werken.werkz.Goal.attain(Goal.java:575)
        at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
        at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
        at org.apache.maven.cli.App.doMain(App.java:524)
        at org.apache.maven.cli.App.main(App.java:1080)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at com.werken.forehead.Forehead.run(Forehead.java:543)
        at com.werken.forehead.Forehead.main(Forehead.java:573)
 
"VM Thread" prio=1 tid=0x0x8078db0 nid=0x392 runnable
 
"VM Periodic Task Thread" prio=1 tid=0x0x80816f0 nid=0x395 waiting on
monitor
"Suspend Checker Thread" prio=1 tid=0x0x80820a0 nid=0x396 runnable


-----------end----------


Am Don, 2003-06-26 um 11.32 schrieb Ben Walding:
> It's overloaded.
> 
> Probably...  there is about a 3-4M / project leak in the reactor.  Jason 
> has fixed it, but the changes aren't checked in yet.  It is the major 
> blocker which is holding up rc1.
> 
> What do the reactor memory read outs look like?
> 
> (That all being said, it shouldn't hang... can you get the thread dump 
> of the jvm?   ctrl-break on windows will produce it)
> 
> Kristine Weissbarth wrote:
> 
> >hi,
> >
> >my projects structure looks something like that with a lot of
> >subprojects:
> >
> >project
> >|
> >|--subproject 1
> >|
> >|--subproject 2
> >|    |--subsubproject 2.1
> >|    |--subsubprojects 2.2
> >|
> >|--subproject 3
> >|
> >|--subproject 4
> >|    |--subsubproject 4.1
> >|...
> >
> >using the reactor I'm generating the maven documentation website and if
> >I don't process all the subprojects this works fine. But if I try to run
> >the reactor for all the subprojects it hangs somewhere (after having
> >processed most of the subprojects) and doesn't 'move' any further. It
> >seems as if it was overloaded or something.
> >Does anybody know where the problem is?
> >
> >Thanks.
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >  
> >
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: maven hangs

Posted by Ben Walding <de...@walding.com>.

It's overloaded.

Probably...  there is about a 3-4M / project leak in the reactor.  Jason 
has fixed it, but the changes aren't checked in yet.  It is the major 
blocker which is holding up rc1.

What do the reactor memory read outs look like?

(That all being said, it shouldn't hang... can you get the thread dump 
of the jvm?   ctrl-break on windows will produce it)

Kristine Weissbarth wrote:

>hi,
>
>my projects structure looks something like that with a lot of
>subprojects:
>
>project
>|
>|--subproject 1
>|
>|--subproject 2
>|    |--subsubproject 2.1
>|    |--subsubprojects 2.2
>|
>|--subproject 3
>|
>|--subproject 4
>|    |--subsubproject 4.1
>|...
>
>using the reactor I'm generating the maven documentation website and if
>I don't process all the subprojects this works fine. But if I try to run
>the reactor for all the subprojects it hangs somewhere (after having
>processed most of the subprojects) and doesn't 'move' any further. It
>seems as if it was overloaded or something.
>Does anybody know where the problem is?
>
>Thanks.
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>  
>



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: maven hangs

Posted by Kristine Weissbarth <kr...@sourcepark.de>.

hi,

thanks, but I already grouped goals together in my maven.xml, like this:

<maven:reactor
  ..
  goals="clean,jar:install,site:deploy"
  ..
/>

Is that what you meant?



Am Don, 2003-06-26 um 11.36 schrieb Vipul Vij:
> Hi Kristine,
> 
> I have found this true with my projects. I found the way around was to NOT
> to execute each goal separately but group a few together. E.g.. generate
> Artefacts task in maven.xml included jar:install and war:install. I don't
> know why, but it seemed to work. I think this was the problem, I will try to
> confirm this; I haven't looked at this for a long time.
> 
> Regards,
> 
> Vipul
> ----- Original Message -----
> From: "Kristine Weissbarth" <kr...@sourcepark.de>
> To: "Maven Users List" <us...@maven.apache.org>
> Sent: Thursday, June 26, 2003 10:31 AM
> Subject: maven hangs
> 
> 
> > hi,
> >
> > my projects structure looks something like that with a lot of
> > subprojects:
> >
> > project
> > |
> > |--subproject 1
> > |
> > |--subproject 2
> > |    |--subsubproject 2.1
> > |    |--subsubprojects 2.2
> > |
> > |--subproject 3
> > |
> > |--subproject 4
> > |    |--subsubproject 4.1
> > |...
> >
> > using the reactor I'm generating the maven documentation website and if
> > I don't process all the subprojects this works fine. But if I try to run
> > the reactor for all the subprojects it hangs somewhere (after having
> > processed most of the subprojects) and doesn't 'move' any further. It
> > seems as if it was overloaded or something.
> > Does anybody know where the problem is?
> >
> > Thanks.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: maven hangs

Posted by Vipul Vij <vi...@orange.net>.

Hi Kristine,

I have found this true with my projects. I found the way around was to NOT
to execute each goal separately but group a few together. E.g.. generate
Artefacts task in maven.xml included jar:install and war:install. I don't
know why, but it seemed to work. I think this was the problem, I will try to
confirm this; I haven't looked at this for a long time.

Regards,

Vipul
----- Original Message -----
From: "Kristine Weissbarth" <kr...@sourcepark.de>
To: "Maven Users List" <us...@maven.apache.org>
Sent: Thursday, June 26, 2003 10:31 AM
Subject: maven hangs


> hi,
>
> my projects structure looks something like that with a lot of
> subprojects:
>
> project
> |
> |--subproject 1
> |
> |--subproject 2
> |    |--subsubproject 2.1
> |    |--subsubprojects 2.2
> |
> |--subproject 3
> |
> |--subproject 4
> |    |--subsubproject 4.1
> |...
>
> using the reactor I'm generating the maven documentation website and if
> I don't process all the subprojects this works fine. But if I try to run
> the reactor for all the subprojects it hangs somewhere (after having
> processed most of the subprojects) and doesn't 'move' any further. It
> seems as if it was overloaded or something.
> Does anybody know where the problem is?
>
> Thanks.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org