no type hierarchy
no supertypes hierarchy
no subtypes hierarchy
Recovery scans run periodically (the default is every 2 minutes). You may manually force an immediate recovery scan. A recovery scan attempts recovery on each entry in the transaction logs managed by this recovery manager instance
Start and initialize an instance of a transaction recovery manager.
There must be exactly one recovery service per set of transaction logs, so it is recommended that the recovery service runs in a dedicated process whenever multiple processes share the same set of transaction logs.
Stop this transaction recovery manager.
Return a list of XA capable JDBC drivers that are known to work correctly with the transaction manager. Some drivers, even though they support XA, are not fully compliant so recovery is not guaranteed under all scenarios. If an unsupported driver is used then we recommend exhaustive testing. Drivers that are known to work correctly include:
org.postgresql.Driver, oracle.jdbc.driver.OracleDriver, com.microsoft.sqlserver.jdbc.SQLServerDriver, com.mysql.jdbc.Driver, com.ibm.db2.jcc.DB2Driver, com.sybase.jdbc3.jdbc.SybDriver
|Methods inherited from: |