> When looking at the spawned process with Process Explorer, it seems to be doing nothing. No cpu usage and no IO.
Maybe it is blocking for some reason?
I have very occasionally observed this but not been able to reliably reproduce it to debug.
It could be something wrong with the new mechanism to try and keep the Grails process active and reuse it. Why it sometimes totally locks up before even seeming to have done anything at all is still mystery to me. If you have a way to reliably reproduce that problem it would be interesting to know how. If I can reproduce I may be able to fix it for the next release.
As workaround you may be able to just switch back to the older and slower way of executing Grails commands by doing this:
- Open the preferences via: Windows >> Preferences
- Go to "Groovy >> Grails >> Grails Launch"
- Deselect the 'Keep external Grails running' option.
Kris De Volder -- SpringSource