[
https://issues.apache.org/jira/browse/CURATOR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085409#comment-14085409
]
ASF GitHub Bot commented on CURATOR-71:
---------------------------------------
Github user madrob commented on the pull request:
https://github.com/apache/curator/pull/31#issuecomment-51126572
Updated the PR to remove the first logging in ConnectionState. I think
you're right about leaving the second one in, since it's covered by a boolean
flag.
> Error message in StandardLockInternalsDriver for retryable lock acquire error
> -----------------------------------------------------------------------------
>
> Key: CURATOR-71
> URL: https://issues.apache.org/jira/browse/CURATOR-71
> Project: Apache Curator
> Issue Type: Bug
> Components: Recipes
> Affects Versions: 2.1.0-incubating
> Reporter: Vegard B. Havdal
>
> We occasionally get the error message "Sequential path not found..." from
> StandardLockInternalDriver, but the subsequent NoNode exception is caught and
> treated as normal in some cases in LockInternals. Ie. bogus error message in
> our log.
> Consider removing the error log msg from StandardLockInternalDriver, not log
> and throw.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
