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
libdirectory of the JDK used to run your application. This is retrieved usingSystem.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.
