Zeebe does not stream activated job to a Worker in Spring application

Camunda 8 Topics
, ,
1

I am having issues with Zeebe in a way that it (most often) does not stream jobs to my registered workers. I am using Spring 3.2.7 with dependency spring-boot-starter-camunda 8.5.2. As suggested by community, we are also using Camunda platform found on GitHub where we simply run it with docker compose up, on main branch.

XML definition of my service task is this:

    <bpmn:serviceTask id="RetrieveCreditBureauInfoTask" name="Retrieve credit bureau info">
      <bpmn:extensionElements>
        <zeebe:taskDefinition type="retrieve-credit-bureau-info" />
      </bpmn:extensionElements>
      <bpmn:incoming>Flow_1icuqst</bpmn:incoming>
      <bpmn:outgoing>Flow_0uheqbt</bpmn:outgoing>
    </bpmn:serviceTask>

, and when I run my Spring application, I see that Worker for that task has been started successfully:
i.c.z.s.c.jobhandling.JobWorkerManager : . Starting Zeebe worker: ZeebeWorkerValue{type='retrieve-credit-bureau-info', name='retrieveCreditBureauInfoWorker#retrieveCreditBureauInfo', timeout=PT-0.001S, maxJobsActive=-1, requestTimeout=PT-1S, pollInterval=PT-0.001S, autoComplete=true, fetchVariables=[], enabled=true, methodInfo=io.camunda.zeebe.spring.client.bean.MethodInfo@206de1f, tenantIds=[], forceFetchAllVariables=false, streamEnabled=true, streamTimeout=PT-0.001S}

Also, this is the code for such worker:

import io.camunda.zeebe.spring.client.annotation.JobWorker;
import lombok.extern.slf4j.Slf4j;
import org.springframework.stereotype.Component;

@Component
@Slf4j
@SuppressWarnings("unused")
public class RetrieveCreditBureauInfoWorker {
  @JobWorker(type = "retrieve-credit-bureau-info")
  public void retrieveCreditBureauInfo() {
    log.info("Retrieving credit bureau info...");
  }
}

As I can see, token appears to be not moving from my service task, which most likely means Zeebe hasn’t streamed job to my worker.
stuck-token

2

Hello Stefan,

I’m not sure if I’m right, but there are two possible causes:

  1. are you connected to the right Camunda cluster? Are you using self managed or the SaaS solution? Maybe you have the wrong parameters.

  2. Also, I’m not sure whether your worker necessarily needs a return statement for the token to move on.

I hope I was able to help you a little further.

3

Hi, I tried it of course and none of the ideas actually solve it. Thanks for your answer, also.

So, I am using this platform, on which I connect from my Spring boot application. I am correctly connected, because I see the processes are always deployed.

The one thing I noticed are warnings when starting the app. First 5 lines look like this:

WARN 12152 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'io.camunda.zeebe.spring.client.annotation.processor.AnnotationProcessorConfiguration' of type [io.camunda.zeebe.spring.client.annotation.processor.AnnotationProcessorConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). The currently created BeanPostProcessor [zeebeAnnotationProcessorRegistry] is declared through a non-static factory method on that class; consider declaring it as static instead.
WARN 12152 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'deploymentPostProcessor' of type [io.camunda.zeebe.spring.client.annotation.processor.ZeebeDeploymentAnnotationProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [zeebeAnnotationProcessorRegistry]? Check the corresponding BeanPostProcessor declaration and its dependencies.
WARN 12152 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'zeebe.client-io.camunda.zeebe.spring.client.properties.ZeebeClientConfigurationProperties' of type [io.camunda.zeebe.spring.client.properties.ZeebeClientConfigurationProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [zeebeAnnotationProcessorRegistry]? Check the corresponding BeanPostProcessor declaration and its dependencies.
WARN 12152 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'camunda.client-io.camunda.zeebe.spring.client.properties.CamundaClientProperties' of type [io.camunda.zeebe.spring.client.properties.CamundaClientProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [zeebeAnnotationProcessorRegistry]? Check the corresponding BeanPostProcessor declaration and its dependencies.
WARN 12152 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'io.camunda.zeebe.spring.client.configuration.ZeebeClientAllAutoConfiguration' of type [io.camunda.zeebe.spring.client.configuration.ZeebeClientAllAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [zeebeAnnotationProcessorRegistry]? Check the corresponding BeanPostProcessor declaration and its dependencies.

Could it do something with my situation?

4

Solution found on this post:

5

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