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 Tue, 29 Jul 2014 00:01:45 GMT


ASF GitHub Bot commented on CURATOR-126:

Github user Randgalt commented on the pull request:
    I pushed an update to the test that has an assert. I tested it with the old background
thread code and the test fails. It succeeds with the new code.
    From: cammckenzie <>
    Reply: apache/curator <>>
    Date: July 28, 2014 at 6:29:46 PM
    To: apache/curator <>>
    Cc: Jordan Zimmerman <>>
    Subject:  Re: [curator] CURATOR-126: Fix race condition in CuratorFrameworkImpl.close()
    I have pushed a unit test up onto the CURATOR-126 branch. Have a play with it, I still
seem to be getting the error logged when running against the fix. Could be something bogus
in the test though.
    Reply to this email directly or view it on GitHub.

> 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: Jordan Zimmerman
>             Fix For: 2.7.0
>   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