@ZeebeDeployment returns Exception

Camunda 8 Topics
1

Hello,

The application was starting normally, but once I added @ZeebeDemployment to add my BPMN and the workers, the application run failed due to the following exception :

org.springframework.context.ApplicationContextException: Failed to start bean 'zeebeClientLifecycle'; nested exception is io.camunda.zeebe.client.api.command.ClientStatusException: io exception

               at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:181) ~[spring-context-5.3.19.jar:5.3.19]

               at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:54) ~[spring-context-5.3.19.jar:5.3.19]

               at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:356) ~[spring-context-5.3.19.jar:5.3.19]

               at java.base/java.lang.Iterable.forEach(Iterable.java:75) ~[na:na]

               at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:155) ~[spring-context-5.3.19.jar:5.3.19]

               at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:123) ~[spring-context-5.3.19.jar:5.3.19]

               at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:935) ~[spring-context-5.3.19.jar:5.3.19]

               at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586) ~[spring-context-5.3.19.jar:5.3.19]

               at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145) ~[spring-boot-2.6.7.jar:2.6.7]

               at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:740) ~[spring-boot-2.6.7.jar:2.6.7]

               at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:415) ~[spring-boot-2.6.7.jar:2.6.7]

               at org.springframework.boot.SpringApplication.run(SpringApplication.java:303) ~[spring-boot-2.6.7.jar:2.6.7]

               at org.springframework.boot.SpringApplication.run(SpringApplication.java:1312) ~[spring-boot-2.6.7.jar:2.6.7]

               at org.springframework.boot.SpringApplication.run(SpringApplication.java:1301) ~[spring-boot-2.6.7.jar:2.6.7]

               at ma.camunuda.inner.bpm.ProcessApplication.main(ProcessApplication.java:15) ~[classes/:na]

               at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]

               at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:na]

               at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]

               at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]

               at org.springframework.boot.devtools.restart.RestartLauncher.run(RestartLauncher.java:49) ~[spring-boot-devtools-2.6.7.jar:2.6.7]

Caused by: io.camunda.zeebe.client.api.command.ClientStatusException: io exception

               at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.transformExecutionException(ZeebeClientFutureImpl.java:93) ~[zeebe-client-java-8.0.6.jar:8.0.6]

               at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:50) ~[zeebe-client-java-8.0.6.jar:8.0.6]

               at io.camunda.zeebe.spring.client.annotation.processor.ZeebeDeploymentAnnotationProcessor.lambda$start$6(ZeebeDeploymentAnnotationProcessor.java:79) ~[spring-zeebe-8.0.8.jar:8.0.8]

               at java.base/java.util.ArrayList.forEach(ArrayList.java:1540) ~[na:na]

               at io.camunda.zeebe.spring.client.annotation.processor.ZeebeDeploymentAnnotationProcessor.start(ZeebeDeploymentAnnotationProcessor.java:60) ~[spring-zeebe-8.0.8.jar:8.0.8]

               at io.camunda.zeebe.spring.client.annotation.processor.ZeebeAnnotationProcessorRegistry.lambda$startAll$0(ZeebeAnnotationProcessorRegistry.java:38) ~[spring-zeebe-8.0.8.jar:8.0.8]

               at java.base/java.util.ArrayList.forEach(ArrayList.java:1540) ~[na:na]

               at io.camunda.zeebe.spring.client.annotation.processor.ZeebeAnnotationProcessorRegistry.startAll(ZeebeAnnotationProcessorRegistry.java:38) ~[spring-zeebe-8.0.8.jar:8.0.8]

               at io.camunda.zeebe.spring.client.lifecycle.ZeebeClientLifecycle.start(ZeebeClientLifecycle.java:49) ~[spring-zeebe-8.0.8.jar:8.0.8]

               at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:178) ~[spring-context-5.3.19.jar:5.3.19]

               ... 19 common frames omitted

Caused by: java.util.concurrent.ExecutionException: io.grpc.StatusRuntimeException: UNAVAILABLE: io exception

               at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395) ~[na:na]

               at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999) ~[na:na]

               at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:48) ~[zeebe-client-java-8.0.6.jar:8.0.6]

               ... 27 common frames omitted

Caused by: io.grpc.StatusRuntimeException: UNAVAILABLE: io exception

               at io.grpc.Status.asRuntimeException(Status.java:535) ~[grpc-api-1.45.1.jar:1.45.1]

               at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:478) ~[grpc-stub-1.45.1.jar:1.45.1]

               at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:463) ~[grpc-core-1.45.1.jar:1.45.1]

               at io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:427) ~[grpc-core-1.45.1.jar:1.45.1]

               at io.grpc.internal.DelayedClientCall$DelayedListener.onClose(DelayedClientCall.java:460) ~[grpc-core-1.45.1.jar:1.45.1]

               at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:562) ~[grpc-core-1.45.1.jar:1.45.1]

               at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:70) ~[grpc-core-1.45.1.jar:1.45.1]

               at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:743) ~[grpc-core-1.45.1.jar:1.45.1]

               at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:722) ~[grpc-core-1.45.1.jar:1.45.1]

               at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) ~[grpc-core-1.45.1.jar:1.45.1]

               at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133) ~[grpc-core-1.45.1.jar:1.45.1]

               at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]

               at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]

               at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]

Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: no further information: /0.0.0.0:26500

Caused by: java.net.ConnectException: Connection refused: no further information

               at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[na:na]

               at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:779) ~[na:na]

               at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337) ~[netty-transport-4.1.76.Final.jar:4.1.76.Final]

               at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334) ~[netty-transport-4.1.76.Final.jar:4.1.76.Final]

               at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:710) ~[netty-transport-4.1.76.Final.jar:4.1.76.Final]

               at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:658) ~[netty-transport-4.1.76.Final.jar:4.1.76.Final]

               at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:584) ~[netty-transport-4.1.76.Final.jar:4.1.76.Final]

               at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:496) ~[netty-transport-4.1.76.Final.jar:4.1.76.Final]

               at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) ~[netty-common-4.1.76.Final.jar:4.1.76.Final]

               at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.76.Final.jar:4.1.76.Final]

               at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.76.Final.jar:4.1.76.Final]

               at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]

And I cannot realise what’s the prolem !

Thank you in advance !

2

Hello @Hanane-Boutzrout ,

your client tries to reach zeebe under localhost:26500.

Is the engine running there? And if yes, which version of the engine and the client do you use?

Jonathan

3

Hello @jonathan.lukas,
Yes the engine is running ! I can browse into Operate and Tasklist and since both depend on Zeebe that means it is running !
But I don’t get why it refuses to connect with it !
I’m using version 8.0.5 !

4

Hello @Hanane-Boutzrout ,

the dependency from zeebe to Operate and Tasklist is loose.

That means they can run without zeebe.

How do you run zeebe? Local, docker or k8s?
Can you please check whether zeebe is really running.

Jonathan

5

I run it in local !

If you don’t mind, can I ask how to check that ?

Its ports (26500 and 9600) are listening, but when I try localhost:9600/health and localhost:26500/health, I don’t get anything !

6

Hello @Hanane-Boutzrout ,

the logs of zeebe should show you what it is doing. Is there something suspicious?

Jonathan

1 Like
7

Do you have your client configured to try to connect to 0.0.0.0?
You can set that address as the address your broker is listening to, but you cannot try to connect to that address… it’s a special address meaning “Allow connections on all addresses on this computer”

Try setting your client to connect to 127.0.0.1

8

Hello @GotnOGuts,

First, thank you for your reply!

And that’s actually one of the things that I don’t get, I’m already setting the broker to connect to my address :

zeebe:
  broker:
    gatewayAddress: 127.0.0.1:26500
  client:
    security:
      plaintext: true

But still it doesn’t work !

9

How are you running Zeebe?

1 Like
10

Locally, using this command line :

tar -xzf zeebe-distribution-X.Y.Z.tar.gz -C zeebe/
./bin/broker
11

Hi @Hanane-Boutzrout . Please change your config to this:

zeebe:
  client:
    broker:
      gatewayAddress: 127.0.0.1:26500
    security:
      plaintext: true
2 Likes
12

Hello @lzgabel

That’s exactly what I did yesterday but I forgot to update the answer here !

But still, thank you for your proposition and your reply !

2 Likes
13