Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364317

Summary:	Launching as an Acceleo Generator with some non compilable projects : Eclipse is blocked and need to be killed (deadlock)
Product:	[Modeling] Acceleo	Reporter:	Cedric Brun <cedric.brun>
Component:	Core	Assignee:	Project Inbox <acceleo-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	blocker
Priority:	P3	CC:	laurent.goubet
Version:	3.2
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Cedric Brun

2011-11-21 07:59:31 EST

I'm using Acceleo 3.2 on a dynamic instance.  Launching the generator it get stuck at 57% of the "launching". After waiting a few minutes, the only option I get is to kill Eclipse

Binary or EMTL emtl => it doesn't matter.

This used to work with 3.2 milestones if I recal correctly. Looks like this regression was introduced late in the developments.

To reproduce 
- import the two projects here : https://github.com/cbrun/versions-generator
- start the launch configuration

Comment 1 Laurent Goubet

2011-11-21 08:16:59 EST

Cannot be reproduced on windows 7 with the latest code from git. Should be looked at under an unix-based OS.

Comment 2 Cedric Brun

2011-11-21 08:21:12 EST

I just checked out the Acceleo master, created a new workspace and launched and It work as expected. 

Weirder and weirder....

Comment 3 Cedric Brun

2011-11-21 09:38:20 EST

OK, we found what is related to being reproduced or not. 

I have most of EMF Core in the same workspace, I guess Acceleo deploys some bundles (and some are not even compiling - which might not help)

Comment 4 Cedric Brun

2011-11-21 09:54:32 EST

Even closing EMF core projects, I still ends up with a deadlock. 

My workspace is a mess with some projects not being compilable. The generator I want to launch is not depending on those but there is another generator, in the workspace, which might => acceleo then deploys and redeploys the bundles. At some point I end up with one gread waiting for "packageAdmin.refreshPackages()" while the other is waiting for "AcceleoWorkspaceUtil.dispose()".

Comment 5 Cedric Brun

2011-11-21 09:54:42 EST

Even closing EMF core projects, I still ends up with a deadlock. 

My workspace is a mess with some projects not being compilable. The generator I want to launch is not depending on those but there is another generator, in the workspace, which might => acceleo then deploys and redeploys the bundles. At some point I end up with one gread waiting for "packageAdmin.refreshPackages()" while the other is waiting for "AcceleoWorkspaceUtil.dispose()".

Comment 6 Cedric Brun

2011-11-21 10:07:48 EST

I also had NPE's from org.eclipse.acceleo.common.internal.utils.workspace.AcceleoWorkspaceUtil.checkImportPackagesDependencies(IPluginModelBase)

because of my "broken workspace".

Comment 7 Cedric Brun

2011-11-21 10:14:13 EST

Fixed an pushed in 
 bfdd6121553286e985e8bc80fb1c488a756a561a (master)
 8fb4e5287bd0c3730fef480c7a61c5a1bf81b030 (R3_2_maintenance)