flowchartsman commented on issue #5417:
URL: https://github.com/apache/pulsar/issues/5417#issuecomment-758165797
I can confirm that this happens when accessing the broker directly _and_
when accessing the proxy:
```
curl -v
http://<broker_addr>:8080/admin/v2/non-persistent/tenantName/namespaceName
* Trying <broker_addr>...
* TCP_NODELAY set
* Connected to <broker_addr> (<broker_addr>) port 8080 (#0)
> GET /admin/v2/non-persistent/tenantName/namespaceName HTTP/1.1
> Host: <broker_addr>:8080
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Date: Mon, 11 Jan 2021 19:15:13 GMT
< broker-address: <broker_addr>
< Content-Type: text/plain
< Content-Length: 3183
< Server: Jetty(9.4.33.v20201020)
<
--- An unexpected error occurred in the server ---
Message: java.util.concurrent.CompletionException:
java.util.concurrent.TimeoutException
Stacktrace:
org.apache.pulsar.client.admin.PulsarAdminException:
java.util.concurrent.CompletionException: java.util.concurrent.TimeoutException
at
org.apache.pulsar.client.admin.internal.BaseResource.getApiException(BaseResource.java:231)
at
org.apache.pulsar.client.admin.internal.TopicsImpl$5.failed(TopicsImpl.java:233)
at
org.glassfish.jersey.client.JerseyInvocation$1.failed(JerseyInvocation.java:839)
at
org.glassfish.jersey.client.ClientRuntime.processFailure(ClientRuntime.java:247)
at
org.glassfish.jersey.client.ClientRuntime.processFailure(ClientRuntime.java:242)
at
org.glassfish.jersey.client.ClientRuntime.access$100(ClientRuntime.java:62)
at
org.glassfish.jersey.client.ClientRuntime$2.lambda$failure$1(ClientRuntime.java:178)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
at
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:288)
at
org.glassfish.jersey.client.ClientRuntime$2.failure(ClientRuntime.java:178)
at
org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector.lambda$apply$1(AsyncHttpConnector.java:200)
at
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774)
at
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:750)
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
at
java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1990)
at
org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector.lambda$timeoutAfter$7(AsyncHttpConnector.java:300)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.concurrent.CompletionException:
java.util.concurrent.TimeoutException
at
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
at
java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
at
java.util.concurrent.CompletableFuture.orApply(CompletableFuture.java:1385)
at
java.util.concurrent.CompletableFuture$OrApply.tryFire(CompletableFuture.java:1364)
at
java.util.concurrent.CompletableFuture$CoCompletion.tryFire(CompletableFuture.java:1034)
... 10 more
Caused by: java.util.concurrent.TimeoutException
... 8 more
* Connection #0 to host <broker_addr> left intact
* Closing connection 0
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
