curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <>
Subject [jira] [Created] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
Date Thu, 24 Jul 2014 10:52:38 GMT
Scott Blum created CURATOR-126:

             Summary: IllegalStateException in performBackgroundOperation during close
                 Key: CURATOR-126
             Project: Apache Curator
          Issue Type: Bug
          Components: Framework
    Affects Versions: 2.5.0
            Reporter: Scott Blum

[CuratorFramework-0] ERROR org.apache.curator.framework.imps.CuratorFrameworkImpl  - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
	at org.apache.curator.CuratorZookeeperClient.getZooKeeper(
	at org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(
	at org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(
	at org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(
	at org.apache.curator.framework.imps.CuratorFrameworkImpl$
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$

I see this sometimes during test runs; I believe this happens because CuratorZookeeperClient.started
gets set to false during shutdown, but the backgroundOperation loop can still be running since
shutting down the backgroundOperation loop is inherently racy.

This message was sent by Atlassian JIRA

View raw message