[
https://issues.apache.org/jira/browse/IVY-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523255
]
Colin Fleming commented on IVY-598:
-----------------------------------
It actually seems to be this error here:
http://issues.apache.org/bugzilla/show_bug.cgi?id=42742
Increasing the PermGen space seems to make it work. I'm going to try loading
less classes to see if that will help, hopefully taskdefs persist across subant
calls.
So assuming this is actually the problem, it's not really an Ivy problem but
large builds are almost certainly going to have this problem with the
recommended Ivy usage pattern (buildlist/subant). I'm going to see if I can
come up with an imaginative solution to this, but this is probably worth noting
in the documentation somewhere. Our build is big (80+ modules) and up till now
we've been taskdef'ing using the antlib.xml, we might have to go to defining
individual tasks as required.
> ivy:info locks up
> -----------------
>
> Key: IVY-598
> URL: https://issues.apache.org/jira/browse/IVY-598
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.0.0-alpha-2
> Environment: OSX 10.4.10, JDK 1.5.0_07
> Reporter: Colin Fleming
> Attachments: debug.output.txt, threaddump.txt, threaddump2.txt,
> threaddump3.txt
>
>
> Occasionally Ivy seems to deadlock, and something that I've changed in our
> project suddenly makes it happen all the time. This is an urgent issue for
> us, it used to only affect me from time to time but suddenly it's frequently
> happening to most people in our project. It appears to lock up loading
> classes during an ivy:info. I can't break out with a Ctrl-C, I have to kill
> -9 the process from another terminal. I've attached three thread dumps from
> different times it's happened plus the debug output of one run of the
> ivy:info task (the run associated with threaddump3, in case it helps). This
> is almost 100% reproducible for me now, which unfortunately means I can build
> almost 0% of the time :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
