Camunda 8 message Event Issue

Camunda 8 Topics
1

Hi,
May I know why getting below errors when using messaging event to start the process

io.camunda.zeebe.client.api.command.ClientStatusException: Reached maximum capacity of requests handled

  at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.transformExecutionException(ZeebeClientFutureImpl.java:93)

  at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:50)

  at com.unobank.common.camunda.services.impl.MessageEventServiceImpl.messageThrowEvent(MessageEventServiceImpl.java:26)

  at com.unobank.service.workers.PaymentJobWorker.messageThrowEvent(PaymentJobWorker.java:249)

  at jdk.internal.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)

  at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

  at java.base/java.lang.reflect.Method.invoke(Method.java:569)

  at io.camunda.zeebe.spring.client.bean.MethodInfo.invoke(MethodInfo.java:46)

  at io.camunda.zeebe.spring.client.jobhandling.JobHandlerInvokingSpringBeans.handle(JobHandlerInvokingSpringBeans.java:88)

  at io.camunda.zeebe.client.impl.worker.JobRunnableFactory.executeJob(JobRunnableFactory.java:44)

  at io.camunda.zeebe.client.impl.worker.JobRunnableFactory.lambda$create$0(JobRunnableFactory.java:39)

  at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)

  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

  at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)

  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)

  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)

  at java.base/java.lang.Thread.run(Thread.java:840)

Caused by: java.util.concurrent.ExecutionException: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Reached maximum capacity of requests handled

  at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)

  at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073)

  at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:48)

  ... 15 more

Caused by: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Reached maximum capacity of requests handled

  at io.grpc.Status.asRuntimeException(Status.java:535)

  at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:487)

  at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:563)

  at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:70)

  at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:744)

  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)

  ... 3 more

TIA

2

This error indicates Zeebe’s backpressure mechanism has kicked in due to the broker receiving more requests than it can handle, and you should implement retry logic with exponential backoff for message correlation calls. I found the following relevant resources:

Does this help? If not, can anyone from the community jump in? :waving_hand:

:light_bulb: Hints: Use the Ask AI feature in Camunda’s documentation to chat with AI and get fast help. Report bugs and features in Camuda’s GitHub issue tracker. Trust the process. :robot:

3

Hello!

This error means the Zeebe broker has hit its request handling limit. It usually happens when too many commands (like message publishes or job completions) are sent at once, overwhelming the broker. To fix it, you can throttle or batch requests, reduce worker concurrency, or scale your Zeebe cluster resources. In short, the broker is applying backpressure, so you need to slow down request rates or increase capacity.