Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

ZkLockRegistryTests: increase tryLock timeout

Browse Source 
https://build.spring.io/browse/INT-AT42SIO-253/

 ```
 java.lang.AssertionError: Should have been able to lock with zookeeper server restarted!
 	at org.junit.Assert.fail(Assert.java:88)
 	at org.junit.Assert.assertTrue(Assert.java:41)
 	at org.springframework.integration.zookeeper.lock.ZkLockRegistryTests.voidLockFailsWhenServerDown(ZkLockRegistryTests.java:339)
 ```

 When we do `testingServer.restart();` we should give more time to let it started on background, therefore increase the next `lock2.tryLock()` to 10 seconds.

 **Cherry-pick to 4.3.x and 4.2.x**
(cherry picked from commit 6ffdd5e)
This commit is contained in:
Artem Bilan
2016-08-23 11:01:47 -04:00
parent e18be4def6
commit 0d7e3f7e60
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
spring-integration-zookeeper/src/test/java/org/springframework/integration/zookeeper/lock/ZkLockRegistryTests.java
View File

@@ -337,7 +337,7 @@ public class ZkLockRegistryTests extends ZookeeperTestSupport {
testingServer.restart(); testingServer.restart();
assertTrue("Should have been able to lock with zookeeper server restarted!", assertTrue("Should have been able to lock with zookeeper server restarted!",
lock2.tryLock(1, TimeUnit.SECONDS)); lock2.tryLock(10, TimeUnit.SECONDS));
assertTrue("Should have still held lock1", lock1.tryLock(1, TimeUnit.SECONDS)); assertTrue("Should have still held lock1", lock1.tryLock(1, TimeUnit.SECONDS));