Examples of commitNoSync()

• com.sleepycat.je.Transaction.commitNoSync()
  End the transaction, not writing to stable storage and not committing synchronously. This means the transaction will exhibit the ACI (atomicity, consistency, and isolation) properties, but not D (durability); that is, database integrity will be maintained, but it is possible this transaction may be undone during recovery.

  This behavior may be set for a database environment using the {@link com.sleepycat.je.EnvironmentConfig#setTxnNoSync EnvironmentConfig.setTxnNoSync} method or for a single transaction usingthe {@link com.sleepycat.je.Environment#beginTransaction Environment.beginTransaction} method. Any value specified to thismethod overrides both of those settings.

  All cursors opened within the transaction must be closed before the transaction is committed.

  If the method encounters an error, the transaction will have been aborted when the call returns.

  After this method has been called, regardless of its return, the {@link Transaction} handle may not be accessed again, with oneexception: the {@code abort} method may be called any number of timesto simplify error handling.

  @throws com.sleepycat.je.rep.InsufficientReplicasException if the masterin a replicated environment could not contact enough replicas to initiate the commit. @throws com.sleepycat.je.rep.InsufficientAcksException if the master ina replicated environment did not receive enough replica acknowledgments, althought the commit succeeded locally. @throws com.sleepycat.je.rep.ReplicaWriteException if a write operationwas performed with this transaction, but this node is now a Replica. @throws OperationFailureException if this exception occurred earlier andcaused the transaction to be invalidated. @throws EnvironmentFailureException if an unexpected, internal orenvironment-wide failure occurs. @throws IllegalStateException if the transaction or environment has beenclosed, or cursors associated with the transaction are still open.
• org.apache.derby.iapi.store.access.TransactionController.commitNoSync()
  "Commit" this transaction without sync'ing the log. Everything else is identical to commit(), use this at your own risk.
  bits in the commitflag can turn on to fine tuned the "commit": KEEP_LOCKS - no locks will be released by the commit and no post commit processing will be initiated. If, for some reasons, the locks cannot be kept even if this flag is set, then the commit will sync the log, i.e., it will revert to the normal commit. READONLY_TRANSACTION_INITIALIZATION - Special case used for processing while creating the transaction. Should only be used by the system while creating the transaction to commit readonly work that may have been done using the transaction while getting it setup to be used by the user. In the future we should instead use a separate tranaction to do this initialization. Will fail if called on a transaction which has done any updates. @see TransactionController#commit @exception StandardException Only exceptions with severities greater thanExceptionSeverity.TRANSACTION_SEVERITY will be thrown. If an exception is thrown, the transaction will not (necessarily) have been aborted. The standard error handling mechanism is expected to do the appropriate cleanup. In other words, if commit() encounters an error, the exception is propagated up to the the standard exception handler, which initiates cleanupOnError() processing, which will eventually abort the transaction.
• org.apache.derby.iapi.store.access.conglomerate.TransactionManager.commitNoSync()
• org.apache.derby.iapi.store.raw.xact.RawTransaction.commitNoSync()

Examples of org.apache.derby.iapi.store.raw.xact.RawTransaction.commitNoSync()