Re: [VOTE] Release Apache Camel Kamelets 4.6.0
+1 (binding) Le lun. 13 mai 2024 à 09:56, Andrea Cosentino a écrit : > Hello all, > > This is a vote for releasing camel-kamelets 4.6.0 > > This is a release supporting Camel 4.6.0 > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.6.0 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1712 > Kamelets Tag: > https://github.com/apache/camel-kamelets/releases/tag/v4.6.0 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.6.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Zineb Bendhiba
Re: Saga with LRA service not executing comp* routes
I open https://github.com/MikaelAnderssonWigander/lra-test/pull/2 On Mon, May 13, 2024 at 3:59 PM Mikael Andersson Wigander wrote: > Hi > > Thanks but now I can’t connect to the service. > ConnectException. > > Old create a PR with a working sample so I know what to change? > > /M > > Den 13 maj 2024 kl 09:32, Zheng Feng <[zf...@redhat.com](mailto:Den 13 > maj 2024 kl 09:32, Zheng Feng < skrev: > > > Sorry, your project is good and the problem is the way you run the > narayana > > lra coordinate server. It needs access to the participant url to > > complete or compensate the translation. > > So you have to run docker with the host network. > > > > Please try "docker run --network host -e QUARKUS_HTTP_PORT=8180 > > quay.io/jbosstm/lra-coordinator:latest" > > > > On Mon, May 13, 2024 at 2:44 PM Zheng Feng wrote: > > > >> Thanks and it looks like there are some configuration issues. please > check > >> https://camel.apache.org/components/4.4.x/others/lra.html > >> Also there is no need to add LRASagaService, we can add it automatically > >> if camel-quarkus-lra is in classpath. > >> > >> So I create PR > https://github.com/MikaelAnderssonWigander/lra-test/pull/1 > >> and can you check if it works as what you expected? > >> > >> On Mon, May 13, 2024 at 2:29 PM Mikael Andersson Wigander > >> wrote: > >> > >>> Hi > >>> > >>> Check out > >>> > >>> https://github.com/MikaelAnderssonWigander/lra-test > >>> > >>> /M > >>> > >>> Den 11 maj 2024 kl 12:16, Mikael Andersson Wigander > >>> <[mikael.andersson.wigan...@pm.me.INVALID](mailto:Den 11 maj 2024 kl > >>> 12:16, Mikael Andersson Wigander < skrev: > >>> > >>> > Of course I need to isolate the code and create a sample repo. > >>> > > >>> > I’ll be back > >>> > > >>> > /M > >>> > > >>> > Den 11 maj 2024 kl 11:59, Zheng Feng <[zf...@redhat.com](mailto:Den > 11 > >>> maj 2024 kl 11:59, Zheng Feng < skrev: > >>> > > >>> >> OK, is it possible to share your project and I can take a deep look > at > >>> it? > >>> >> > >>> >> On Sat, May 11, 2024 at 5:34 PM Mikael Andersson Wigander > >>> >> wrote: > >>> >> > >>> >>> 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 < 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 > >>> >>> > 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. > >>> >>> >> > >>> >>>
[VOTE] Release Apache Camel Kamelets 4.6.0
Hello all, This is a vote for releasing camel-kamelets 4.6.0 This is a release supporting Camel 4.6.0 Kamelets release files: https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.6.0 Kamelets staging repository: https://repository.apache.org/content/repositories/orgapachecamel-1712 Kamelets Tag: https://github.com/apache/camel-kamelets/releases/tag/v4.6.0 Please cast your vote. [ ] +1 Release camel-kamelets 4.6.0 [ ] -1 Veto the release (provide specific comments) The vote is open for at least 72 hours. Here's my +1. Thanks, Andrea Cosentino
Re: Saga with LRA service not executing comp* routes
Hi Thanks but now I can’t connect to the service. ConnectException. Old create a PR with a working sample so I know what to change? /M Den 13 maj 2024 kl 09:32, Zheng Feng <[zf...@redhat.com](mailto:Den 13 maj 2024 kl 09:32, Zheng Feng < skrev: > Sorry, your project is good and the problem is the way you run the narayana > lra coordinate server. It needs access to the participant url to > complete or compensate the translation. > So you have to run docker with the host network. > > Please try "docker run --network host -e QUARKUS_HTTP_PORT=8180 > quay.io/jbosstm/lra-coordinator:latest" > > On Mon, May 13, 2024 at 2:44 PM Zheng Feng wrote: > >> Thanks and it looks like there are some configuration issues. please check >> https://camel.apache.org/components/4.4.x/others/lra.html >> Also there is no need to add LRASagaService, we can add it automatically >> if camel-quarkus-lra is in classpath. >> >> So I create PR https://github.com/MikaelAnderssonWigander/lra-test/pull/1 >> and can you check if it works as what you expected? >> >> On Mon, May 13, 2024 at 2:29 PM Mikael Andersson Wigander >> wrote: >> >>> Hi >>> >>> Check out >>> >>> https://github.com/MikaelAnderssonWigander/lra-test >>> >>> /M >>> >>> Den 11 maj 2024 kl 12:16, Mikael Andersson Wigander >>> <[mikael.andersson.wigan...@pm.me.INVALID](mailto:Den 11 maj 2024 kl >>> 12:16, Mikael Andersson Wigander < skrev: >>> >>> > Of course I need to isolate the code and create a sample repo. >>> > >>> > I’ll be back >>> > >>> > /M >>> > >>> > Den 11 maj 2024 kl 11:59, Zheng Feng <[zf...@redhat.com](mailto:Den 11 >>> maj 2024 kl 11:59, Zheng Feng < skrev: >>> > >>> >> OK, is it possible to share your project and I can take a deep look at >>> it? >>> >> >>> >> On Sat, May 11, 2024 at 5:34 PM Mikael Andersson Wigander >>> >> wrote: >>> >> >>> >>> 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 < 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 >>> >>> > 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 >> >>
Re: Svar: Re: Svar: Re: Saga with LRA service not executing comp* routes
Sorry, your project is good and the problem is the way you run the narayana lra coordinate server. It needs access to the participant url to complete or compensate the translation. So you have to run docker with the host network. Please try "docker run --network host -e QUARKUS_HTTP_PORT=8180 quay.io/jbosstm/lra-coordinator:latest" On Mon, May 13, 2024 at 2:44 PM Zheng Feng wrote: > Thanks and it looks like there are some configuration issues. please check > https://camel.apache.org/components/4.4.x/others/lra.html > Also there is no need to add LRASagaService, we can add it automatically > if camel-quarkus-lra is in classpath. > > So I create PR https://github.com/MikaelAnderssonWigander/lra-test/pull/1 > and can you check if it works as what you expected? > > On Mon, May 13, 2024 at 2:29 PM Mikael Andersson Wigander > wrote: > >> Hi >> >> Check out >> >> https://github.com/MikaelAnderssonWigander/lra-test >> >> /M >> >> Den 11 maj 2024 kl 12:16, Mikael Andersson Wigander >> <[mikael.andersson.wigan...@pm.me.INVALID](mailto:Den 11 maj 2024 kl >> 12:16, Mikael Andersson Wigander < skrev: >> >> > Of course I need to isolate the code and create a sample repo. >> > >> > I’ll be back >> > >> > /M >> > >> > Den 11 maj 2024 kl 11:59, Zheng Feng <[zf...@redhat.com](mailto:Den 11 >> maj 2024 kl 11:59, Zheng Feng < skrev: >> > >> >> OK, is it possible to share your project and I can take a deep look at >> it? >> >> >> >> On Sat, May 11, 2024 at 5:34 PM Mikael Andersson Wigander >> >> wrote: >> >> >> >>> 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 < 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 >> >>> > 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 > >
Re: Svar: Re: Svar: Re: Saga with LRA service not executing comp* routes
Thanks and it looks like there are some configuration issues. please check https://camel.apache.org/components/4.4.x/others/lra.html Also there is no need to add LRASagaService, we can add it automatically if camel-quarkus-lra is in classpath. So I create PR https://github.com/MikaelAnderssonWigander/lra-test/pull/1 and can you check if it works as what you expected? On Mon, May 13, 2024 at 2:29 PM Mikael Andersson Wigander wrote: > Hi > > Check out > > https://github.com/MikaelAnderssonWigander/lra-test > > /M > > Den 11 maj 2024 kl 12:16, Mikael Andersson Wigander > <[mikael.andersson.wigan...@pm.me.INVALID](mailto:Den 11 maj 2024 kl > 12:16, Mikael Andersson Wigander < skrev: > > > Of course I need to isolate the code and create a sample repo. > > > > I’ll be back > > > > /M > > > > Den 11 maj 2024 kl 11:59, Zheng Feng <[zf...@redhat.com](mailto:Den 11 > maj 2024 kl 11:59, Zheng Feng < skrev: > > > >> OK, is it possible to share your project and I can take a deep look at > it? > >> > >> On Sat, May 11, 2024 at 5:34 PM Mikael Andersson Wigander > >> wrote: > >> > >>> 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 < 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 > >>> > 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
Svar: Re: Svar: Re: Saga with LRA service not executing comp* routes
Hi Check out https://github.com/MikaelAnderssonWigander/lra-test /M Den 11 maj 2024 kl 12:16, Mikael Andersson Wigander <[mikael.andersson.wigan...@pm.me.INVALID](mailto:Den 11 maj 2024 kl 12:16, Mikael Andersson Wigander < skrev: > Of course I need to isolate the code and create a sample repo. > > I’ll be back > > /M > > Den 11 maj 2024 kl 11:59, Zheng Feng <[zf...@redhat.com](mailto:Den 11 maj > 2024 kl 11:59, Zheng Feng < skrev: > >> OK, is it possible to share your project and I can take a deep look at it? >> >> On Sat, May 11, 2024 at 5:34 PM Mikael Andersson Wigander >> wrote: >> >>> 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 < 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 >>> > 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
