com.gemstone.gemfire.cache.query.cq.dunit

Class CqDataDUnitTest

java.lang.Object

junit.framework.Assert

junit.framework.TestCase

dunit.DistributedTestCase

com.gemstone.gemfire.cache30.CacheTestCase

com.gemstone.gemfire.cache.query.cq.dunit.CqDataDUnitTest

All Implemented Interfaces:

Serializable, junit.framework.Test

public class CqDataDUnitTest
extends CacheTestCase

This class tests the ContiunousQuery mechanism in GemFire. This includes the test with different data activities.

See Also:

Serialized Form

Nested Class Summary

Nested classes/interfaces inherited from class dunit.DistributedTestCase

DistributedTestCase.ExpectedException, DistributedTestCase.WaitCriterion, DistributedTestCase.WaitCriterion2

Field Summary

Fields

Modifier and Type	Field and Description
protected CqQueryDUnitTest	cqDUnitTest

Fields inherited from class com.gemstone.gemfire.cache30.CacheTestCase

cache

Fields inherited from class dunit.DistributedTestCase

logPerTest, reconnect, system, testName

Constructor Summary

Constructors

Constructor and Description
CqDataDUnitTest(String name)

Method Summary

Modifier and Type	Method and Description
CacheSerializableRunnable	setTestHook()
void	setUp() Sets up the test (noop).
void	testClientWithFeederAndCQ() Tests with client acting as feeder/publisher and registering cq.
void	testCQHAWithState() Test for CQ Fail over/HA with redundancy level set.
void	testCQWithBridgeClient() Test for CQ with BridgeClient.
void	testCQWithBridgeWriter() Test for CQ with ConnectionPool...
void	testCQWithConnectionPool() Test for CQ with ConnectionPool.
void	testCQWithDestroysAndInvalidates() Tests propogation of invalidates and destorys to the clients.
void	testCQWithEstablishCallBackConnection() Test for CQ with establishCallBackConnection.
void	testCQWithEviction() Test for CQ when entries are evicted from region.
void	testCQWithLoad() Test for CQ when region is populated with net load.
void	testCQWithMultipleClients() Tests make sure that the second client doesnt get more events then there should be.
void	testEventsDuringQueryExecution() Test for events created during the CQ query execution.
void	testMultipleExecuteWithInitialResults() This test was created to test executeWithInitialResults being called multiple times.
void	testRegionEvents() Test for: Region destroy, calls close on the server.

Methods inherited from class com.gemstone.gemfire.cache30.CacheTestCase

addExceptionTag1, basicGetCache, beginCacheXml, cleanDiskDirs, closeAllCache, closeCache, createLonerCache, createMcastCache, createMcastCache, createRegion, createRegion, createRootRegion, createRootRegion, disconnectFromDS, finishCacheXml, finishCacheXml, getCache, getCache, getCache, getCache, getClientCache, getDiskDirs, getGemfireCache, getInternalRegionArguments, getRootRegion, getRootRegion, hasCache, remoteTearDown, removeExceptionTag1, sendSerialMessageToAll, sendUnorderedMessageToAll, tearDown2

Methods inherited from class dunit.DistributedTestCase

addExpectedException, addExpectedException, addHydraProperties, attachDebugger, checkBBFlag, cleanupAllVms, clearBBFlag, crashDistributedSystem, crashDistributedSystem, createLogWriter, disconnectAllFromDS, dumpAllStacks, dumpMyThreads, dumpStack, dumpStack, dumpStack, dumpStackTrace, fail, getAllDistributedSystemProperties, getDistributedSystemProperties, getDUnitLocatorAddress, getDUnitLocatorPort, getDUnitLocatorString, getDUnitLogLevel, getIPLiteral, getLogWriter, getLonerSystem, getMcastSystem, getMcastSystem, getRepeatTimeoutMs, getServerHostName, getSystem, getSystem, getTestClass, getTestName, getUniqueName, getVMCount, incBBFlag, invokeInEveryVM, invokeInEveryVM, invokeInEveryVM, invokeInEveryVM, invokeInEveryVMRepeatingIfNecessary, invokeInLocator, invokeRepeatingIfNecessary, isConnectedToDS, join, noteTiming, pause, pause, perVMSetUp, realTearDown, setDiskStoreForGateway, setSystem, setTestName, staticPause, tearDown, unregisterAllDataSerializersFromAllVms, unregisterDataSerializerInThisVM, unregisterInstantiatorsInThisVM, waitForBBFlag, waitForCriterion, waitMutex

Methods inherited from class junit.framework.TestCase

assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, countTestCases, createResult, fail, fail, failNotEquals, failNotSame, failSame, format, getName, run, run, runBare, runTest, setName, toString

Methods inherited from class java.lang.Object

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

Field Detail

cqDUnitTest

protected CqQueryDUnitTest cqDUnitTest

Constructor Detail

CqDataDUnitTest

public CqDataDUnitTest(String name)

Method Detail

setUp

public void setUp()
           throws Exception

Description copied from class: DistributedTestCase

Sets up the test (noop).

Overrides:

setUp in class DistributedTestCase

Throws:

Exception

testClientWithFeederAndCQ

public void testClientWithFeederAndCQ()
                               throws Exception

Tests with client acting as feeder/publisher and registering cq. Added wrt bug 37161. In case of InterestList the events are not sent back to the client if its the originator, this is not true for cq.

Throws:

Exception

testCQHAWithState

public void testCQHAWithState()
                       throws Exception

Test for CQ Fail over/HA with redundancy level set.

Throws:

Exception

testCQWithDestroysAndInvalidates

public void testCQWithDestroysAndInvalidates()
                                      throws Exception

Tests propogation of invalidates and destorys to the clients. Bug 37242.

Throws:

Exception

testCQWithMultipleClients

public void testCQWithMultipleClients()
                               throws Exception

Tests make sure that the second client doesnt get more events then there should be. This will test the fix for bug 37295.

Throws:

Exception

testCQWithLoad

public void testCQWithLoad()
                    throws Exception

Test for CQ when region is populated with net load.

Throws:

Exception

testCQWithEviction

public void testCQWithEviction()
                        throws Exception

Test for CQ when entries are evicted from region.

Throws:

Exception

testCQWithConnectionPool

public void testCQWithConnectionPool()
                              throws Exception

Test for CQ with ConnectionPool.

Throws:

Exception

testCQWithBridgeClient

public void testCQWithBridgeClient()
                            throws Exception

Test for CQ with BridgeClient.

Throws:

Exception

testCQWithBridgeWriter

public void testCQWithBridgeWriter()
                            throws Exception

Test for CQ with ConnectionPool... BridgeWriteR?? Is it definitely needed?.

Throws:

Exception

testCQWithEstablishCallBackConnection

public void testCQWithEstablishCallBackConnection()
                                           throws Exception

Test for CQ with establishCallBackConnection.

Throws:

Exception

testRegionEvents

public void testRegionEvents()
                      throws Exception

Test for: Region destroy, calls close on the server. Region clear triggers cqEvent with query op region clear. Region invalidate triggers cqEvent with query op region invalidate.

Throws:

Exception

testEventsDuringQueryExecution

public void testEventsDuringQueryExecution()
                                    throws Exception

Test for events created during the CQ query execution. When CQs are executed using executeWithInitialResults there may be possibility that the region changes during that time may not be reflected in the query result set thus making the query data and region data inconsistent.

Throws:

Exception

testMultipleExecuteWithInitialResults

public void testMultipleExecuteWithInitialResults()
                                           throws Exception

This test was created to test executeWithInitialResults being called multiple times. Previously, the queueEvents would be overwritten and we would lose data. This test will execute the method twice. The first time, the first execution will block it's own child thread (TC1). The second execution will block until TC1 is completed (based on how executeWithInitialResults is implemented) A third thread will be awaken and release the latch in the testhook for TC1 to complete.

Throws:

Exception

setTestHook

public CacheSerializableRunnable setTestHook()