I use Quarkus but that shouldn’t be a reason I’d say. The service running in my docket locally for the moment.
I have required properties set, I see that the service register the request and receives an id and the logs in the lra service is logging completion and closing. Everything work if using the In-memory service but not when using the LRA service. It is not declared in the registry as for the IM one. Old that be an issue? I expect the properties is enough /M Den 11 maj 2024 kl 11:19, Zheng Feng <[zf...@redhat.com](mailto:Den 11 maj 2024 kl 11:19, Zheng Feng <<a href=)> skrev: > What runtime framework did you use? spring-boot or quarkus? > And have you set some properties with "camel.lra.coordinator-url" and > "camel.lra.local-participant-url" ? > > The LRA service is running on the same network with your application? it > should access the internal rest paths and route to the right compensation > and completion direct router. > > Also you can check the camel-quarkus lra integration tests [1] or > camel-spring-boot saga example [2] > > [1] https://github.com/apache/camel-quarkus/tree/main/integration-tests/lra > [2] https://github.com/apache/camel-spring-boot-examples/tree/main/saga > > On Sat, May 11, 2024 at 3:58 PM Mikael Andersson Wigander > <mikael.andersson.wigan...@pm.me.invalid> wrote: > >> Hi >> >> When using the saga component together with in memory lra service the >> calls to the compensation and completion routes are executed. This I can se >> when debugging and logging. >> >> But when I switch to using the LRA service (docker image from JBOSS) the >> routes completion and compensation routes are not executed. >> >> Obviously I’m missing something. In any example using this setup there’s >> always rest interface implemented but only within the main route. >> Compensation and completion are still using the direct component. >> >> When debugging the lra service I can clearly see that it is call both >> complete and compensate methods but that is directed to the running lra >> service, not to my routes. >> >> According to the documentation certain rest paths are created and also >> that it will be internal hinting to the design that I still can use the >> direct component and no need to create rest interface for them. >> >> I have also added the platform-http component as required. >> >> What am I missing? >> >> /M
