All Implemented Interfaces:
Reapable

public class SubordinateAtomicAction extends SubordinateAtomicAction
A subordinate JTA transaction; used when importing another transaction context via JCA. This overrides the basic subordinate transaction simply so that we can ensure JCA transactions are laid out in the right place in the object store.
Author:
mcl
  • Constructor Details

    • SubordinateAtomicAction

      public SubordinateAtomicAction()
      Deprecated.
      This is only used by test code
    • SubordinateAtomicAction

      public SubordinateAtomicAction(Uid actId)
    • SubordinateAtomicAction

      public SubordinateAtomicAction(Uid actId, boolean peekXidOnly) throws ObjectStoreException, IOException
      Recovery SAA. If the record is removed and peekXidOnly is true then the Xid will be null.
      Parameters:
      actId -
      peekXidOnly -
      Throws:
      ObjectStoreException
      IOException
    • SubordinateAtomicAction

      public SubordinateAtomicAction(int timeout, Xid xid)
  • Method Details

    • type

      public String type()
      The type of the class is used to locate the state of the transaction log in the object store. Overloads BasicAction.type()
      Overrides:
      type in class SubordinateAtomicAction
      Returns:
      a string representation of the hierarchy of the class for storing logs in the transaction object store.
    • getType

      public static final String getType()
    • getXid

      public final Xid getXid()
      If the record was removed Xid will be null
      Returns:
    • getParentNodeName

      public String getParentNodeName()
    • save_state

      public boolean save_state(OutputObjectState os, int t)
      Description copied from class: BasicAction
      Redefined version of save_state and restore_state from StateManager. Normal operation (no crashes): BasicAction.save_state is called after a successful prepare. This causes and BasicAction object to be saved in the object store. This object contains primarily the "intentions list" of the BasicAction. After successfully completing phase 2 of the commit protocol, the BasicAction object is deleted from the store. Failure cases: If a server crashes after successfully preparing, then upon recovery the action must be resolved (either committed or aborted) depending upon whether the co-ordinating atomic action committed or aborted. Upon server recovery, the crash recovery mechanism detects ServerBasicAction objects in the object store and attempts to activate the BasicAction object of the co-ordinating action. If this is successful then the SAA is committed else aborted. If, when processing phase 2 of the commit protocol, the co-ordinator experiences a failure to commit from one of the records then the BasicAction object is NOT deleted. It is rewritten when a new state which contains a list of the records that failed during phase 2 commit. This list is called the "failedList". The crash recovery manager will detect local BasicAction objects in addition to SAA objects in the objectstore. An attempt will be made to commit these actions. If the action contained a call to a now dead server, this action can never be resolved and the AA object can never be removed. However, if the action is purely local then after the processing is complete the removed by crash recovery.
      Overrides:
      save_state in class BasicAction
      Returns:
      true if successful, false otherwise.
    • restore_state

      public boolean restore_state(InputObjectState os, int t)
      Description copied from class: BasicAction
      This assumes the various lists are zero length when it is called.
      Overrides:
      restore_state in class BasicAction
      Returns:
      true if successful, false otherwise.
    • activated

      public boolean activated()
      Overrides:
      activated in class SubordinateAtomicAction