Author: mircea.markus Date: 2008-08-28 12:25:14 -0400 (Thu, 28 Aug 2008) New Revision: 6632 Modified: core/trunk/src/test/java/org/jboss/cache/lock/PessimisticLockTest.java Log: this scenario is only acceptable in a pessimistic locking scheme Modified: core/trunk/src/test/java/org/jboss/cache/lock/PessimisticLockTest.java =================================================================== --- core/trunk/src/test/java/org/jboss/cache/lock/PessimisticLockTest.java 2008-08-28 16:24:02 UTC (rev 6631) +++ core/trunk/src/test/java/org/jboss/cache/lock/PessimisticLockTest.java 2008-08-28 16:25:14 UTC (rev 6632) @@ -5,6 +5,7 @@ import org.jboss.cache.DefaultCacheFactory; import org.jboss.cache.Fqn; import org.jboss.cache.NodeSPI; +import org.jboss.cache.config.Configuration; import static org.jboss.cache.lock.LockType.READ; import static org.jboss.cache.lock.LockType.WRITE; import org.jboss.cache.transaction.DummyTransactionManagerLookup; @@ -36,6 +37,7 @@ { cache = new DefaultCacheFactory<Object, Object>().createCache(false); cache.getConfiguration().setTransactionManagerLookupClass(DummyTransactionManagerLookup.class.getName()); + cache.getConfiguration().setNodeLockingScheme(Configuration.NodeLockingScheme.PESSIMISTIC); cache.start(); tm = cache.getConfiguration().getRuntimeConfig().getTransactionManager(); lockManager = TestingUtil.extractLockManager(cache);