The RollbackCause for an atomic block execution attempt that ended with
a call to retry or retryFor.
An ExternalDecider is given the final control over the decision of
whether or not to commit a transaction, which allows two-phase commit to
be integrated with a single non-transactional resource.
The RollbackCause for a NestingLevel whose optimistic execution was
invalid, and that should be retried.
RollbackCauses for which the failure is permanent and no attempt should
be made to retry the underlying atomic block.
A record of the reason that a atomic block execution attempt was rolled back.
The Status for an atomic block execution attempt that is being or that
has been cancelled.
The current state of an attempt to execute an atomic block.
RollbackCauses for which the failure is transient and another attempt
should be made to execute the underlying atomic block.
The RollbackCause for an atomic block that should not be restarted
because it threw an exception.
The Status for a transaction nesting level that may perform Ref reads
and writes, that is waiting for a child nesting level to complete, or
that has been merged into an Active parent nesting level.
The Status for the nesting levels of a transaction that has been
committed.
The Status for the nesting levels of a transaction that has decided to
commit, but whose Ref writes are not yet visible to other threads.
The Status for the nesting levels of a transaction that has
successfully acquired all write permissions necessary to succeed, and
that has delegated the final commit decision to an external decider.
The Status for the nesting levels of a transaction that are attempting
to commit, but for which the outcome is uncertain.
Arranges for handler to be executed as soon as possible after the
current transaction is committed, if this nesting level is part of the
overall transaction commit.
Arranges for handler to be executed as soon as possible after the
current transaction is committed, if this nesting level is part of the
overall transaction commit. Details:
Refs using a new top-level atomic block or .single;RolledBack or Committed.
Arranges for handler to be called as both an after-commit and
after-rollback handler.
Arranges for handler to be called as both an after-commit and
after-rollback handler.
Equivalent to:
afterRollback(handler) afterCommit(handler)
Arranges for handler to be executed as soon as possible after the
current nesting level is rolled back, or runs the handler immediately if
the current nesting level's status is already RolledBack.
Arranges for handler to be executed as soon as possible after the
current nesting level is rolled back, or runs the handler immediately if
the current nesting level's status is already RolledBack. Details:
Committed.
Arranges for handler to be executed as late as possible while the root
nesting level of the current transaction is still Active, unless the
current nesting level is rolled back.
Arranges for handler to be executed as late as possible while the root
nesting level of the current transaction is still Active, unless the
current nesting level is rolled back. Reads, writes and additional
nested transactions may be performed inside the handler. Details:
handler is run the transaction might still
be rolled back;beforeCommit from inside handler, the
reentrantly added handler will be included in this before-commit phase;
andReturns Some(t) if called from inside the static or dynamic scope of
the transaction context t, None otherwise.
Returns Some(t) if called from inside the static or dynamic scope of
the transaction context t, None otherwise. If an implicit InTxn is
available it may be used.
Rolls back the current nesting level for modular blocking.
Rolls back the current nesting level for modular blocking. It will be
retried, but only after some memory location observed by this transaction
has been changed. If any alternatives to this atomic block were provided
via orAtomic or atomic.oneOf, then the alternative will be tried
before blocking.
if the transaction is not active.
Causes the transaction to roll back and retry using modular blocking with a timeout, or returns immediately if the timeout has already expired.
Causes the transaction to roll back and retry using modular blocking with
a timeout, or returns immediately if the timeout has already expired.
The STM keeps track of the total amount of blocking that has occurred
during modular blocking; this time is apportioned among the calls to
View.tryAwait and retryFor that are part of the current attempt.
retryFor(0) is a no-op.
Returns only if the timeout has expired.
the maximum amount of time that this retryFor should
block, in units of unit.
the units in which to measure timeout, by default
milliseconds.
Causes the current nesting level to be rolled back due to the specified
cause.
Causes the current nesting level to be rolled back due to the specified
cause. This method may only be called by the thread executing the
transaction; obtain a NestingLevel instance n and call
n.requestRollback(cause) if you wish to doom a transaction from another
thread.
if the current transaction has already decided to commit.
(rare) Delegates final decision of the outcome of the transaction to
decider if the current nesting level participates in the top-level
commit.
(rare) Delegates final decision of the outcome of the transaction to
decider if the current nesting level participates in the top-level
commit. This method can succeed with at most one value per top-level
transaction.
if setExternalDecider(d) was
previously called in this transaction, d != decider, and the
nesting level from which setExternalDecider(d) was called has not
rolled back.
if the current transaction's status is not
Active or Preparing
Returns the status of the current nesting level of the current
transaction, equivalent to NestingLevel.current.status.
(rare) Arranges for handler to be called after (if) it has been decided
that the current transaction will commit, but before the writes made by
the transaction have become available to other threads.
(rare) Arranges for handler to be called after (if) it has been decided
that the current transaction will commit, but before the writes made by
the transaction have become available to other threads. While-committing
handlers can lead to scalability problems, because while this transaction
is in the Committing state it might obstruct other transactions.
Details:
Refs, even using Ref.single;RolledBack or Committed.
(rare) Arranges for handler to be called after the Ref reads and
writes have been checked for serializability, but before the decision has
been made to commit or roll back.
(rare) Arranges for handler to be called after the Ref reads and
writes have been checked for serializability, but before the decision has
been made to commit or roll back. While-preparing handlers can lead to
scalability problems, because while this transaction is in the
Preparing state it might obstruct other transactions. Details:
Refs, even using Ref.single;Preparing phase.
The
Txnobject provides methods that operate on the current transaction context. These methods are only valid within an atomic block or a transaction life-cycle handler, which is checked at compile time by requiring that an implicitInTxnorInTxnEndbe available.