Fix C8 self-managed example connectivity (#185) - #266
Open
Hafflgav wants to merge 1 commit into
Open
Conversation
Cause: the C8.8 docker-compose migration moved the orchestration REST API/UI to host port 8088 (the app itself uses 8080), but application-c8sm.yml still pointed the Camunda client at the old port 8081 and no longer set a gRPC address, so deployment and REST calls failed against a dead port. Fix: point the client at grpc-address :26500 / rest-address :8088 (matching docker-compose.yaml) and document the 8080-vs-8088 split in the README. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Hafflgav
added
Prio: COULD
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
References #185.
Cause
The C8.8
docker-compose.yamlmigration publishes the consolidatedorchestrationcontainer's REST API/UI on host port 8088 (the example app itself uses 8080), but
application-c8sm.ymlstill pointed the Camunda client at the old port 8081 and nolonger set a gRPC address — so process deployment and every REST call hit a dead port.
Fix
application-c8sm.yml:rest-address: http://localhost:8088(was:8081), add explicitgrpc-address: http://localhost:26500, drop the obsoletetasklist.base-url.README.md: document the8080(app) vs8088(engine UI,demo/demo) split.Verified
docker compose upbrings up a healthycamunda/camunda:8.8.2; REST API v2 on:8088returns 200 while the old
:8081is connection-refused; the app boots and configures theCamunda basic-auth client against
:8088.Remaining blocker but out of scope
The example still can't fully start on
develop: the c8 adapter is pinned to 2026.07.1,which is built for Spring Boot 4 / Camunda 8.9, while this repo runs Spring Boot 3.5.16
(duplicate
healthContributorRegistrybean +httpclient5method mismatch).This is addressed in Issue: #267