Hi, Good to hear from you that the issue has been resolved. I recommend you to leverage the camel-k <https://github.com/apache/camel-k> if you are going to run the camel application in the K8S environment.
On Mon, May 20, 2024 at 5:34 PM Mikael Andersson Wigander <mikael.andersson.wigan...@pm.me.invalid> wrote: > Hi > > This is now solved. > > The issue was that we need to include “http://“ in the values for the > coordinator and participator properties. > > We excluded that because we can communicate in K8 without it (some default > I recon). > > Maybe there’s something internal I might need to make a ticket for? > > /M > > Den 19 maj 2024 kl 15:43, Zheng Feng <[zf...@redhat.com](mailto:Den 19 > maj 2024 kl 15:43, Zheng Feng <<a href=)> skrev: > > > Hi, > > > > Maybe you can take a look at > > > https://github.com/apache/camel-k-examples/tree/main/generic-examples/saga > > > > On Sat, May 18, 2024 at 10:39 PM Mikael Andersson Wigander > > <mikael.andersson.wigan...@pm.me.invalid> wrote: > > > >> Hi, me again :) > >> > >> Recently I posted an ask about Saga and LRA and got everything working > >> with an external coordinator from quay/jboss running in my local Docker > >> thanks to you! > >> > >> My Saga application can complete and compensate as intended with the > >> coordinator. > >> > >> BUT when deploying both in our K8 nothing works. > >> > >> I can conclude that from within each application shell I can connect to > >> them each, the coordinator has access to my application and vice versa. > >> > >> When the Saga starts my application just stalls and will not release so > >> the only way to restart it is to scale down/up. > >> > >> No logs present in any service to indicate suspicious behaviour. > >> > >> I had to use the InMemoryService for the moment until I figure this out. > >> > >> Any clues where to look? It’s a long shot I know but anything might > help. > >> > >> Camel LRA has a Logger defined but logs are at the barest minimum and > >> produces no help. > >> > >> Thx > >> > >> M > >> > >> /M
