About Terracotta Documentation
This documentation is about Terracotta DSO, an advanced distributed-computing technology aimed at meeting special clustering requirements.
Terracotta products without the overhead and complexity of DSO meet the needs of almost all use cases and clustering requirements. To learn how to migrate from Terracotta DSO to standard Terracotta products, see Migrating From Terracotta DSO. To find documentation on non-DSO (standard) Terracotta products, see Terracotta Documentation. Terracotta release information, such as release notes and platform compatibility, is found in Product Information.
- How DSO Clustering Works
- Platform Concepts
- Hello Clustered World
- Setup and Configuration
- Planning for a Clustered App
- Configuring Terracotta DSO
- Configuration Reference
- Using Annotations
- Cluster Events
- Data Locality Methods
- Distributed Cache
- Clustered Async Data Processing
- Tool Guides
- Developer Console
- Operations Center
- tim-get (TIM Management Tool)
- Platform Statistics Recorder
- Eclipse Plugin
- Sessions Configurator
- Clustering Spring Webapp with Sessions Configurator
- Testing, Tuning, and Deployment
- Top 5 Tuning Tips
- Testing a Clustered App
- Tuning a Clustered App
- Deployment Guide
- Operations Guide
- FAQs and Troubleshooting
- General FAQ
- DSO Technical FAQ
- Troubleshooting Guide
- Non-portable Classes
- Migrating From DSO
- Concept and Architecture Guide
- Examinator Reference Application
- Clustered Data Structures Guide
- Integrating Terracotta DSO
- Clustering Spring Framework
- Integration Modules Manual
- AspectWerkz Pattern Language
Publish Date: November, 2011
Non-portable classes are not shareable in Terracotta.
There are two types of non-portable classes in Terracotta:
- Never-Portable - these classes represent local resources or other non-shareable classes and are never shared.
- Unsupported - currently these classes are not supported by Terracotta but may be supported in the future.
See the Concept and Architecture Guide for more information on portability in Terracotta.
The following list shows classes that are never shareable. Generally, these classes are not shareable because they are intrinsically associated with a local resource such as a socket, a file descriptor, or a thread:
If your current code base contains references to any of these classes, use the Terracotta setting
honor-transient. This mechanism specifies whether Terracotta should or should not share a field in a class that is marked with the transient keyword.
See the Concept and Architecture Guide for more information on transience in Terracotta.
See the Configuration Guide and Reference for more information on configuring transience in Terracotta.
The following list shows classes that are not shareable in Terracotta version 2.7 and earlier.
java.util.concurrent.atomic.AtomicBoolean is supported beginning with Terracotta 2.7.2.
In many cases, the
java.util.concurrent.* classes can be replaced by an equivalent class from the oswego concurrent class library.