cremersstijn :

I’m currently experimenting with grails and google app engine. Has anybody succeeded in deploying grails to app engine? or should i switch to gaelyk?

Deployment shouldn’t be a problem. Then again I havn’t tried it in a while. GAELYK probably will give you better performance once up on AppEngine though.

I recently got excited about Grails and GAE (I know, behind the power curve). do you have any updates with the new plugin. also, jsut to chip in, but some people are advocating GAELYK for Groovy/ GAE because of the pitfalls of grails/gae. Are you still developing on the GAE? can you forward me an example of a site you have done?

Thanks,
Keith

This is a real issue when writing Grails Applications for Google AppEngine. I have yet to find a solution to it.
The problem is that the grails runtime takes a long time to warm up. Too long for appengine infact.
Some people have tried to create a job that access your application every minute, to keep the runtime warm.
However since AppEngine is load balanced, you cannot garantuee that the job will ask for a response from the same server.
End result, you just eat up your qouta.

Now rumors has it that Google have done some profiling for Grails on AppEngine and came up with some areas to “fix”. I saw a tweet from Graeme a while back when there might be a possilibty to have some work done in that area for Grails 1.3.x.

But yes, this is a blocker for using Grails in AppEngine and I have yet to solve it. If anyone else figures it out please do tell.

Do you run into this? Are there examples of non-trivial applications or even trivial ones written in Grails that work reliably under App-Engine? What’s the secret?

Thanks!

Sorry for the late reply. Are you wrapping your save() in a transaction? I’ve noticed that unless I commit my transactions I cannot read the Id afterwards.

It has something todo with AppEngine prefeering to do the actual commit asynch, to avoid locking the url processing unless you really need the Id.