com.gemstone.gemfire.internal.cache.tier.sockets

Class DurableClientSimpleDUnitTests

java.lang.Object

junit.framework.Assert

junit.framework.TestCase

dunit.DistributedTestCase

com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientDUnitTest

com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientSimpleDUnitTests

All Implemented Interfaces:

java.io.Serializable, junit.framework.Test

public class DurableClientSimpleDUnitTests
extends DurableClientDUnitTest

See Also:

Serialized Form

Nested Class Summary

Nested classes/interfaces inherited from class com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientDUnitTest

DurableClientDUnitTest.CqExceptionDueToActivatingClientTestHook, DurableClientDUnitTest.RejectClientReconnectTestHook

Nested classes/interfaces inherited from class dunit.DistributedTestCase

DistributedTestCase.ExpectedException, DistributedTestCase.WaitCriterion, DistributedTestCase.WaitCriterion2

Field Summary

Fields inherited from class com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientDUnitTest

durableClientVM, isPrimaryRecovered, publisherClientVM, regionName, server1VM, server2VM

Fields inherited from class dunit.DistributedTestCase

logPerTest, reconnect, system, testName

Constructor Summary

Constructors

Constructor and Description
DurableClientSimpleDUnitTests(java.lang.String name)

Method Summary

Modifier and Type	Method and Description
void	DISABLED_testReadyForEventsNotCalledImplicitlyWithCacheXML()
void	testCloseAllCqsAndDrainEvents() Test functionality to close the cq and drain all events from the ha queue from the server This draining should not affect events that still have register interest
void	testCloseAllCqsAndDrainEventsNoInterestRegistered() Test functionality to close the cq and drain all events from the ha queue from the server This draining should remove all events due to no interest registered Continues to publish afterwards to verify that stats are correct
void	testCloseCacheProxy() Test functionality to close the durable client and drain all events from the ha queue from the server
void	testCloseCqAndDrainEvents() Test functionality to close the cq and drain all events from the ha queue from the server
void	testCloseCqAndDrainEvents2Client() Test functionality to close the cq and drain all events from the ha queue from the server Two durable clients, one will have a cq be closed, the other should be unaffected
void	testCqCloseExceptionDueToActivatingClient() Tests scenario where close cq will throw an exception due to a client being reactivated
void	testCqCloseExceptionDueToActiveConnection() Tests situation where a client is trying to reconnect while a cq is being drained
void	testDurableClientMultipleServersOneLive() Test that starting a durable client on multiple servers (one live and one not live) is processed correctly.
void	testDurableClientReconnectTwoServers() Tests whether a durable client reconnects properly to two servers.
void	testHAQueuedCqStat() Tests the ha queued cq stat
void	testHAQueuedCqStatForFailover() server 1 and 2 both get events server 1 goes down dc reconnects server 2 behaves accordingly
void	testHAQueuedCqStatForGII() Server 2 comes up, client connects and registers cqs, server 2 then disconnects events are put into region client goes away server 2 comes back up and should get a gii check stats server 1 goes away client comes back and receives all events stats should still be correct
void	testHAQueuedCqStatForGII2() Start both servers, but shut down secondary server before durable client has connected.
void	testHAQueuedCqStatForGIINoFailover() Server 2 comes up and goes down after client connects and registers cqs events are put into region client goes away server 2 comes back up and should get a gii check stats client comes back and receives all events stats should still be correct
void	testHAQueuedCqStatOnSecondary()
void	testHAQueuedCqStatWithTimeOut() Tests the ha queued cq stat
void	testHAQueueSizeStat() Tests the ha queued events stat Connects a durable client, registers durable cqs and then shuts down the durable client Publisher then does puts onto the server Events are queued up and the stats are checked Durable client is then reconnected, events are dispatched and stats are rechecked
void	testHAQueueSizeStatExpired() Tests the ha queued events stat Connects a durable client, registers durable cqs and then shuts down the durable client Publisher then does puts onto the server Events are queued up and the stats are checked Test sleeps until durable client times out Stats should now be 0 Durable client is then reconnected, no events should exist and stats are rechecked
void	testHAQueueSizeStatForGII() Tests the ha queued events stat Starts up two servers, shuts one down Connects a durable client, registers durable cqs and then shuts down the durable client Publisher then does puts onto the server Events are queued up Durable client is then reconnected but does not send ready for events Secondary server is brought back up Stats are checked Durable client then reregisters cqs and sends ready for events
void	testMultipleBridgeClientsInSingleDurableVM() Test that a durable client VM with multiple BridgeClients correctly registers on the server.
void	testReadyForEventsNotCalledImplicitly()
void	testReadyForEventsNotCalledImplicitlyForRegisterInterestWithCacheXML()
void	testRejectClientWhenDrainingCq() Tests situation where a client is trying to reconnect while a cq is being drained.
void	testSimpleDurableClientMultipleServers() Test that starting a durable client on multiple servers is processed correctly.
void	testSimpleDurableClientUpdate() Test that a durable client correctly receives updates.
void	testSimpleTwoDurableClients() Test that the server correctly processes starting two durable clients.
void	testTwoDurableClientsStartStopUpdate() Test that updates to two durable clients are processed correctly.
void	XtestMultipleVMsWithSameDurableId() Test that a second VM with the same durable id cannot connect to the server while the first VM is connected.

Methods inherited from class com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientDUnitTest

checkCqListenerEvents, checkCqStatOnServer, checkForAck, checkHAQueueSize, checkInterestEvents, checkNumberOfClientProxies, checkNumDurableCqs, checkPrimaryRecovery, checkPrimaryUpdater, checkProxyIsAlive, closeCache, closeDurableClient, createCq, createCq, disconnectDurableClient, disconnectDurableClient, durableFailover, durableFailoverAfterReconnect, flushEntries, getBridgeServer, getClientDistributedSystemProperties, getClientDistributedSystemProperties, getClientDistributedSystemPropertiesNonDurable, getClientPool, getClientPool, getClientPool, getClientProxy, getHARegionQueueName, getNumberOfClientProxies, publishEntries, registerInterest, restartDurableClient, sendClientReady, setBridgeObeserverForAfterPrimaryRecovered, setPrimaryRecoveryCheck, setTestFlagToVerifyActForMarker, setUp, startClient, startClient, startDurableClient, startDurableClient, startDurableClient, tearDown2, test39630, testDurableClientConnectServerStopStart, testDurableClientPrimaryUpdate, testDurableHAFailover, testDurableNonHAFailover, testReadyForEventsNotCalledImplicitlyWithCacheXML, testSimpleDurableClient, testStartStopStartDurableClient, testStartStopStartDurableClientUpdate, testStartStopTimeoutDurableClient, verifyDurableClientOnServer, verifyListenerUpdates, verifyListenerUpdates, verifyListenerUpdatesDisconnected, verifyListenerUpdatesEntries, verifyReceivedMarkerAck, verifySimpleDurableClient, verifySimpleDurableClientMultipleServers

Methods inherited from class dunit.DistributedTestCase

addExpectedException, addExpectedException, addHydraProperties, attachDebugger, checkBBFlag, cleanupAllVms, clearBBFlag, crashDistributedSystem, crashDistributedSystem, createLogWriter, disconnectAllFromDS, disconnectFromDS, 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

Constructor Detail

DurableClientSimpleDUnitTests

public DurableClientSimpleDUnitTests(java.lang.String name)

Method Detail

testSimpleDurableClientUpdate

public void testSimpleDurableClientUpdate()

Test that a durable client correctly receives updates.

testMultipleBridgeClientsInSingleDurableVM

public void testMultipleBridgeClientsInSingleDurableVM()

Test that a durable client VM with multiple BridgeClients correctly registers on the server.

Overrides:

testMultipleBridgeClientsInSingleDurableVM in class DurableClientDUnitTest

XtestMultipleVMsWithSameDurableId

public void XtestMultipleVMsWithSameDurableId()

Test that a second VM with the same durable id cannot connect to the server while the first VM is connected. Also, verify that the first client is not affected by the second one attempting to connect.

Overrides:

XtestMultipleVMsWithSameDurableId in class DurableClientDUnitTest

testSimpleTwoDurableClients

public void testSimpleTwoDurableClients()

Test that the server correctly processes starting two durable clients.

Overrides:

testSimpleTwoDurableClients in class DurableClientDUnitTest

testDurableClientMultipleServersOneLive

public void testDurableClientMultipleServersOneLive()

Test that starting a durable client on multiple servers (one live and one not live) is processed correctly.

testTwoDurableClientsStartStopUpdate

public void testTwoDurableClientsStartStopUpdate()

Test that updates to two durable clients are processed correctly.

testDurableClientReconnectTwoServers

public void testDurableClientReconnectTwoServers()

Tests whether a durable client reconnects properly to two servers.

testReadyForEventsNotCalledImplicitly

public void testReadyForEventsNotCalledImplicitly()

Overrides:

testReadyForEventsNotCalledImplicitly in class DurableClientDUnitTest

DISABLED_testReadyForEventsNotCalledImplicitlyWithCacheXML

public void DISABLED_testReadyForEventsNotCalledImplicitlyWithCacheXML()

testReadyForEventsNotCalledImplicitlyForRegisterInterestWithCacheXML

public void testReadyForEventsNotCalledImplicitlyForRegisterInterestWithCacheXML()

Overrides:

testReadyForEventsNotCalledImplicitlyForRegisterInterestWithCacheXML in class DurableClientDUnitTest

testHAQueueSizeStat

public void testHAQueueSizeStat()
                         throws java.lang.Exception

Tests the ha queued events stat Connects a durable client, registers durable cqs and then shuts down the durable client Publisher then does puts onto the server Events are queued up and the stats are checked Durable client is then reconnected, events are dispatched and stats are rechecked

Throws:

java.lang.Exception

testHAQueueSizeStatExpired

public void testHAQueueSizeStatExpired()
                                throws java.lang.Exception

Tests the ha queued events stat Connects a durable client, registers durable cqs and then shuts down the durable client Publisher then does puts onto the server Events are queued up and the stats are checked Test sleeps until durable client times out Stats should now be 0 Durable client is then reconnected, no events should exist and stats are rechecked

Throws:

java.lang.Exception

testHAQueueSizeStatForGII

public void testHAQueueSizeStatForGII()
                               throws java.lang.Exception

Tests the ha queued events stat Starts up two servers, shuts one down Connects a durable client, registers durable cqs and then shuts down the durable client Publisher then does puts onto the server Events are queued up Durable client is then reconnected but does not send ready for events Secondary server is brought back up Stats are checked Durable client then reregisters cqs and sends ready for events

Throws:

java.lang.Exception

testHAQueuedCqStat

public void testHAQueuedCqStat()
                        throws java.lang.Exception

Tests the ha queued cq stat

Throws:

java.lang.Exception

testHAQueuedCqStatOnSecondary

public void testHAQueuedCqStatOnSecondary()
                                   throws java.lang.Exception

Throws:

java.lang.Exception

testHAQueuedCqStatForGII

public void testHAQueuedCqStatForGII()
                              throws java.lang.Exception

Server 2 comes up, client connects and registers cqs, server 2 then disconnects events are put into region client goes away server 2 comes back up and should get a gii check stats server 1 goes away client comes back and receives all events stats should still be correct

Throws:

java.lang.Exception

testHAQueuedCqStatForGII2

public void testHAQueuedCqStatForGII2()
                               throws java.lang.Exception

Start both servers, but shut down secondary server before durable client has connected. Connect durable client to primary, register cqs and then shutdown durable client Publish events, reconnect durable client but do not send ready for events Restart secondary and check stats to be sure cqs have correct stats due to GII Shutdown primary and fail over to secondary Durable Client sends ready or events and receives events Recheck stats

Throws:

java.lang.Exception

testHAQueuedCqStatForGIINoFailover

public void testHAQueuedCqStatForGIINoFailover()
                                        throws java.lang.Exception

Server 2 comes up and goes down after client connects and registers cqs events are put into region client goes away server 2 comes back up and should get a gii check stats client comes back and receives all events stats should still be correct

Throws:

java.lang.Exception

testHAQueuedCqStatForFailover

public void testHAQueuedCqStatForFailover()
                                   throws java.lang.Exception

server 1 and 2 both get events server 1 goes down dc reconnects server 2 behaves accordingly

Throws:

java.lang.Exception

testHAQueuedCqStatWithTimeOut

public void testHAQueuedCqStatWithTimeOut()
                                   throws java.lang.Exception

Tests the ha queued cq stat

Throws:

java.lang.Exception

testCloseCqAndDrainEvents

public void testCloseCqAndDrainEvents()
                               throws java.lang.Exception

Test functionality to close the cq and drain all events from the ha queue from the server

Throws:

java.lang.Exception

testCloseAllCqsAndDrainEvents

public void testCloseAllCqsAndDrainEvents()
                                   throws java.lang.Exception

Test functionality to close the cq and drain all events from the ha queue from the server This draining should not affect events that still have register interest

Throws:

java.lang.Exception

testCloseAllCqsAndDrainEventsNoInterestRegistered

public void testCloseAllCqsAndDrainEventsNoInterestRegistered()
                                                       throws java.lang.Exception

Test functionality to close the cq and drain all events from the ha queue from the server This draining should remove all events due to no interest registered Continues to publish afterwards to verify that stats are correct

Throws:

java.lang.Exception

testCloseCqAndDrainEvents2Client

public void testCloseCqAndDrainEvents2Client()
                                      throws java.lang.Exception

Test functionality to close the cq and drain all events from the ha queue from the server Two durable clients, one will have a cq be closed, the other should be unaffected

Throws:

java.lang.Exception

testRejectClientWhenDrainingCq

public void testRejectClientWhenDrainingCq()
                                    throws java.lang.Exception

Tests situation where a client is trying to reconnect while a cq is being drained. The client should be rejected until no cqs are currently being drained

Throws:

java.lang.Exception

testCqCloseExceptionDueToActivatingClient

public void testCqCloseExceptionDueToActivatingClient()
                                               throws java.lang.Exception

Tests scenario where close cq will throw an exception due to a client being reactivated

Throws:

java.lang.Exception

testCqCloseExceptionDueToActiveConnection

public void testCqCloseExceptionDueToActiveConnection()
                                               throws java.lang.Exception

Tests situation where a client is trying to reconnect while a cq is being drained

Throws:

java.lang.Exception

testCloseCacheProxy

public void testCloseCacheProxy()
                         throws java.lang.Exception

Test functionality to close the durable client and drain all events from the ha queue from the server

Throws:

java.lang.Exception

testSimpleDurableClientMultipleServers

public void testSimpleDurableClientMultipleServers()

Test that starting a durable client on multiple servers is processed correctly.

Overrides:

testSimpleDurableClientMultipleServers in class DurableClientDUnitTest