curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CURATOR-98) Avoid erroneous 'Could not cancel' warning produced by cache tasks
Date Wed, 19 Mar 2014 18:37:45 GMT

     [ https://issues.apache.org/jira/browse/CURATOR-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jordan Zimmerman resolved CURATOR-98.
-------------------------------------

    Resolution: Fixed

PR accepted and merged

> Avoid erroneous 'Could not cancel' warning produced by cache tasks
> ------------------------------------------------------------------
>
>                 Key: CURATOR-98
>                 URL: https://issues.apache.org/jira/browse/CURATOR-98
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 2.4.1
>            Reporter: Joe Littlejohn
>            Assignee: Jordan Zimmerman
>             Fix For: 2.4.2
>
>
> Pull request:
> https://github.com/apache/curator/pull/3
> When closing providers, we regularly see an erroneous warning related to a failure to
cancel cache tasks.
> This change applies some more defensive checks before attempting to cancel tasks, ensuring
that the cancel operation is only attempted if the future has not completed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message