此内容没有您所选择的语言版本。

10.2.4. Object Models


JBoss Transaction Service supports two models for objects. Implementation of the state and concurrency controls depend on which model is used.
Single
The application only contains a single copy of the object The object resides within a single JVM, and all clients must address their invocations to this server. The single model provides better performance, but creates a single point of failure. In a multi-threaded environment, the object may not be protected from corruption if a single thread fails.
Single Object Model
Multiple
Logically, a single instance of the object exists. Copies of the object are distributed across multiple JVMs. Performance suffers compared to the single model, better failure isolation is achieved.
Multiple Object Model
The single model is the default. You can override this on a per-object basis by providing an appropriate instance of the com.arjuna.ats.arjuna.gandiva.ObjectName class when you create your object.

Note

You can change the model before any instantiation of the object There is no need for it to remain the same during the object's lifetime.
Use the following method to provide a suitable ObjectName class. Refer to Example 10.6, “Object Models” for an example.
  1. Create a new instance of ObjectName.
  2. Set the object model attribute using the com.arjuna.ats.arjuna.ArjunaNames.StateManager_objectModel() name.

Example 10.6. Object Models

{
    ObjectName attr = new ObjectName(“SNS:myObjectName”);
      
    attr.setLongAttribute(ArjunaNames.StateManager_objectModel(),
			  ObjectModel.SINGLE);
      
    AtomicObject obj = new AtomicObject(ObjectType.ANDPERSISTENT, attr);
}
Copy to Clipboard Toggle word wrap
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat