web server - Borland Technical Publications
web server - Borland Technical Publications
web server - Borland Technical Publications
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Partition Transaction Service (Transaction Manager)<br />
For example, when JTS is hosted by a standalone EJB Container property<br />
jts.allow_unrecoverable_completion must be specified using its system property<br />
equivalent:<br />
prompt% vbj -DEJBAllowUnrecoverableCompletion com.inprise.ejb.Container<br />
ejbcontainer beans.jar -jns -jts<br />
Property Description Default<br />
jts.allow_unrecoverable_co<br />
mpletion=true|false<br />
jts.no_global_tids=true|<br />
false<br />
jts.no_local_tids=true|<br />
false<br />
jts.timeout_enable=true|<br />
false<br />
jts.timeout_interval=<br />
jts.default_timeout=<br />
jts.default_max_timeout=<br />
jts.trace=true|false<br />
jts.transaction_debug_time<br />
out=<br />
If set to true, this instructs the Container built-in<br />
JTS implementation to do a non-recoverable (that<br />
is, non two-phase) completion when there are<br />
multiple Resource registrations. Use at your own<br />
risk. It is provided only as a developer friendly<br />
feature. For OpenJMS, this property is set to true<br />
by default.<br />
By default, JTS generates X/Open XA compatible<br />
transaction identifiers. By setting this property to<br />
true, the transaction key generation behavior<br />
changes to generate non-XA compliant tids. By<br />
generating XA compliant properties out of the box,<br />
the EJB container can work with JDBC2/XA<br />
drivers seamlessly.<br />
There is an optimization where the EJB container<br />
detects that a transaction was started in the<br />
transaction service that lives in the same VM, and<br />
make the transaction comparison faster. Setting<br />
this property to true turns that off. This local<br />
transaction identifier (local tid) is a subset of the<br />
global transaction id hence makes the transaction<br />
comparisons faster.<br />
By default, JTS transaction timeout facility is<br />
disabled. When enabled, each new transaction<br />
created by JTS will registered with a timeout in the<br />
JTS Timeout Manager. If the timeout expires<br />
before completion of the transaction, JTS will<br />
automatically rollback the transaction.<br />
The JTS Timeout Manager examines registered<br />
transactions for timeout expiration at intervals in<br />
seconds controlled by the value of this property.<br />
Setting it to a value of 0 causes the interval to<br />
occur every 9999 seconds.<br />
The timeout period for a Bean Managed<br />
transaction can be configured using JTA<br />
UserTransaction setTransactionTimeout() method. If<br />
not used or if transaction is a Container Managed<br />
transaction, the default transaction timeout value<br />
is applied. This can be configured upon JTS<br />
startup using the jts.default_timeout property<br />
value. The granularity of this property is 1 second.<br />
To prevent specification of an excessive timeout<br />
value for the jts.default_timeout property, the<br />
jts.default_max_timeout property controls the<br />
maximum time a transaction can be active before<br />
its expired. The granularity of this property is 1<br />
second.<br />
Set this property to generate JTS debug<br />
messages.<br />
If set, this property displays a list of active<br />
transactions maintained by JTS. Its value dictates<br />
the interval in seconds at which transactions are<br />
displayed.<br />
False<br />
False<br />
False<br />
False<br />
5<br />
600<br />
3600<br />
False<br />
None<br />
350 BES Developer’s Guide
Change language