You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Ryan Ruel (Jira)" <ji...@apache.org> on 2023/03/30 14:16:00 UTC
[jira] (CURATOR-665) ModeledFramework does not throw expected exception and instead hangs
[ https://issues.apache.org/jira/browse/CURATOR-665 ]
Ryan Ruel deleted comment on CURATOR-665:
-----------------------------------
was (Author: ryan0751):
Thanks [~tison] .
To confirm, yes I am using 5.4.0.
I reproduced your test above, and YES I did get the exception.
However, if I change the "update" operation to a "set" (which is what I am using in my test), then I see the hang again.
Can you try that in your test?
> ModeledFramework does not throw expected exception and instead hangs
> --------------------------------------------------------------------
>
> Key: CURATOR-665
> URL: https://issues.apache.org/jira/browse/CURATOR-665
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 5.4.0
> Reporter: Ryan Ruel
> Priority: Major
>
> When writing data to ZooKeeper via Curator, I found that when I was receiving a KeeperException NoAuth back from ZooKeeper, my call would hang indefinitely.
> The NoAuth was expected as I was testing writing to a path where the ACL was set to prevent my client from writing (X509 authentication scheme).
> The call which hangs:
> {code:java}
> myFramework.set(myModel).toCompletableFuture().get();{code}
> The logs from the call:
> {code:java}
> 2023-03-29 14:20:29,511 [Curator-Framework-0] ERROR imps.CuratorFrameworkImpl - Background exception was not retry-able or retry gave up
> org.apache.zookeeper.KeeperException$NoAuthException: KeeperErrorCode = NoAuth for /test/foo {code}
> I'd expect this exception to bubble up wrapped in a CompletionException.
> Instead, CuratorFrameworkImpl just logs the exception and then the call to get() hangs indefinitely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)