spring-integration: ZookeeperLockRegistry does not honor timeout semantics on tryLock

I was trying to write a test that checked the behavior of ZookeeperLockRegistry when the zookeeper cluster is unreachable. I wrote a test that extended the pattern in DefaultLockRegistryTests to ensure the lock is not able to be locked when the testingserver is shutdown. Here’s a snippet of the code:

testingServer.stop();
Lock lock2 = registry.obtain("bar");
assertFalse("Should not have been able to lock with zookeeper server stopped!", lock2.tryLock(2, TimeUnit.SECONDS));

The call to lock2.tryLock(2, TimeUnit.SECONDS)) hangs forever until I kill the test. This is the call in curator framework that seems to cause the problem: https://github.com/apache/curator/blob/apache-curator-2.10.0/curator-recipes/src/main/java/org/apache/curator/framework/recipes/locks/StandardLockInternalsDriver.java#L54

These seems to occur regardless of the CuratorFramework client configuration that is passed into the registry. I do see the background reconnect process timingout and eventually giving up (properly according to my settings), but the call linked to above seems to run in the foreground and not honor the retry/timeout settings.