Transaction-manager
From Resin 3.0
(Difference between revisions)
Line 12: | Line 12: | ||
{{:transaction-log}} | {{:transaction-log}} | ||
+ | |||
+ | == example == | ||
+ | |||
+ | <resin xmlns="http://caucho.com/ns/resin"> | ||
+ | |||
+ | <transaction-manager> | ||
+ | <transaction-log> | ||
+ | <path>xalog/xa.log</path> | ||
+ | </transaction-log> | ||
+ | </transaction-manager> | ||
+ | |||
+ | .... | ||
+ | </resin> |
Revision as of 19:24, 13 February 2006
The <transaction-manager> tag configures the distributed transaction manager.
tag | description |
---|---|
<transaction-log> | configures the transaction log |
transaction-log
tag | description |
---|---|
path | path to the transaction log |
The transaction log saves the state of every transaction handled by the transaction manager. It is configured as part of <transaction-manager>. In the case of an unexpected or unclean server shutdown, Resin will use the transaction log to properly rollback uncompleted transactions in the database.
example
<resin xmlns="http://caucho.com/ns/resin"> <transaction-manager> <transaction-log> <path>xalog/xa.log</path> </transaction-log> </transaction-manager> .... </resin>