ObjectDB Database Search

a rollback only transaction (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:271) at javax ... an active transaction as rollback only. In that case - you can only close the transaction with rollback not with commit . Maybe your application caught the exception and then tried to commit. support

(Exception e) { if (transaction.isActive()) transaction. rollback (); throw e; } finally ... , the persistence provider must mark the transaction for rollback . Parameters: function - the function Returns ... locking failure causes transaction-level rollback the LockTimeoutException is thrown if the database

, the transaction is marked for rollback , and no more callback methods for that operation are invoked. Listeners

, and the database locking failure results in transaction-level rollback , the provider must throw the PessimisticLockException and ensure that the JTA transaction or EntityTransaction has been marked for rollback ... rollback , the provider must throw the LockTimeoutException (and must not mark the transaction

whether the current resource transaction has been marked for rollback . Returns: boolean indicating whether the transaction has been marked for rollback . Throws: IllegalStateException - if isActive is false ... error condition is encountered. Since: Jakarta Persistence (JPA) 1.0 void rollback () Roll

transaction rollback . This exception may be thrown as part of an API call, at, flush or at commit time. The current transaction, if one is active, will be not be marked for rollback . Since: Jakarta Persistence

function throws an exception, the JTA transaction is marked for rollback , and the exception ... . If the given function throws an exception, the JTA transaction is marked for rollback , and the exception

. The current transaction, if one is active, will be marked for rollback . If the entity already exists ... , if one is active and the persistence context has been joined to it, will be marked for rollback

, is marked for rollback . Since: Jakarta Persistence (JPA) 2.0 Public Constructors

and the persistence context has been joined to it, will be marked for rollback . See Also: EntityManager

.getTransaction(). rollback (); em.close(); } } @Override protected void doPost( HttpServletRequest request

: Attempt to rollback a transaction when no transaction is active at com.objectdb.o.JPE.g(JPE.java:73 ... .BaseTransaction. rollback (BaseTransaction.java:134) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate. rollback (BaseTransactionManagerDelegate.java:114) at org.jboss.as.ejb3.tx.CMTTxInterceptor

.getTransaction(). rollback ();            

().commit(); } finally { if (em.getTransaction().isActive()) { em.getTransaction(). rollback (); } em

(). rollback ();             }       

constructor and we are still in the same transaction (before any commit or rollback ). In the debugger

the persistence by reachability rule. Of course, if the transaction is ended with rollback () and not with commit

().isActive()) updateEm.getTransaction(). rollback () ; updateEm.close() ; if (em.getTransaction().isActive()) em.getTransaction(). rollback () ; em.close() ; ioan.bodnar Bodnar Ciprian Apparently

().commit(); } catch(Exception e) { if(em.getTransaction().isActive()) em.getTransaction(). rollback