Community
Participate
Working Groups
Build Identifier: M20110210-1200 Continuation of http://www.eclipse.org/forums/index.php?t=rview&th=206257 I am one of the developper behind IvyDE : http://ant.apache.org/ivy/ivyde . This plugin is managing the dependencies computed by Ivy. In the trunk version I often get a sort of dead lock between some Eclipse Jobs and the IvyDE one and I would like to understand why, so I can fix my plugin. What I see is in the progress view, the IvyDE resolve job (job which compute the dependencies of each project and setup the IvyDE classpath containers) and the "Initialzin Java Tooling" jobs being both stuck. If I cancel the IvyDE job, then things progress and terminate sucessfully. Please find there the relevant jstack output : http://people.apache.org/~hibou/jstack-ivyde.txt I don't understand much which thread is blocking ivyde one. To explain a little bit the IvyDE stacks, the "Worker-4" is the IvyDE Job which is launching the "IvyDE resolver thread" which actually do the resolve. We have two threads here to bind the Eclipse progress monitor into Ivy's interuption mechanism so the resolve may be stop as early as possible. And during that resolve, Ivy is also configured to search dependencies into the workspace (WorkspaceResolver). And during that search in the workspace, it looks up for the IvyDE classpath containers of the projects which holds the Ivy metadata required to achieve the Ivy resolve. Reproducible: Always Steps to Reproduce: 1. Install latest IvyDE from the updatesite https://hudson.apache.org/hudson/job/IvyDE-updatesite/lastSuccessfulBuild/artifact/trunk/build 2. Setup a project which use IvyDE (there are many here http://svn.apache.org/repos/asf/ant/ivy/ivyde/trunk/test/ ) 3. Restart eclipse
Created attachment 191489 [details] the jstack output during the dead lock here is the jstack output referenced in the description
This looks like bug 320329
> This looks like bug 320329 Yup! Jay, please confirm if this is indeed a dup.
I tried with the 3.7 M6, I cannot reproduce the lock.
As per comment 4 *** This bug has been marked as a duplicate of bug 320329 ***
Verified with build I20110514-0800