You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having the following problem with Curator 1.0.8, with both ZooKeeper 3.3.3 (Linux) and 3.3.5 (OS X). I wrote a test program that starts a CuratorFramework, starts a DistributedQueue with a BlockingQueueConsumer, adds a few items, waits for them to reach the consumer, removes them, closes the queue, then closes the CuratorFramework. Everything succeeds until I try to close the queue, which gives me the following error:
SEVERE: Exception caught in background handler
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at com.netflix.curator.framework.recipes.queue.DistributedQueue.runLoop(DistributedQueue.java:421)
at com.netflix.curator.framework.recipes.queue.DistributedQueue.access$100(DistributedQueue.java:62)
at com.netflix.curator.framework.recipes.queue.DistributedQueue$2.call(DistributedQueue.java:187)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
What might be causing this?
Thanks,
Esteban
The text was updated successfully, but these errors were encountered:
I'm having the following problem with Curator 1.0.8, with both ZooKeeper 3.3.3 (Linux) and 3.3.5 (OS X). I wrote a test program that starts a CuratorFramework, starts a DistributedQueue with a BlockingQueueConsumer, adds a few items, waits for them to reach the consumer, removes them, closes the queue, then closes the CuratorFramework. Everything succeeds until I try to close the queue, which gives me the following error:
What might be causing this?
Thanks,
Esteban
The text was updated successfully, but these errors were encountered: