About transaction

141-150 of 200Refresh
JPA Doc
4

refresh(entity, lockMode)

locking failure causes transaction-level rollback the LockTimeoutException will be thrown ... is not managed TransactionRequiredException - if there is no transaction and if invoked on a container-managed EntityManager instance with PersistenceContextType.TRANSACTION or with a lock mode
JPA Doc
4

refresh(entity, lockMode, properties)

but cannot be locked: the PessimisticLockException will be thrown if the database locking failure causes transaction ... managed TransactionRequiredException - if there is no transaction and if invoked on a container-managed EntityManager instance with PersistenceContextType.TRANSACTION or with a lock mode
Issue
4

Unexpected exception (Error 990) com.objectdb.o.InternalException

$AjcClosure27.run(PatternApplicationServiceImpl.java:1) at com.btc.ep.base.transactions.annotations.TransactionAspect.ajc$around$com_btc_ep_base_transactions_annotations_TransactionAspect$1$adc4043cproceed(TransactionAspect.aj:90) at com.btc.ep.base.transactions.annotations.TransactionAspect.ajc
JDO Doc
4

checkConsistency()

with the datastore. This method has no effect if a transaction is not active. If a datastore transaction is active, this method verifies the consistency of instances in the cache against the datastore ... to do so. If an optimistic transaction is active, this method obtains a datastore connection and verifies
JDO Doc
4

Constants.TX_REPEATABLE_READ

Static Field javax.jdo.Constants String TX_REPEATABLE_READ Transaction isolation level representing the requirement to read the same data in the same transaction. Since: JDO 2.2 See Also: PersistenceManagerFactory.getTransactionIsolationLevel() Transaction.getIsolationLevel()
JDO Doc
4

Constants.TX_SERIALIZABLE

Static Field javax.jdo.Constants String TX_SERIALIZABLE Transaction isolation level representing the requirement to serialize transactions. Since: JDO 2.2 See Also: PersistenceManagerFactory.getTransactionIsolationLevel() Transaction.getIsolationLevel()
JPA Doc
4

find(entityClass, primaryKey, lockMode)

locking failure causes transaction-level rollback the LockTimeoutException will be thrown ... TransactionRequiredException - if there is no transaction and a lock mode other than NONE is specified ... fails and the transaction is rolled back LockTimeoutException - if pessimistic locking fails
JPA Doc
4

find(entityClass, primaryKey, lockMode, properties)

: the PessimisticLockException will be thrown if the database locking failure causes transaction-level ... TransactionRequiredException - if there is no transaction and a lock mode other than NONE is specified ... and the transaction is rolled back LockTimeoutException - if pessimistic locking fails
JPA Doc
4

find(entityClass, primaryKey, lockMode, properties)

but cannot be locked: the PessimisticLockException will be thrown if the database locking failure causes transaction ... TransactionRequiredException - if there is no transaction and a lock mode other than NONE is specified ... locking fails and the transaction is rolled back LockTimeoutException - if pessimistic locking fails
JPA Doc
4

getResultList()

back TransactionRequiredException - if a lock mode has been set and there is no transaction PessimisticLockException - if pessimistic locking fails and the transaction is rolled back LockTimeoutException - if pessimistic ... exceeds the query timeout value set and the transaction is rolled back Since: JPA 1.0