Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

Not sure this is your answer, but the Terracotta technical FAQ has a question that implies this can be caused by having an old version of Ehcache sneak in at runtime (maybe via WebLogic?).

I think the docs on this page are clear that the zapped server's data is cleared, not integrated into the other server's data. Only then can the zapped server start up as a mirror and sync with the active server's data.

This doc
http://terracotta.org/documentation/terracotta-server-array/server-arrays

and the related server-array docs mostly likely have your answers.

You're seeing how those specialized JARs for some of Terracotta's products serve a similar purpose to TIMs. The evolution of distributed data with Terracotta clustering, however, is away from these specialized JARs and toward the use of Ehcache directly. Or, if you don't want that, another good solution are the tools found in the Terracotta Toolkit.

http://terracotta.org/documentation/web-sessions/installation-guide

I can't speak to the accuracy of that blog you mention -- it's a bit outdated and uses DSO. You should try the instructions in http://terracotta.org/documentation/enterprise-ehcache/installation-guide with a clean start. That should work.

If you are saying there's no session replication, can you provide more details? Maybe a cookie-domain issue?

Use these instructions:

http://terracotta.org/documentation/web-sessions/installation-guide

I don't think you following the steps on that page. Your tc-config.xml has DSO items in it; do not use a TIM and do not instrument classes. Follow the instructions exactly as shown.

You don't need to use TIMs with the way current Terracotta clustering works. For example, see http://terracotta.org/documentation/enterprise-ehcache/installation-guide.

I think there's a discussion of this issue in http://ehcache.org/documentation/apis/jta. See the section Transaction Timeouts.

My apologies, I didn't see that FAQ, just your postings. Now I've looked at it and you're right, it's badly out of date. I will let an admin know about that.

Just to clarify, Terracotta != DSO. DSO is a specific technology that could be used with the Terracotta Server Array. There may be specific use cases for DSO, but it is not the best tool for the vast majority of use cases (for performance, reliability, ease of integration, flexibility, etc.). The Terracotta Server Array now uses a much improved object-distribution scheme.

But if you do find that your needs require DSO, the DSO docs are -- as you may have found -- here:

http://www.terracotta.org/confluence/display/docs/Home

I'm not sure where you're getting those URLs, but they are very old. Those pages haven't been used/updated in years. The latest Terracotta clustering docs are here:

http://terracotta.org/documentation

If you are trying to access DSO docs on the Confluence wiki, please try again and if any links are still not available, post the specific URLs.

Try Cache.setMemoryStoreEvictionPolicy(), and with Ehcache 2.5.1.