Zeebe gRPC Client Fails with 504 Gateway Timeout After Upgrading to Camunda 8.5.6

Hi Team,

I’m in the process of upgrading our application to Camunda 8.5.6 using the following dependencies:

xml

<dependency>
    <groupId>io.camunda</groupId>
    <artifactId>spring-boot-starter-camunda-sdk</artifactId>
    <version>8.5.6</version>
</dependency>
<dependency>
    <groupId>io.camunda.spring</groupId>
    <artifactId>java-client-operate</artifactId>
    <version>8.5.6</version>
</dependency>

We’re using Spring Boot 3.3, and connecting to a self-managed Zeebe cluster (hosted at bpm-zeebe-dev.qdf.gov.qa:443).

Here is my current application.yml configuration:

yaml

zeebe:
  client:
    connection-mode: ADDRESS
    broker:
      gateway-address: bpm-zeebe-dev.qdf.gov.qa:443
      keep-alive: PT1H
    security:
      plaintext: false
      enabled: true
    default-job-worker-stream-enabled: true

When I start my application, I get the following error:

Failed to stream jobs of type 'solace-place-msg-worker-java1' to worker 'default'

io.grpc.StatusRuntimeException: UNAVAILABLE: HTTP status code 504
invalid content-type: text/html
headers: Metadata(:status=504,...,content-type=text/html,...)
DATA-----------------------------
<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx</center>
</body>
</html>

I have tried some methods suggested in related topics , but not working
Any known issues with Camunda 8.5.6 and Spring Boot 3.3 related to this?

Thanks in advance for your support!

Hi @Aditya_kulkarni, welcome to the forum! What version of Camunda is deployed to your self-managed cluster?

Hi @nathan.loding , thanks. Its same version there as well 8.5.6. I even created separate env for this and checked with 8.6 version as well .But same issue persists.

@Aditya_kulkarni - there aren’t any known issues with either of those versions or the Spring SDK. If you disable job streaming and use job polling instead, does it work?