user manual

404 BES Developer’s Guide
Partition Transaction Service (Transaction Manager)
Partition Transaction Service (Transaction Manager)
Listed below are properties that influence the behavior of the Partition
Transaction Service (Transaction Manager). The properties can be specified
when hosted by either a standalone EJB container or a Partition.
When configuring the Partition Transaction Service for a Partition, set the
properties in the partition.xml file which is located in the <install_dir>/var/
domains/base/configurations/<configuration_name>/mos/<partition_name>/adm/
properties.
If running an EJB container standalone, they must be specified using system
property names described below in section titled JTS System Properties. For
example, when JTS is hosted by a standalone EJB Container property
jts.allow_unrecoverable_completion must be specified using its system property
equivalent:
prompt% vbj -DEJBAllowUnrecoverableCompletion com.inprise.ejb.Container
ejbcontainer beans.jar -jns -jts
Property Description Default
jts.allow_unrecoverable_co
mpletion=true|false
If set to true, this instructs the Container
built-in JTS implementation to do a non-
recoverable (that is, non two-phase)
completion when there are multiple
Resource registrations. Use at your own risk.
It is provided only as a developer friendly
feature.
False
jts.no_global_tids=true|
false
By default, JTS generates X/Open XA
compatible transaction identifiers. By setting
this property to true, the transaction key
generation behavior changes to generate
non-XA compliant tids. By generating XA
compliant properties out of the box, the EJB
container can work with JDBC2/XA drivers
seamlessly.
False
jts.no_local_tids=true|
false
There is an optimization where the EJB
container detects that a transaction was
started in the transaction service that lives in
the same VM, and make the transaction
comparision faster. Setting this property to
true turns that off. This local transaction
identifier (local tid) is a subset of the global
transaction id hence makes the transaction
comparisons faster.
False
jts.timeout_enable=true|
false
By default, JTS transaction timeout facility is
disabled. When enabled, each new
transaction created by JTS will registered
with a timeout in the JTS Timeout Manager.
If the timeout expires before completion of
the transaction, JTS will automatically
rollback the transaciton.
False