Most of the configuration activities that you need to perform for your transactional BDB XML application will involve the locking and logging subsystems. See Concurrency and Managing BDB XML Files for details.
However, there are a couple of things that you can do to configure your transaction subsystem directly. These things are:
Configure the maximum number of simultaneous transactions needed by your application. In general, you should not need to do this unless you use deeply nested transactions or you have many threads all of which have active transactions. In addition, you may need to a higher maximum number of transactions if you are using snapshot isolation. See Snapshot Isolation Transactional Requirements for details.
By default, your application can support 20 active transactions.
You can set the maximum number of simultaneous transactions supported by your application using EnvironmentConfig.setTxnMaxActive().
If your application has exceeded this maximum value, then any attempt to begin a new transaction will fail.
This value can also be set using the DB_CONFIG file's set_tx_max parameter. Remember that the DB_CONFIG must reside in your environment home directory.
Configure the timeout value for your transactions. This value represents the longest period of time a transaction can be active. Note, however, that transaction timeouts are checked only when BDB XML examines its lock tables for blocked locks (see Locks, Blocks, and Deadlocks for more information). Therefore, a transaction's timeout can have expired, but the application will not be notified until BDB XML has a reason to examine its lock tables.
Be aware that some transactions may be inappropriately timed out before the transaction has a chance to complete. You should therefore use this mechanism only if you know your application might have unacceptably long transactions and you want to make sure your application will not stall during their execution. (This might happen if, for example, your transaction blocks or requests too much data.)
Note that by default transaction timeouts are set to 0 seconds, which means that they never time out.
To set the maximum timeout value for your transactions, use the EnvironmentConfig.setTxnTimeout() method. This method configures the entire environment; not just the handle used to set the configuration. Further, this value may be set at any time during the application's lifetime. (Use Environment.setConfig() to set this value after the environment has been opened.)
This value can also be set using the DB_CONFIG file's set_txn_timeout parameter.
For example:
package dbxml.txn;
import com.sleepycat.db.Environment;
import com.sleepycat.db.EnvironmentConfig;
import com.sleepycat.db.LockDetectMode;
import com.sleepycat.dbxml.XmlManager;
import com.sleepycat.dbxml.XmlManagerConfig;
import java.io.File;
...
Environment myEnv = null;
File envHome = new File("/export1/testEnv");
XmlManager myManager = null;
XmlContainer myContainer = null;
try {
EnvironmentConfig envConf = new EnvironmentConfig();
envConf.setAllowCreate(true); // If the environment does not
// exits, create it.
envConf.setInitializeCache(true); // Turn on the shared memory
// region.
envConf.setInitializeLocking(true); // Turn on the locking subsystem.
envConf.setInitializeLogging(true); // Turn on the logging subsystem.
envConf.setTransactional(true); // Turn on the transactional
// subsystem.
// Configure a maximum transaction timeout of 1 second.
myEnvConfig.setTxnTimeout(1000000);
// Configure 40 maximum transactions.
myEnv.setTxnMaxActive(40);
myEnv = new Environment(envHome, envConf);
XmlManagerConfig managerConfig = new XmlManagerConfig();
myManager = new XmlManager(myEnv, managerConfig);
// From here, you open your containers, proceed with your
// container operations, and respond to deadlocks as
// is normal (omitted for brevity).
...