parReg.tx

Class ParRegBridgeView

java.lang.Object

tx.ViewTest

parReg.tx.ParRegViewTest

parReg.tx.ParRegBridgeView

public class ParRegBridgeView
extends ParRegViewTest

A test to validate what different threads/VMs see in terms of transactional state (when a tx is in progress) as well as non-tx operations. This version is used in client/server distIntegrity tests with partitioned regions in the bridgeServers. Variants exist to kill the tx edge client, the delegate or a dataHost server.

Field Summary

Fields inherited from class tx.ViewTest

checkEventCounters, initializeTxInfo, interestPolicy, isBridgeClient, isProxy, isScopeLocal, isSerialExecution, killSyncObject, myVmPid, rng, txContext, txInProgress, viewTest

Constructor Summary

Constructors

Constructor and Description
ParRegBridgeView()

Method Summary

Modifier and Type	Method and Description
static void	HydraCloseTask_validateTxConsistency() Hydra CLOSETASK to verify that either all or no VMs received the distribution of a transaction (even though the tx vm was killed mid-way through the operation.
static void	HydraCloseTask_verifyResourcesReleased() Hydra CLOSETASK to ensure that we can access the same entries that were accessed in the original transaction (to ensure all locking resources were released).
static void	HydraTask_initialize()
static void	HydraTask_killCommittor() kill the VM if we are the transactional thread and a commit is in Progress (see TxBB.commitInProgress)
static void	HydraTask_killDataHost() kill a DataHost server if the VM if we are the transactional thread and a commit is in Progress (see TxBB.commitInProgress)
static void	HydraTask_killDelegate() kill the delegate (killTarget on BB) if we are the transactional thread and a commit is in Progress (see TxBB.commitInProgress)
protected void	postClientVmInfoToBB() Write ClientVmInfo for delegate and another (nonDelegate) host to BB for future use with kill methods above.
void	setupCommitTestCallbacks(String commitStatePrm)
protected boolean	updatesVisible() Depending on the commitStateTrigger (the point at which the committing VM was killed), should we be able to see the tx updates?
protected void	validateTxConsistency()
protected void	verifyResourcesReleased() Hydra CLOSETASK to verify that resources (e.g.

Methods inherited from class parReg.tx.ParRegViewTest

checkEventCounters, checkTxEventCounters, checkWriterCounters, initialize

Methods inherited from class tx.ViewTest

adjustOldValue, beginTx, checkCommittedState, executeTx, finishTx, getValueInVM, HydraTask_checkCommittedState, HydraTask_executeTx, HydraTask_waitForDist, incrementEventCounters, initialize, validateAllStates, validateCacheClosed, validateCombinedOpsAfterCommit, validateCombinedOpsAfterRollback, validateCommittedState, validateNonTxOps, validateState, validateState, validateTxOps, validateTxOps, verifyCallbackInvocation

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ParRegBridgeView

public ParRegBridgeView()

Method Detail

HydraTask_initialize

public static void HydraTask_initialize()

HydraCloseTask_verifyResourcesReleased

public static void HydraCloseTask_verifyResourcesReleased()

Hydra CLOSETASK to ensure that we can access the same entries that were accessed in the original transaction (to ensure all locking resources were released).

verifyResourcesReleased

protected void verifyResourcesReleased()

Hydra CLOSETASK to verify that resources (e.g. locks) have been released after a client which was committing a transaction is killed. This cannot be invoked in the case of the distributed commit succeeding as we likely can't execute the exact operation again. Either check this case, or provide functions to randomly create these operations with a given Region & Key.

Overrides:

verifyResourcesReleased in class ViewTest

HydraCloseTask_validateTxConsistency

public static void HydraCloseTask_validateTxConsistency()

Hydra CLOSETASK to verify that either all or no VMs received the distribution of a transaction (even though the tx vm was killed mid-way through the operation. Either everyone has all the updates or no one does!

validateTxConsistency

protected void validateTxConsistency()

Overrides:

validateTxConsistency in class ViewTest

updatesVisible

protected boolean updatesVisible()

Depending on the commitStateTrigger (the point at which the committing VM was killed), should we be able to see the tx updates?

Overrides:

updatesVisible in class ParRegViewTest

setupCommitTestCallbacks

public void setupCommitTestCallbacks(String commitStatePrm)

Overrides:

setupCommitTestCallbacks in class ParRegViewTest

postClientVmInfoToBB

protected void postClientVmInfoToBB()

Write ClientVmInfo for delegate and another (nonDelegate) host to BB for future use with kill methods above.

HydraTask_killCommittor

public static void HydraTask_killCommittor()
                                    throws ClientVmNotFoundException

kill the VM if we are the transactional thread and a commit is in Progress (see TxBB.commitInProgress)

Throws:

ClientVmNotFoundException

HydraTask_killDelegate

public static void HydraTask_killDelegate()
                                   throws ClientVmNotFoundException

kill the delegate (killTarget on BB) if we are the transactional thread and a commit is in Progress (see TxBB.commitInProgress)

Throws:

ClientVmNotFoundException

HydraTask_killDataHost

public static void HydraTask_killDataHost()
                                   throws ClientVmNotFoundException

kill a DataHost server if the VM if we are the transactional thread and a commit is in Progress (see TxBB.commitInProgress)

Throws:

ClientVmNotFoundException