Camunda 8.8 - project does not start

Camunda 8 Topics
1

Hi,

I’m trying to run the latest version of camunda (8.8.0-alpha8) on a project with spring boot.
I’m having a problem starting the project:

2025-09-25T10:57:26.826Z TRACE 487193 --- [bpm] [           main] o.s.c.support.DefaultLifecycleProcessor  : Starting bean 'zeebeLifecycleEventProducer' of type [io.camunda.zeebe.spring.client.event.ZeebeLifecycleEventProducer]
2025-09-25T10:57:26.827Z DEBUG 487193 --- [bpm] [           main] o.s.c.support.DefaultLifecycleProcessor  : Successfully started bean 'zeebeLifecycleEventProducer'
2025-09-25T10:57:26.827Z TRACE 487193 --- [bpm] [           main] o.s.c.support.DefaultLifecycleProcessor  : Starting bean 'camundaLifecycleEventProducer' of type [io.camunda.spring.client.event.CamundaLifecycleEventProducer]
2025-09-25T10:57:29.118Z  INFO 487193 --- [bpm] [           main] .c.s.c.a.p.DeploymentAnnotationProcessor : Configuring deployment: DeploymentValue{resources=[classpath*:/process/**/*.bpmn, classpath*:/forms/**/*.form], beanInfo=ClassInfo{beanName=camundaConfiguration}}
2025-09-25T10:57:29.999Z  WARN 487193 --- [bpm] [           main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Failed to start bean 'camundaLifecycleEventProducer'
2025-09-25T10:57:30.075Z ERROR 487193 --- [bpm] [           main] o.s.b.d.LoggingFailureAnalysisReporter   : 

***************************
APPLICATION FAILED TO START
***************************

Does anyone have any idea how to solve this problem?

Thanks,

Pom:

 <dependency>
            <groupId>io.camunda</groupId>
            <artifactId>spring-boot-starter-camunda-sdk</artifactId>
 </dependency>

Version: 8.8.0-alpha8

Properties:

camunda:
  client:
    mode: saas
    enabled: true
    grpc-address: https://${camunda.client.cloud.cluster-id}.${camunda.client.cloud.region}.zeebe.${camunda.client.cloud.domain}:${camunda.client.cloud.port}
    rest-address: https://${camunda.client.cloud.region}.zeebe.${camunda.client.cloud.domain}:${camunda.client.cloud.port}/${camunda.client.cloud.cluster-id}
    prefer-rest-over-grpc: false
    cloud:
      domain: camunda.io
      port: 443
      cluster-id: ********
      region: ********
    deployment:
      enabled: true
    worker:
      defaults:
        enabled: true
        stream-enabled: true
        request-timeout: PT60S
        timeout: PT60S
        poll-interval: PT60S
        max-jobs-active: 10
    auth:
      client-id: ********
      client-secret: ********
      audience: zeebe.${camunda.client.cloud.domain}
      scope: # optional
2

Hi there! :wave:

I can see you’re experiencing a startup issue with Camunda 8.8.0-alpha8 and Spring Boot. The error Failed to start bean 'camundaLifecycleEventProducer' is typically related to connection issues between your Spring Boot application and the Camunda SaaS cluster.

The Main Issue

Looking at your configuration, I notice you’re manually setting grpc-address and rest-address properties while using mode: saas. This is actually the root cause of your problem!

For Camunda SaaS, you should NOT set grpc-address or rest-address manually. These properties are intended for self-managed installations, not SaaS. When using SaaS mode, the SDK automatically resolves the correct endpoints based on your cluster and region configuration.

Corrected Configuration

Here’s how your configuration should look for SaaS:

camunda:
  client:
    mode: saas
    enabled: true
    prefer-rest-over-grpc: false
    cloud:
      domain: camunda.io
      port: 443
      cluster-id: ********
      region: ********
    deployment:
      enabled: true
    worker:
      defaults:
        enabled: true
        stream-enabled: true
        request-timeout: PT60S
        timeout: PT60S
        poll-interval: PT60S
        max-jobs-active: 10
    auth:
      client-id: ********
      client-secret: ********
      audience: zeebe.camunda.io
      scope: # optional

Key changes:

  1. Remove the grpc-address and rest-address properties completely
  2. Keep the cloud configuration with cluster-id, region, domain, and port
  3. The SDK will automatically construct the correct endpoints from these values

Why This Happens

When you manually set grpc-address and rest-address in SaaS mode, it can cause conflicts where the SDK tries to connect to incorrect endpoints or gets confused about which connection method to use. The alpha versions are particularly sensitive to configuration mismatches.

Additional Considerations for Alpha Versions

Since you’re using 8.8.0-alpha8, be aware that:

  • Alpha versions may have configuration changes or bugs
  • The Spring Zeebe SDK is being replaced by the new Camunda Spring Boot SDK starting with 8.8
  • There might be property structure changes between versions

Try the corrected configuration and let me know if you’re still experiencing issues!

References:

3

Thanks for the reply.

I’ve already removed the extra elements ( grpc-address and rest-address).

But the error still occurs.

Is there any version level restriction on the dependencies?

We’re using Spring Boot 3.5.6

4

Thanks for the update! The issue is likely related to Spring Boot version compatibility.

Version Compatibility Issue

You’re using Spring Boot 3.5.6, but according to the official Camunda documentation, Camunda 8.8.0-alpha8 only supports Spring Boot 3.4.x. Spring Boot 3.5.x is not officially supported yet with Camunda 8.8.

This version mismatch is very likely causing the camundaLifecycleEventProducer bean startup failure, as there may be incompatible changes in Spring Boot 3.5.6 that the Camunda SDK doesn’t handle properly.

Recommended Solutions

Option 1: Downgrade Spring Boot (Recommended)

Downgrade to Spring Boot 3.4.x to match the officially supported version:

<parent>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-parent</artifactId>
    <version>3.4.0</version> <!-- or latest 3.4.x -->
    <relativePath/>
</parent>

Option 2: Use a Stable Camunda Version

Consider using a stable release instead of the alpha version:

<dependency>
    <groupId>io.camunda</groupId>
    <artifactId>spring-boot-starter-camunda-sdk</artifactId>
    <version>8.7.0</version> <!-- Latest stable -->
</dependency>

Option 3: Wait for Official Support

If you need Spring Boot 3.5.6 specifically, you may need to wait for a future Camunda release that officially supports it.

Additional Troubleshooting

If you still want to try with the current setup, could you please share:

  1. The complete stack trace (the error you showed was cut off)
  2. Your complete pom.xml to check for any dependency conflicts
  3. Enable debug logging to get more details:
logging:
  level:
    io.camunda: DEBUG
    io.grpc: DEBUG

Why Alpha Versions Are Problematic

Alpha versions like 8.8.0-alpha8 are:

  • Not production-ready
  • May have undocumented breaking changes
  • Have limited compatibility testing
  • May contain bugs that cause startup failures

For production or stable development, I’d strongly recommend using the latest stable release (8.7.x) with Spring Boot 3.4.x.

References:

Let me know if downgrading Spring Boot resolves the issue!

5

When using the new version 8.8.0, the problem is now fixed and the application starts normally.

6

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