Comments on: Part 2: Terracotta: 1, Grails Searchable Plugin+Me: 1

By: Jan Rudert

Jan Rudert — Fri, 27 Feb 2009 09:10:52 +0000

How did you manage that terracotta does not complain about nonshareable groovy classes like MetaClassRegistry? I treid to workaround this by sharing all groovy internal classes but I am told that I should create terracotta locks for them. This is beyond what I am able to do… Thx

By: Fred

Fred — Wed, 10 Dec 2008 10:42:47 +0000

Thanks Mike for sharing your hard work !

Have you tried to use the Terracotta integration now available in the Compass release ?

I tried it but got the same classloader error than you…

By: Groovy on Grails : Terracotta Meets Grails with the Terracotta for Grails Plugin (Graeme Rocher)

Tue, 02 Sep 2008 17:24:32 +0000

[...] that adds support for the Terracotta data grid. It was always possible to do this with a bit of manual configuration, but now the plugin automates things nicely using a few new Grails command line [...]

By: Mike

Mike — Wed, 30 Jan 2008 14:54:34 +0000

Graeme,

The classloader needs to be registered with Terracotta before any of the the classes you tell Terracotta about get loaded so I suppose it depends. Is there anyway to specify a precedence in how the plugins get loaded?

I think the best approach though is the Terracotta config module which would make it really easy to include/exclude Terracotta in the equation.

-Mike

By: Orion Letizi

Orion Letizi — Wed, 30 Jan 2008 13:49:47 +0000

Mike, this is great news. I’m glad you met with some success. This is very exciting stuff.

–Orion

By: Graeme Rocher

Graeme Rocher — Wed, 30 Jan 2008 09:48:01 +0000

Hey Mike, nice work. But couldn’t you do it without hacking Grails? At what point does the class loader have to be registered with Terracotta?

If it can happen later maybe you could do it a plugin with

def classLoader = ApplicationHolder.application.classLoader

By: Taylor Gautier

Taylor Gautier — Wed, 30 Jan 2008 04:36:27 +0000

Hey Mike. That’s awesome to see!!

More likely than not you can replace the named lock with “auto-synchronized” locks to get a little bit better lock granularity.

As far as Groovy goes, as a proof of concept, actually, I did cluster Groovy, but that wasn’t so much clustering Groovy as it was using Groovy to instantiate native Java objects that as you already know Terracotta supports natively.