Examples of TransactionManager

co.cask.tephra.TransactionManager
This is the central place to manage all active transactions in the system. A transaction consists of
- A write pointer: This is the version used for all writes of that transaction.
- A read pointer: All reads under the transaction use this as an upper bound for the version.
- A set of excluded versions: These are the write versions of other transactions that must be excluded from reads, because those transactions are still in progress, or they failed but couldn't be properly rolled back.
To use the transaction system, a client must follow this sequence of steps:
1. Request a new transaction.
2. Use the transaction to read and write datasets. Datasets are encouraged to cache the writes of the transaction in memory, to reduce the cost of rollback in case the transaction fails.
3. Check whether the transaction has conflicts. For this, the set of change keys are submitted via canCommit(), and the transaction manager verifies that none of these keys are in conflict with other transactions that committed since the start of this transaction.
4. If the transaction has conflicts:
  1. Roll back the changes in every dataset that was changed. This can happen in-memory if the changes were cached.
  2. Abort the transaction to remove it from the active transactions.
5. If the transaction has no conflicts:
Transactions may be short or long-running. A short transaction is started with a timeout, and if it is not committed before that timeout, it is invalidated and excluded from future reads. A long-running transaction has no timeout and will remain active until it is committed or aborted. Long transactions are typically used in map/reduce jobs and can produce enormous amounts of changes. Therefore, long transactions do not participate in conflict detection (they would almost always have conflicts). We also assume that the changes of long transactions are not tracked, and therefore cannot be rolled back. Hence, when a long transaction is aborted, it remains in the list of excluded transactions to make its writes invisible.
com.alu.e3.common.transaction.TransactionManager
com.arjuna.mw.wst.TransactionManager
This is the interface that the core exposes in order to allow different types of participants to be enrolled. The messaging layer continues to work in terms of the registrar, but internally we map to one of these methods. This could also be the interface that high-level users see (e.g., at the application Web Service). As with UserTransaction a TransactionManager does not represent a specific transaction, but rather is responsible for providing access to an implicit per-thread transaction context. @author Mark Little (mark.little@arjuna.com) @version $Id: TransactionManager.java,v 1.10.6.1 2005/11/22 10:36:06 kconner Exp $ @since XTS 1.0.
com.arjuna.mw.wst11.TransactionManager
This is the interface that the core exposes in order to allow different types of participants to be enrolled. The messaging layer continues to work in terms of the registrar, but internally we map to one of these methods. This could also be the interface that high-level users see (e.g., at the application Web Service). As with UserTransaction a TransactionManager does not represent a specific transaction, but rather is responsible for providing access to an implicit per-thread transaction context. @author Mark Little (mark.little@arjuna.com) @version $Id: TransactionManager.java,v 1.10.6.1 2005/11/22 10:36:06 kconner Exp $ @since XTS 1.0.
com.arjuna.mw.wstx.TransactionManager
This is the service side component of the user interface. Since services or some entity acting on their behalf (e.g., an interceptor) must enlist participants with the transaction, this interface primarily concentrates on those methods. However, a service may well not be the final destination for a transaction, i.e., in order to perform its work, the service may have to make other remote invocations on other services and propagate the context, suspend it, etc. As such, all of the UserTransaction methods are also available to the service. @author Mark Little (mark.little@arjuna.com) @version $Id: TransactionManager.java,v 1.1 2002/11/25 11:00:51 nmcl Exp $ @since 1.0.
com.avaje.ebeaninternal.server.transaction.TransactionManager
Manages transactions.
Keeps the Cache and Cluster in synch when transactions are committed.
com.bekvon.bukkit.residence.economy.TransactionManager
@author Administrator
com.caucho.server.admin.TransactionManager
Configures the transaction manager.
com.hp.hpl.jena.tdb.transaction.TransactionManager
com.ibatis.sqlmap.engine.transaction.TransactionManager
com.j256.ormlite.misc.TransactionManager
te both objects but make sure that if either one fails, the transaction is rolled back // and both objects are "restored" to the database fooDao.delete(foo); barDao.delete(bar); return null; } });
For Spring wiring of a Transaction Manager bean, we would do something like the following:
```
 <bean id="transactionManager" class="com.j256.ormlite.misc.TransactionManager" init-method="initialize"> <property name="dataSource" ref="dataSource" /> </bean> 
```
@author graywatson
com.scooterframework.transaction.TransactionManager
TransactionManager interface specified services that are related to managing a transaction. @author (Fei) John Chen
com.sun.enterprise.ee.synchronization.tx.TransactionManager
Transaction Manager coordinates sync transaction across request threads @author Satish Viswanatham @since JDK1.4
com.yahoo.omid.client.TransactionManager
Provides the methods necessary to create and commit transactions. @see TransactionalTable
javax.transaction.TransactionManager
@version $Rev: 46019 $ $Date: 2004-09-14 03:56:06 -0600 (Tue, 14 Sep 2004) $
jdbm.recman.TransactionManager
This class manages the transaction log that belongs to every {@link RecordFile}. The transaction log is either clean, or in progress. In the latter case, the transaction manager takes care of a roll forward.
Implementation note: this is a proof-of-concept implementation which hasn't been optimized for speed. For instance, all sorts of streams are created for every transaction.
jifx.transactionManager.TransactionManager
The Transaction Manager has the responsibility of solving all the incoming requests from a client through an specific channel, and to assign the work to the corresponding entity in a transactional way.
net.hasor.db.transaction.TransactionManager
数据源的事务管理器。 @version : 2013-10-30 @author 赵永春(zyc@hasor.net)
net.jini.core.transaction.server.TransactionManager
The interface used for managers of the two-phase commit protocol for top-level transactions. All ServerTransaction objects are governed by a transaction manager that runs this protocol. @author Sun Microsystems, Inc. @see NestableTransactionManager @see ServerTransaction @see TransactionParticipant @since 1.0
net.sourceforge.peers.sip.transaction.TransactionManager
org.apache.cayenne.tx.TransactionManager
An optional utility service that simplifies wrapping multiple operations in transactions. Users only rarely need to invoke it directly, as all standard Cayenne operations are managing their own transactions internally. @since 3.2
org.apache.derby.iapi.store.access.conglomerate.TransactionManager
The TransactionManager interface provides methods on the transaction needed by an access method implementer, but should not be visible to clients of a TransactionController.
@see TransactionController
org.apache.hadoop.hbase.client.transactional.TransactionManager
Transaction Manager. Responsible for committing transactions.
org.apache.torque.util.TransactionManager
Torque's interface to the transaction management system. @version $Id: TransactionManager.java 1448414 2013-02-20 21:06:35Z tfischer $
org.axonframework.unitofwork.TransactionManager
Interface towards a mechanism that manages transactions
Typically, this will involve opening database transactions or connecting to external systems. @param < T> The type of object used to represent the transaction @author Allard Buijze @since 2.0
org.castor.jdo.conf.TransactionManager
org.cipango.server.transaction.TransactionManager
org.datanucleus.transaction.TransactionManager
TransactionManager is facade for creating (Open/XA) transactions. A cache of transactions is held with each transaction for a user object. If using with a multithreaded PM/EM then you must lock access external to TransactionManager since this is for a PMF/EMF.
org.drools.persistence.TransactionManager
org.exist.storage.txn.TransactionManager
This is the central entry point to the transaction management service. There's only one TransactionManager per database instance that can be retrieved via {@link BrokerPool#getTransactionManager()}. TransactionManager provides methods to create, commit and rollback a transaction. @author wolf
org.exolab.castor.jdo.conf.TransactionManager
Class TransactionManager. @version $Revision: 1.1 $ $Date: 2004/03/25 08:59:10 $
org.fto.jthink.transaction.TransactionManager
... ... ... ... transactionManager.commit(); }catch(Exception e){ transactionManager.rollback(); throw e; }finally{ transactionManager.close(); } ... ... 无更新操作，只有查询操作的情况 ... ... try{ transactionManager.begin(); ... ... ... ... }finally{ transactionManager.close(); } ... ...
```
 历史更新记录: 2005-06-23  创建此类型 
```
@author wenjian @version 1.0 @since JThink 1.0 @see org.fto.jthink.resource.ResourceContainer @see org.fto.jthink.transaction.TransactionManager
org.g4studio.core.orm.xibatis.sqlmap.engine.transaction.TransactionManager
org.jboss.as.console.client.shared.subsys.tx.model.TransactionManager
@author Heiko Braun @date 10/25/11
org.jpos.transaction.TransactionManager
org.jpox.transaction.TransactionManager
TransactionManager is facade for creating (Open/XA) transactions A cache of transactions is held per userObject
org.jtester.core.context.TransactionManager
测试方法的的事务管理
事务是方法级别的（可能有多线程测试） @author darui.wudr
org.openstreetmap.osmosis.apidb.v0_6.impl.TransactionManager
Obtains transaction snapshots used for replication.
org.socialmusicdiscovery.server.business.logic.TransactionManager
Interface that represents a transaction manager which manage the transaction but also makes sure the {@link javax.persistence.EntityManager} instance for the current context is in the appropriate state
sg.edu.nus.iss.se07.bc.TransactionManager
ChangeLog 6 April 2009 - Isak Rabin 1) Remove all static keyword from method 2) Remove all @annotation 3) Access to TransactionDA through its instance

Examples of javax.transaction.TransactionManager

   }


   public void testIgnoreModsTransactional() throws Exception
   {
      startCache(false, true);
      TransactionManager mgr = cache.getTransactionManager();


      // initialise the loaders
      loader1.put(fqn, key, value);
      loader2.put(fqn, key, value);


      // check contents
      assertEquals(value, cache.get(fqn, key));
      assertEquals(value, chainingCacheLoader.get(fqn).get(key));
      assertEquals(value, loader1.get(fqn).get(key));
      assertEquals(value, loader2.get(fqn).get(key));


      // do a put
      mgr.begin();
      cache.put(fqn, key, value + 2);
      assertEquals(value + 2, cache.get(fqn, key));
      assertEquals(value, chainingCacheLoader.get(fqn).get(key));
      assertEquals(value, loader1.get(fqn).get(key));
      assertEquals(value, loader2.get(fqn).get(key));
      mgr.commit();
      assertEquals(value + 2, cache.get(fqn, key));
      assertEquals(value + 2, chainingCacheLoader.get(fqn).get(key));
      assertEquals(value + 2, loader1.get(fqn).get(key));
      assertEquals(value, loader2.get(fqn).get(key));

View Full Code Here

Examples of javax.transaction.TransactionManager

   }


   public void testCrudsTransactional() throws Exception
   {
      startCache(false, false);
      TransactionManager mgr = cache.getTransactionManager();


      // assert that the loaders ae empty
      chainingCacheLoader.remove(cache.getRoot().getFqn());
      assertNull(loader1.get(fqn));
      assertNull(loader2.get(fqn));
      assertNull(chainingCacheLoader.get(fqn));


      // put something in the cache.
      mgr.begin();
      cache.put(fqn, key, value);
      assertEquals(value, cache.get(fqn, key));
      assertNull(chainingCacheLoader.get(fqn));
      assertNull(loader1.get(fqn));
      assertNull(loader2.get(fqn));
      mgr.commit();
      assertEquals(value, cache.get(fqn, key));
      assertEquals(value, chainingCacheLoader.get(fqn).get(key));
      assertEquals(value, loader1.get(fqn).get(key));
      assertEquals(value, loader2.get(fqn).get(key));

View Full Code Here

Examples of javax.transaction.TransactionManager

   }


   public void testSyncTxRepl() throws Exception
   {
      Integer age;
      TransactionManager tm = cache1.getTransactionManager();


      tm.begin();
      Transaction tx = tm.getTransaction();
      Listener lis = new Listener();
      cache1.getNotifier().addCacheListener(lis);
      lis.put("/a/b/c", "age", 38);


      tm.suspend();
      assertNull("age on cache2 must be null as the TX has not yet been committed", cache2.get("/a/b/c", "age"));
      tm.resume(tx);
      tm.commit();


      // value on cache2 must be 38
      age = (Integer) cache2.get("/a/b/c", "age");
      assertNotNull("\"age\" obtained from cache2 must be non-null ", age);
      assertTrue("\"age\" must be 38", age == 38);

View Full Code Here

Examples of javax.transaction.TransactionManager

   }


   public void testSyncTxReplMap() throws Exception
   {
      Integer age;
      TransactionManager tm = cache1.getConfiguration().getRuntimeConfig().getTransactionManager();
      tm.begin();
      Transaction tx = tm.getTransaction();
      Listener lis = new Listener();
      cache1.getNotifier().addCacheListener(lis);
      Map<String, Comparable> map = new HashMap<String, Comparable>();
      map.put("age", 38);
      map.put("name", "Ben");
      lis.put("/a/b/c", map);
      tm.suspend();
      assertNull("age on cache2 must be null as the TX has not yet been committed", cache2.get("/a/b/c", "age"));
      tm.resume(tx);
      tm.commit();


      // value on cache2 must be 38
      age = (Integer) cache2.get("/a/b/c", "age");
      assertNotNull("\"age\" obtained from cache2 must be non-null ", age);
      assertTrue("\"age\" must be 38", age == 38);

View Full Code Here

Examples of javax.transaction.TransactionManager

      }
   }


   private void destroyCache(CacheSPI c)
   {
      TransactionManager tm = c.getTransactionManager();
      try
      {
         if (tm != null && tm.getTransaction() != null)
            tm.rollback();
      }
      catch (Exception e)
      {
      }
      c.stop();

View Full Code Here

Examples of javax.transaction.TransactionManager

   {
      DataVersion version = new TestVersion("99");
      cache[0].getInvocationContext().getOptionOverrides().setDataVersion(version);
      cache[0].put(fqn, key, "value");// TestVersion-99 should be on both caches now


      TransactionManager mgr = cache[0].getTransactionManager();
      mgr.begin();
      // don't explicitly set a data version.


      // force an IC scrub
      //cache[1].getInvocationContext().setOptionOverrides(null);
      cache[1].put(fqn, key, "value2");
      try
      {
         mgr.commit();


         assertTrue("expected to fail", false);
      }
      catch (RollbackException e)
      {

View Full Code Here

Examples of javax.transaction.TransactionManager

   {
      DataVersion version = new TestVersion("99");
      cache[0].getInvocationContext().getOptionOverrides().setDataVersion(version);
      cache[0].put(fqn, key, "value");// TestVersion-99 should be on both caches now


      TransactionManager mgr = cache[0].getTransactionManager();
      mgr.begin();


      version = new TestVersion("999");
      cache[1].getInvocationContext().getOptionOverrides().setDataVersion(version);
      cache[1].put(fqn, key, "value2");
      mgr.commit();
   }

View Full Code Here

Examples of javax.transaction.TransactionManager

   {
      DataVersion version = new TestVersion("99");
      cache[0].getInvocationContext().getOptionOverrides().setDataVersion(version);
      cache[0].put(fqn, key, "value");// TestVersion-99 should be on both caches now


      TransactionManager mgr = cache[0].getTransactionManager();
      mgr.begin();


      version = new TestVersion("29");
      cache[1].getInvocationContext().getOptionOverrides().setDataVersion(version);
      cache[1].put(fqn, key, "value2");
      try
      {
         mgr.commit();
         assertTrue("expected to fail", false);
      }
      catch (RollbackException e)
      {
         // should fail.

View Full Code Here

Examples of javax.transaction.TransactionManager

    */
   public void testIncompatibleVersionTypes2() throws Exception
   {
      cache[0].put(fqn, key, "value");// default data version should be on both caches now


      TransactionManager mgr = cache[0].getTransactionManager();
      mgr.begin();


      // explicitly set data version
      DataVersion version = new TestVersion("99");
      cache[1].getInvocationContext().getOptionOverrides().setDataVersion(version);


      try
      {
         cache[1].put(fqn, key, "value2");
         mgr.commit();
         assertTrue("expected to fail", false);
      }
      catch (Exception e)
      {
         // should fail.

View Full Code Here

Examples of javax.transaction.TransactionManager

    */
   public void testCompatibleVersionTypes2() throws Exception
   {
      cache[0].put(fqn, key, "value");// TestVersion-99 should be on both caches now


      TransactionManager mgr = cache[0].getTransactionManager();
      mgr.begin();


      DataVersion version = new DefaultDataVersion(300);
      cache[1].getInvocationContext().getOptionOverrides().setDataVersion(version);
      cache[1].put(fqn, key, "value2");
      mgr.commit();
   }

View Full Code Here

0 1 2 3 4 5 6 7 8

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.