diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2015-02-17 17:25:57 +0000 |
|---|---|---|
| committer | <> | 2015-03-17 16:26:24 +0000 |
| commit | 780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch) | |
| tree | 598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/programmer_reference/xa_xa_restrict.html | |
| parent | 7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff) | |
| download | berkeleydb-master.tar.gz | |
Diffstat (limited to 'docs/programmer_reference/xa_xa_restrict.html')
| -rw-r--r-- | docs/programmer_reference/xa_xa_restrict.html | 104 |
1 files changed, 54 insertions, 50 deletions
diff --git a/docs/programmer_reference/xa_xa_restrict.html b/docs/programmer_reference/xa_xa_restrict.html index 9f1292a2..9c44bd39 100644 --- a/docs/programmer_reference/xa_xa_restrict.html +++ b/docs/programmer_reference/xa_xa_restrict.html @@ -14,7 +14,7 @@ <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> @@ -22,9 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="xa_xa_config.html">Prev</a> </td> - <th width="60%" align="center">Chapter 13. - Distributed Transactions - </th> + <th width="60%" align="center">Chapter 13. Distributed Transactions </th> <td width="20%" align="right"> <a accesskey="n" href="xa_faq.html">Next</a></td> </tr> </table> @@ -38,84 +36,90 @@ </div> </div> </div> - <p> - When you are using Berkeley DB for XA transactions, there are a few - restrictions you should be aware of: + <p> + When you are using Berkeley DB for XA transactions, there + are a few restrictions you should be aware of: </p> <div class="itemizedlist"> <ul type="disc"> <li> <p> - Configure environment using the <a href="../api_reference/C/configuration_reference.html" class="olink">DB_CONFIG</a> file + Configure environment using the <a href="../api_reference/C/configuration_reference.html" class="olink">DB_CONFIG</a> file </p> - <p> - For most options, you must configure your environment via - the <a href="../api_reference/C/configuration_reference.html" class="olink">DB_CONFIG</a> file because an XA application or server cannot - control the environment creation. + <p> + For most options, you must configure your + environment via the <a href="../api_reference/C/configuration_reference.html" class="olink">DB_CONFIG</a> file because an XA + application or server cannot control the environment + creation. </p> </li> <li> - <p> - Snapshot isolation must be configured for the entire - environment. + <p> + Snapshot isolation must be configured for the + entire environment. </p> - <p> - Transactions managed by the Berkeley DB X/open compliant XA - resource manager can be configured for transaction - snapshots using either database open flags or the <a href="../api_reference/C/configuration_reference.html" class="olink">DB_CONFIG</a> file - file. To configure using database open flags, open the XA - managed database with the flag <a href="../api_reference/C/dbopen.html#dbopen_DB_MULTIVERSION" class="olink">DB_MULTIVERSION</a>. When using - DB_CONFIG, include both of the following lines: + <p> + Transactions managed by the Berkeley DB X/open + compliant XA resource manager can be configured for + transaction snapshots using either database open flags + or the <a href="../api_reference/C/configuration_reference.html" class="olink">DB_CONFIG</a> file file. To configure using database + open flags, open the XA managed database with the flag + <a href="../api_reference/C/dbopen.html#dbopen_DB_MULTIVERSION" class="olink">DB_MULTIVERSION</a>. When using DB_CONFIG, include both + of the following lines: </p> <pre class="programlisting">set_flags DB_MULTIVERSION set_flags DB_TXN_SNAPSHOT</pre> - <p> - Note that both methods will results in all transactions - using transaction snapshots, there is no way to enable - transaction snapshots in just a subset of XA managed - transactions. + <p> + Note that both methods will results in all + transactions using transaction snapshots, there is no + way to enable transaction snapshots in just a subset + of XA managed transactions. </p> </li> <li> - <p>No in-memory logging</p> <p> - Upon return from xa_open, Berkeley DB checks to ensure - there is no in-memory logging. If in-memory logging is - detected, a FAILURE message is returned to the application. + No in-memory logging + </p> + <p> + Upon return from xa_open, Berkeley DB checks to + ensure there is no in-memory logging. If in-memory + logging is detected, a FAILURE message is returned to + the application. </p> </li> <li> <p> - No application-level child transactions + No application-level child transactions </p> - <p> - Berkeley DB verifies in the xa_start and xa_end calls that no - XA transaction has a parent. If application-level child - transactions are detected, a FAILURE message is returned to the - application. + <p> + Berkeley DB verifies in the xa_start and xa_end + calls that no XA transaction has a parent. If + application-level child transactions are detected, a + FAILURE message is returned to the application. </p> </li> <li> - <p> - All database-level operations, such as create, rename, and - remove, must be performed in local BDB transactions, not - distributed XA transactions + <p> + All database-level operations, such as create, + rename, and remove, must be performed in local BDB + transactions, not distributed XA transactions </p> - <p> + <p> Berkeley DB checks that there is no XA transaction - currently active during these operations, and if detected, - a FAILURE message is returned to the application. + currently active during these operations, and if + detected, a FAILURE message is returned to the + application. </p> </li> <li> <p> - Close cursors before a service invocation returns + Close cursors before a service invocation returns </p> - <p> - Berkeley DB checks in the <code class="literal">xa_end</code> call - that the <code class="literal">DB_TXN</code> has no active cursors - open and and if detected, a FAILURE message is returned to - the application. + <p> + Berkeley DB checks in the <code class="literal">xa_end</code> + call that the <code class="literal">DB_TXN</code> has no active + cursors open and and if detected, a FAILURE message is + returned to the application. </p> </li> </ul> |