Getting Warning in spring-zeebe client Constantly

Camunda 8 Topics Discussion & Questions
1

Hi Team,

We are constantly getting one warning in the spring Zeebe client and we are not able to figure out why we are getting the error. The workload for the zeebe is very less. we are having only one workflow deployed and a maximum of 5 instances created per hour and it will be complete within a minute.

Another thing we noticed is when there are no jobs available for workers, that time it will show this warning.

specs:
Zeebe 0.25.3 (assigned 16GB RAM & 8VCPU)
spring-zeebe-starter 0.25.0

2020-12-28 15:20:50.046  WARN 1 --- [lt-executor-359] io.zeebe.client.job.poller               : Failed to activated jobs for worker success_event_handler and job type success_event_handle
r
io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Expected to activate jobs of type 'ac_success_event_handler', but no jobs available and at least one broker returned 'RESOURCE_EXHAUSTED'. Ple
ase try again later.
        at io.grpc.Status.asRuntimeException(Status.java:533) ~[grpc-api-1.33.0.jar!/:1.33.0]
        at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:478) ~[grpc-stub-1.33.0.jar!/:1.33.0]
        at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:616) ~[grpc-core-1.33.0.jar!/:1.33.0]
        at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:69) ~[grpc-core-1.33.0.jar!/:1.33.0]
        at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:802) ~[grpc-core-1.33.0.jar!/:1.33.0]
        at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:781) ~[grpc-core-1.33.0.jar!/:1.33.0]
        at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) ~[grpc-core-1.33.0.jar!/:1.33.0]
        at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123) ~[grpc-core-1.33.0.jar!/:1.33.0]
        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:825) ~[na:na]

Please help us in resolving the issue, we are close to production but due to this issue, we are struggling!

Thanks.

2

How many workers do you have, and how often are they polling?

How does your system perform under load? Have you load tested it?

This is not an issue per se - it’s a warning message in the log.

It could be the visible symptom of an actual issue that affects performance, but… is it?

1 Like
3

Hi @jwulf,

I figured out the issue, it was due to the wrong conditional expression in zeebe java client. It’s a bug in zeebe java client. I raised an issue in github.

1 Like
4