I just spent hours trying to figure this out... (probably because I am a Spring newbie), but this might be a problem.

After upgrading to 1.1.2 - it didn't matter what I did in any of my controllers which had a backing class with 5 million+ records, I kept getting out of memory errors.

I then discovered that there was a new method in the AspectJ files for the controllers:

public Collection<Tweet> populateTweets() {
return Tweet.findAllTweets();

I don't really understand why it has to find all here? Any why the upgrade broke it. (seems it should have been there before).

I also found this post: https://jira.springsource.org/browse/ROO-2037

Which I did not 100% understand, but I pulled the method and returned null, and now my app works again.

What gives? Can anyone explain this? Do I need to create a bug report?