This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

AnnouncementAnnouncement Module

Collapse

No announcement yet.

"Waiting for background work to complete" when Roo Shell open in STSPage Title Module

"Waiting for background work to complete" when Roo Shell open in STS

May 13th, 2011, 03:12 PM

I cannot seem to get a handle on using Roo effectively in STS. I like Roo. I want it to work, but the tooling is just not letting me use it. The Roo Shell seems to cause STS to hang for long periods of time, even when there are very few items for it to manage. I've made a couple of Roo-based projects in the past and just muscled through these types of delays, but I was hoping upon installing STS 2.6.1 with Roo 1.1.3, the problems would be resolved. I've created a new project. I have 4 entities. That's all Roo has to manage right now. After adding a custom finder to one of the entities, STS + Roo Shell has become unusable. That's all it took. Now every save causes a "waiting for background work to complete" message. Every Project->Clean is stalled indefinitely. The only escape is to Force Quit STS (because it will not shut down until the background work finishes, which never happens) and start anew without opening the Roo Shell. I then have to use Roo externally to STS and constantly refresh my project to pick up the changes. My machine is a MacBook Pro with a solid-state hard drive and 8GB of ram, so I know its not my machine's lack of "umph" that's slowing me down. Has anyone else had this problem? It has always existed for me with every version of STS + Roo Shell so far. It's like the project becomes "tainted," and there is no recovery. Once upon a time, clearing the sts-cache under the Roo directory might help temporarily, but ultimately, I always run into this time and time again. The proposed increased productivity that's supposed to come with using Roo is completely reversed by the required tools. Any ideas?

When starting the Roo-shell in STS it needs more then 10 minutes (consuming 100% CPU) until it executes a command (e.g. "hint");
When starting the Roo-shell from command line (Win-XP), it's just a matter of < 30 seconds...

Comment

I have had problems with Spring Roo 1.1.5 of a very similar manner working with a web project of around 25 entities. Working on a quad core machine I would have one core maxed out perminantly and Roo would take ages to get into a 'working' state.

The solution I found was to alter the Spring Roo roo.bat file (or roo.sh) to increase the default Java heap space: