JBoss.orgCommunity Documentation

Chapter 5. ORB-specific Configurations

5.1. JacORB

5.1. JacORB

For JacORB to function correctly it needs a valid jacorb.properties or .jacorb_properties file in one of the following places, in searched order:

  1. The classpath

  2. The home directory of the user running the JBoss Transaction Service. The home directory is retrieved using System.getProperty( “user.home” );

  3. The current directory

  4. The lib/ directory of the JDK used to run your application. This is retrieved using System.getProperty(“java.home” );

Note

A template jacorb.properties file is located in the JacORB installation directory.

Within the JacORB properties file there are two important properties which must be tailored to suit your application.

These properties specify the minimum and maximum number of request processing threads that JacORB uses in its thread pool. If no threads are available, may block until a thread becomes available.. For more information on configuring JacORB, refer to the JacORB documentation.

Important

JacORB includes its own implementation of the classes defined in the CosTransactions.idl file. Unfortunately these are incompatible with the version shipped with JBossTS. Therefore, the JBossTS jar files absolutely must appear in the CLASSPATH before any JacORB jars.

When running the recovery manager, it should always uses the same well-known port for each machine on which it runs. Do not use the OAPort property provided by JacORB unless the recovery manager has its own jacorb.properties file or the property is provided on the command line when starting the recovery manager. If the recovery manager and other components of JBossTS share the same jacorb.properties file, use the JTSEnvironmentBean.recoveryManagerPort and JTSEnvironmentBean.recoveryManagerAddress properties.