Timeout instead of incident after send newFailCommand

Camunda 8 Topics Discussion & Questions
1

Hello! I have a Zeebe job handler (kotlin). I expect to get an incident immediately after calling it. But instead of incident I get a timeout exception after some time. What am I doing wrong?

Context: “io.camunda:zeebe-client-java:1.3.1”

 JobHandler { jobClient, activatedJob ->
        jobClient.newFailCommand(activatedJob).retries(0).errorMessage("Job failed!").send()
    }

image
image1780×187 49.1 KB

2

Hey @neki

in order to help you here I would need how you run Zeebe. Are you using the SaaS offering or did you deployed Zeebe on your own? If so how? Helm charts?

Is there anything else going on on the cluster?

Greets
Chris

1 Like
3

Zelldon thanks. We have a self-hosted kube cluster. We use helm template attached below. I suppose this configuration is correct, because jobClient.newCompleteCommand and jobClient.newThrowErrorCommand work correctly

zeebeBroker.yaml 
apiVersion: apps/v1
kind: StatefulSet
metadata:
  labels:
    app: zeebe-broker
  name: zeebe
  namespace: {{ .Values.global.companyName }}
spec:
  replicas: 1
  selector:
    matchLabels:
      app: zeebe-broker
  serviceName: zeebe
  template:
    metadata:
      labels:
        app: zeebe-broker
    spec:
      nodeSelector:
      {{ .Values.global.defaultNodeSelector }}
      containers:
        - name: zeebe
          # our-docker-hub-cache/camunda/zeebe:1.3.1
          image: {{ .Values.imageName }}  
          ports:
            - containerPort: 26500
              name: gateway
            - containerPort: 9600
              name: monitoring-api
            - containerPort: 5701
              name: hazelcast
          volumeMounts:
            - name: config
              mountPath: /usr/local/zeebe/config/application.yaml
              subPath: application.yaml
            - name: zeebe-data
              mountPath: /usr/local/zeebe/data
              subPath: data
            - name: zeebe-data
              mountPath: /usr/local/zeebe/zeebe-hazelcast-exporter.jar
              # Download on https://github.com/camunda-community-hub/zeebe-hazelcast-exporter/releases
              subPath: plugins/zeebe-hazelcast-exporter.jar
              readOnly: true
          env:
            - name: ZEEBE_LOG_LEVEL
              value: warn
          readinessProbe:
            httpGet:
              path: /ready
              port: 9600
            initialDelaySeconds: 20
            periodSeconds: 5
      volumes:
        - name: config
          configMap:
            name: zeebe-config
            defaultMode: 0744
        - name: zeebe-data
          {{ if eq .Values.global.deployType "release" }}
          persistentVolumeClaim:
            claimName: zeebe-broker-pvc
          {{ else if eq .Values.global.deployType "merge-request-environment" }}
          emptyDir: { }
          {{ else }}
          hostPath:
            path: "/mnt/zeebe-broker"
            type: DirectoryOrCreate
  {{ end }}

And we connect our kotlin app by maven lib “io.camunda:zeebe-client-java:1.3.1”

1 Like
5