Hide Forgot
project_key: EDG Running the EDG functional test case HotRodClientRemoteCacheTestCase against the default cache (which is based on cache mode distributed) results in no errors/failures. Changing the cache mode from distributed to replicated results in a number of failed and error tests. We use one RemoteCacheManager instance and one RemoteCache instance in all the tests - remoteCache.clear() is called in setUp() and tearDown() to clear the replicated cache instance on the server side between tests. When we print out the cache contents in setUp() and tearDown() we can see that in the case of a distributed cache instance, the cache instance is successfully emptied; however, when using the replicated cache instance, we see that the cache is not cleared successfully. For example: Using a distributed cache: Running org.jboss.test.cluster.datagrid.test.HotRodClientRemoteCacheTestCase one-time setup of RemoteCacheManager RemoteCacheManager: using server list: test1:11222;test2:11222 Jun 9, 2011 4:54:35 PM org.infinispan.client.hotrod.impl.operations.HotRodOperation readNewTopologyAndHash INFO: ISPN04006: New topology: {/192.168.0.101:11222=2949, /192.168.0.100:11222=2302} Jun 9, 2011 4:54:35 PM org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory updateServers INFO: ISPN04014: New server added(/192.168.0.101:11222), adding to the pool. Jun 9, 2011 4:54:35 PM org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory updateServers INFO: ISPN04014: New server added(/192.168.0.100:11222), adding to the pool. HotRodClientTestSetup: using dist cache configuration setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} Jun 9, 2011 4:54:43 PM org.infinispan.util.logging.Log_$logger info INFO: Version is: 281483566645386 tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} named stats = {hits=69, currentNumberOfEntries=0, totalBytesRead=25186, timeSinceStart=2383, totalNumberOfEntries=136, totalBytesWritten=11852, removeMisses=0, removeHits=24, retrievals=100, stores=136, misses=31} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} one-time teardown of RemoteCachemanager Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.813 sec Results : Tests run: 21, Failures: 0, Errors: 0, Skipped: 0 Using a replicated cache: Running org.jboss.test.cluster.datagrid.test.HotRodClientRemoteCacheTestCase one-time setup of RemoteCacheManager RemoteCacheManager: using server list: test1:11222;test2:11222 Jun 9, 2011 4:55:56 PM org.infinispan.client.hotrod.impl.operations.HotRodOperation readNewTopologyAndHash INFO: ISPN04006: New topology: {/192.168.0.101:11222=2949, /192.168.0.100:11222=2302} Jun 9, 2011 4:55:56 PM org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory updateServers INFO: ISPN04014: New server added(/192.168.0.101:11222), adding to the pool. Jun 9, 2011 4:55:56 PM org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory updateServers INFO: ISPN04014: New server added(/192.168.0.100:11222), adding to the pool. HotRodClientTestSetup: using repl cache configuration setUp: remoteCache elements : {} tearDown: remoteCache elements : {aKey=aValue} setUp: remoteCache elements : {aKey=aValue} tearDown: remoteCache elements : {anotherKey=anotherValue, aKey=aValue} setUp: remoteCache elements : {anotherKey=anotherValue, aKey=aValue} tearDown: remoteCache elements : {anotherKey=anotherValue, aKey=aValue} setUp: remoteCache elements : {anotherKey=anotherValue, aKey=aValue} tearDown: remoteCache elements : {anotherKey=anotherValue, aKey=aValue} setUp: remoteCache elements : {anotherKey=anotherValue, aKey=aValue} tearDown: remoteCache elements : {anotherKey=anotherValue, aKey=anotherValue} setUp: remoteCache elements : {anotherKey=anotherValue, aKey=anotherValue} tearDown: remoteCache elements : {bKey=bValue, cKey=cValue, aKey=aValue} setUp: remoteCache elements : {bKey=bValue, cKey=cValue, aKey=aValue} tearDown: remoteCache elements : {bKey=bValue, cKey=cValue} setUp: remoteCache elements : {bKey=bValue, cKey=cValue} tearDown: remoteCache elements : {bKey=bValue, cKey=cValue, aKey=aValue} setUp: remoteCache elements : {bKey=bValue, cKey=cValue, aKey=aValue} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} Jun 9, 2011 4:56:04 PM org.infinispan.util.logging.Log_$logger info INFO: Version is: 281483566645407 tearDown: remoteCache elements : {aKey=anotherValue} setUp: remoteCache elements : {aKey=anotherValue} tearDown: remoteCache elements : {aKey=anotherValue} setUp: remoteCache elements : {aKey=anotherValue} tearDown: remoteCache elements : {aKey=aNewValue} setUp: remoteCache elements : {aKey=aNewValue} tearDown: remoteCache elements : {aKey=aValue} setUp: remoteCache elements : {aKey=aValue} tearDown: remoteCache elements : {aKey=aValue} setUp: remoteCache elements : {aKey=aValue} tearDown: remoteCache elements : {aKey=aNewValue} setUp: remoteCache elements : {aKey=aNewValue} tearDown: remoteCache elements : {aKey=aNewValue} setUp: remoteCache elements : {aKey=aNewValue} tearDown: remoteCache elements : {aKey=aValue} setUp: remoteCache elements : {aKey=aValue} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} named stats = {hits=44, currentNumberOfEntries=0, totalBytesRead=28263, timeSinceStart=2464, totalNumberOfEntries=135, totalBytesWritten=13516, removeMisses=2, removeHits=8, retrievals=87, stores=135, misses=43} tearDown: remoteCache elements : {} setUp: remoteCache elements : {} tearDown: remoteCache elements : {} one-time teardown of RemoteCachemanager Tests run: 21, Failures: 7, Errors: 4, Skipped: 0, Time elapsed: 8.598 sec <<< FAILURE!
The sources for the functional testsuite have been ported to run against EDG Alpha and have been moved to: https://svn.devel.redhat.com/repos/jboss-qa/edg/as7-testsuite-poc To run the testsuite against two EDG instances: 1. create two names in DNS test1, test2 which point to the IPs you will bind to 2. start up two instances of EDG on these IPs 3. checkout the testsuite and run > mvn integration-test The test cases will expect the two instances to be available.
Is this still an issue with 5.0.0.CR6?
couldn't replicate this in 5.0.0.CR7 and the new build. resolving for now.
Docs QE Status: Removed: NEW