curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
Date Mon, 28 Jul 2014 18:46:41 GMT


ASF GitHub Bot commented on CURATOR-126:

GitHub user dragonsinth opened a pull request:

    CURATOR-126: Fix race condition in CuratorFrameworkImpl.close()


You can merge this pull request into a Git repository by running:

    $ git pull CURATOR-126

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #23
commit 247e02152a96b58f344439d589d02065f1bd2632
Author: Scott Blum <>
Date:   2014-07-28T18:10:37Z

    CURATOR-126: Fix race condition in CuratorFrameworkImpl.close()


> IllegalStateException in performBackgroundOperation during close
> ----------------------------------------------------------------
>                 Key: CURATOR-126
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.5.0
>            Reporter: Scott Blum
>            Assignee: Cameron McKenzie
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> {code}
> [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
> 	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
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at
> {code}
> 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