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

Chapter 9. ORB specific configurations


JacORB

For JacORB to function correctly, ensure there is a valid jacorb.properties or .jacorb_properties file in one of the following places:

  • The CLASSPATH.
  • The home directory of the user running the JBoss Transaction Service. The home directory is retrieved using System.getProperty( “user.home” );
  • The current directory.
  • The lib directory of the JDK used to run your application. This is retrieved using System.getProperty( “java.home” );
The above places are searched in the order given. A template jacorb.properties file can be found in the JacORB installation directory.
The JacORB properties file contains two important properties which must be configured appropriately for your application, they are:
  • jacorb.poa.thread_pool_max
  • jacorb.poa.thread_pool_min
These properties specify the minimum and maximum number of request processing threads that JacORB will use in its thread pool. If too few threads are available, the application may become deadlocked. For more information on configuring JacORB please reference the JacORB documentation.

Note

JacORB comes with its own implementation of the classes defined in the CosTransactions.idl file. Unfortunately these are incompatible with the version shipped with JBoss Transaction Service. Therefore, the JBoss Transaction Service JAR files must appear in the CLASSPATH before any JacORB JARs.
The recovery manager must always use the same well-known port for each machine on which it runs. You should not use the OAPort property provided by JacORB unless the recovery manager has its own jacorb.properties file or the port is provided on the command line when starting the recovery manager. If the recovery manager and other components of JBoss Transaction Service share the same jacorb.properties file, then you should use the com.arjuna.ats.jts.recoveryManagerPort and com.arjuna.ats.jts.recoveryManagerAddress properties.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

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

让开源更具包容性

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

關於紅帽

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

Theme

© 2025 Red Hat