You could work around it as follows, note that I haven't tried this out with an example, but it should work. The version numbers in the instructions are for the latest and greatest of everything, adapt accordingly if you need it.

1. get the binary version of the ehcache tim from http://forge.terracotta.org/releases/downloads/tim-ehcache/tags/release-1.1.2/
2. unzip the archive:
Code:

unzip tim-ehcache-1.1.2-bin.zip

3. go into the archive directory:
Code:

cd tim-ehcache-1.1.2

4. extract the terracotta configuration file for the TIM:
Code:

unzip tim-ehcache-1.3-1.1.2.jar terracotta.xml

5. edit the configuration file, find the snippet below and remove it:
Code:

     <root>
       <field-name>net.sf.ehcache.CacheManager.ALL_CACHE_MANAGERS</field-name>
     </root>
     <root>
       <field-name>net.sf.ehcache.CacheManager.singleton</field-name>
     </root>

6. save the configuration file
7. put it back into the TIM:
Code:

zip tim-ehcache-1.3-1.1.2.jar terracotta.xml

8. put the new TIM jars in the modules directory of your Terracotta installation (make sure that none of the old TIM jars are there anymore)
Code:

mv tim-ehcache-*.jar $TC_INSTALL_DIR/modules

What you did here is make none of the caches and the cache managers shared. So instead of having all of them being shared, you can now cherry pick the ones that should be shared for your use case.

To do this, you could work with different CacheManager instances or even different Cache instances I think. The ones that are shared should be put into a collection field, or individual fields of one of your application classes. You should then adapt your tc-config.xml file to include those fields as shared Terracotta roots.

Let me know how this goes.

Take care,

Geert