Connection to zeebe fails while college is able to connect with the exact same code

Camunda 8 Topics
,
1

Hello there,

I am currently running a self-managed Camunda instance on a Kubernetes cluster within my network. The setup was functioning smoothly, allowing both my colleague and me to connect to the cluster without any issues.

However, after a recent reinstallation of Camunda on the cluster due to resource configuration adjustments, I have encountered the following error message (please see below). Interestingly, my colleague is still able to connect to the same cluster using the exact same Java code with the new client secret but I am not.

I would greatly appreciate any insights or suggestions to help resolve this issue. Thank you in advance for your support!

Best regards,
Tim

io.camunda.zeebe.client.api.command.ClientStatusException
        at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.transformExecutionException(ZeebeClientFutureImpl.java:116)
        at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:54)
        at com.example.DemoApplication.main(DemoApplication.java:39)
Caused by: java.util.concurrent.ExecutionException: io.grpc.StatusRuntimeException: CANCELLED
        at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
        at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
        at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:52)
        ... 1 more
Caused by: io.grpc.StatusRuntimeException: CANCELLED
        at io.grpc.Status.asRuntimeException(Status.java:533)
        at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:481)
        at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:489)
        at io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:453)
        at io.grpc.internal.DelayedClientCall$DelayedListener.onClose(DelayedClientCall.java:486)
        at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:574)
        at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:72)
        at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:742)
        at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:723)
        at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
        at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)
Caused by: java.io.IOException: Failed while requesting access token with status code 401 and message Unauthorized.
        at io.camunda.zeebe.client.impl.oauth.OAuthCredentialsProvider.fetchCredentials(OAuthCredentialsProvider.java:157)
        at io.camunda.zeebe.client.impl.oauth.OAuthCredentialsCache.computeIfMissingOrInvalid(OAuthCredentialsCache.java:100)
        at io.camunda.zeebe.client.impl.oauth.OAuthCredentialsProvider.applyCredentials(OAuthCredentialsProvider.java:79)
        at io.camunda.zeebe.client.impl.ZeebeCallCredentials.lambda$applyRequestMetadata$0(ZeebeCallCredentials.java:49)
        ... 3 more
2

Hi @ad_tim, welcome to the forums! That is strange indeed. Usually when I see that particular error, there’s a networking issue; for instance, a proxy that isn’t compatible with HTTP/2. A few questions:

  • are you both connecting from the same network, or only to the same network?
  • how are you using the “exact same Java code”? Do you have a repository, you both cloned it, and one runs and the other doesn’t? Or you both have your own implementations locally and compared how you’re creating the Zeebe client?
3

Hi,

thanks for your reply.
I solved the problem through using a newer JDK and put the environment variables to the environment variables on my computer.

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.