Re: camel examples main yaml doesn't work for me
Hi I just created a tag for the 3.20.4 release so you can use this https://github.com/apache/camel-examples/tree/camel-examples-3.20.4 On Thu, May 11, 2023 at 9:49 PM Claus Ibsen wrote: > Hi > > Those examples on main branch is for the main branch camel-core which > currently is for Camel v4. > > If you want to run Camel 3.20.x examples then use the branch for that > https://github.com/apache/camel-examples/tree/camel-3.20.x/examples > > We don't tag all the examples for every release (there is just soo much > work), so you can set the camel version to 3.20.4 in the pom.xml file. > > Also if you want to try Camel then Camel JBang is also a great new > fantastic way > https://camel.apache.org/manual/camel-jbang.html > > You can use Camel JBang as a CLI to run and also introspect existing > running Camels and much more to come. > > > > On Thu, May 11, 2023 at 7:14 PM Fyodor Kravchenko > wrote: > >> I have cloned the repository and tried to run the >> camel-examples/examples/main-yaml executable as stated in the readme >> (mvn compile, mvn capel:run), but it didn't seem to work. I just didn't >> print anything. I've also tried to downgrade Camel in the project to the >> latest Camel 3 which compiled but still didn't work. >> >> All it prints is >> >> mvn camel:run >> [INFO] Scanning for projects... >> [INFO] >> [INFO] --< org.apache.camel.example:camel-example-main-yaml >> >-- >> [INFO] Building Camel :: Example :: Main :: YAML 4.0.0-SNAPSHOT >> [INFO] [ jar >> ]- >> [INFO] >> [INFO] --- camel-maven-plugin:3.20.4:run (default-cli) @ >> camel-example-main-yaml --- >> [INFO] You can skip tests from the command line using: mvn camel:run >> -Dmaven.test.skip=true >> [INFO] Using custom org.apache.camel.example.MyApplication to initiate a >> CamelContext >> [INFO] Starting Camel ... >> >> and that's it. I tried to modify the my-route.yaml for it to detect the >> new route but to no avail. >> >> (I am trying this because I'm failing to make my own little test >> project, but actually the official example works worse than my own >> attempt. It doesn't load the route at statrup but works okay when I >> modify the yaml. To reiterate, the example does neither of this: neither >> it loads the route at startup nor at the yaml modification) >> >> I may have java problems. In the environment I try the example: >> >> java --version >> openjdk 19.0.1 2022-10-18 >> OpenJDK Runtime Environment GraalVM CE 22.3.0 (build >> 19.0.1+10-jvmci-22.3-b08) >> OpenJDK 64-Bit Server VM GraalVM CE 22.3.0 (build >> 19.0.1+10-jvmci-22.3-b08, mixed mode, sharing) >> >> JAVA_HOME=/xxx/graalvm-ce-java19-22.3.0 >> >> >> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/xxx/graalvm-ce-java19-22.3.0/bin >> >> I have also Java 8 installed somewhere but I tried to make sure the >> modern java is used. >> >> What am I doing wrong? >> >> --fedd >> >> > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: camel examples main yaml doesn't work for me
Hi Those examples on main branch is for the main branch camel-core which currently is for Camel v4. If you want to run Camel 3.20.x examples then use the branch for that https://github.com/apache/camel-examples/tree/camel-3.20.x/examples We don't tag all the examples for every release (there is just soo much work), so you can set the camel version to 3.20.4 in the pom.xml file. Also if you want to try Camel then Camel JBang is also a great new fantastic way https://camel.apache.org/manual/camel-jbang.html You can use Camel JBang as a CLI to run and also introspect existing running Camels and much more to come. On Thu, May 11, 2023 at 7:14 PM Fyodor Kravchenko wrote: > I have cloned the repository and tried to run the > camel-examples/examples/main-yaml executable as stated in the readme > (mvn compile, mvn capel:run), but it didn't seem to work. I just didn't > print anything. I've also tried to downgrade Camel in the project to the > latest Camel 3 which compiled but still didn't work. > > All it prints is > > mvn camel:run > [INFO] Scanning for projects... > [INFO] > [INFO] --< org.apache.camel.example:camel-example-main-yaml > >-- > [INFO] Building Camel :: Example :: Main :: YAML 4.0.0-SNAPSHOT > [INFO] [ jar > ]- > [INFO] > [INFO] --- camel-maven-plugin:3.20.4:run (default-cli) @ > camel-example-main-yaml --- > [INFO] You can skip tests from the command line using: mvn camel:run > -Dmaven.test.skip=true > [INFO] Using custom org.apache.camel.example.MyApplication to initiate a > CamelContext > [INFO] Starting Camel ... > > and that's it. I tried to modify the my-route.yaml for it to detect the > new route but to no avail. > > (I am trying this because I'm failing to make my own little test > project, but actually the official example works worse than my own > attempt. It doesn't load the route at statrup but works okay when I > modify the yaml. To reiterate, the example does neither of this: neither > it loads the route at startup nor at the yaml modification) > > I may have java problems. In the environment I try the example: > > java --version > openjdk 19.0.1 2022-10-18 > OpenJDK Runtime Environment GraalVM CE 22.3.0 (build > 19.0.1+10-jvmci-22.3-b08) > OpenJDK 64-Bit Server VM GraalVM CE 22.3.0 (build > 19.0.1+10-jvmci-22.3-b08, mixed mode, sharing) > > JAVA_HOME=/xxx/graalvm-ce-java19-22.3.0 > > > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/xxx/graalvm-ce-java19-22.3.0/bin > > I have also Java 8 installed somewhere but I tried to make sure the > modern java is used. > > What am I doing wrong? > > --fedd > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
camel examples main yaml doesn't work for me
I have cloned the repository and tried to run the camel-examples/examples/main-yaml executable as stated in the readme (mvn compile, mvn capel:run), but it didn't seem to work. I just didn't print anything. I've also tried to downgrade Camel in the project to the latest Camel 3 which compiled but still didn't work. All it prints is mvn camel:run [INFO] Scanning for projects... [INFO] [INFO] --< org.apache.camel.example:camel-example-main-yaml >-- [INFO] Building Camel :: Example :: Main :: YAML 4.0.0-SNAPSHOT [INFO] [ jar ]- [INFO] [INFO] --- camel-maven-plugin:3.20.4:run (default-cli) @ camel-example-main-yaml --- [INFO] You can skip tests from the command line using: mvn camel:run -Dmaven.test.skip=true [INFO] Using custom org.apache.camel.example.MyApplication to initiate a CamelContext [INFO] Starting Camel ... and that's it. I tried to modify the my-route.yaml for it to detect the new route but to no avail. (I am trying this because I'm failing to make my own little test project, but actually the official example works worse than my own attempt. It doesn't load the route at statrup but works okay when I modify the yaml. To reiterate, the example does neither of this: neither it loads the route at startup nor at the yaml modification) I may have java problems. In the environment I try the example: java --version openjdk 19.0.1 2022-10-18 OpenJDK Runtime Environment GraalVM CE 22.3.0 (build 19.0.1+10-jvmci-22.3-b08) OpenJDK 64-Bit Server VM GraalVM CE 22.3.0 (build 19.0.1+10-jvmci-22.3-b08, mixed mode, sharing) JAVA_HOME=/xxx/graalvm-ce-java19-22.3.0 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/xxx/graalvm-ce-java19-22.3.0/bin I have also Java 8 installed somewhere but I tried to make sure the modern java is used. What am I doing wrong? --fedd
Re: [VOTE] Release Apache Camel Kamelets 4.0.0-M3
+1 (binding) Thanks! On Thu, May 11, 2023 at 2:56 PM Claus Ibsen wrote: > +1 (binding) > > On Thu, May 11, 2023 at 2:30 PM Andrea Cosentino > wrote: > > > Hello all: > > > > This is a vote for releasing camel-kamelets 4.0.0-M3 > > > > Kamelets release files: > > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M3 > > Kamelets staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1553 > > Kamelets Tag: > > https://github.com/apache/camel/releases/tag/camel-4.0.0-M3 > > > > Please cast your vote. > > > > [ ] +1 Release camel-kamelets 4.0.0-M3 > > [ ] -1 Veto the release (provide specific comments) > > > > The vote is open for at least 72 hours. > > > > Here's my +1. > > > > Thanks, > > Andrea Cosentino > > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: [VOTE] Release Apache Camel Kamelets 4.0.0-M3
+1 (binding) On Thu, May 11, 2023 at 2:30 PM Andrea Cosentino wrote: > Hello all: > > This is a vote for releasing camel-kamelets 4.0.0-M3 > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M3 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1553 > Kamelets Tag: > https://github.com/apache/camel/releases/tag/camel-4.0.0-M3 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.0.0-M3 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Kamelets 4.0.0-M3
+1 (binding) Thanks, Le jeu. 11 mai 2023 à 14:30, Andrea Cosentino a écrit : > Hello all: > > This is a vote for releasing camel-kamelets 4.0.0-M3 > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M3 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1553 > Kamelets Tag: > https://github.com/apache/camel/releases/tag/camel-4.0.0-M3 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.0.0-M3 > [ ] -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: [VOTE] Release Apache Camel Kamelets 4.0.0-M3
The Kamelets tag for 4.0.0-M3 is here: https://github.com/apache/camel-kamelets/releases/tag/v4.0.0-M3 Sorry for the wrong link. Il giorno gio 11 mag 2023 alle ore 14:30 Andrea Cosentino ha scritto: > Hello all: > > This is a vote for releasing camel-kamelets 4.0.0-M3 > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M3 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1553 > Kamelets Tag: > https://github.com/apache/camel/releases/tag/camel-4.0.0-M3 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.0.0-M3 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino >
[VOTE] Release Apache Camel Kamelets 4.0.0-M3
Hello all: This is a vote for releasing camel-kamelets 4.0.0-M3 Kamelets release files: https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M3 Kamelets staging repository: https://repository.apache.org/content/repositories/orgapachecamel-1553 Kamelets Tag: https://github.com/apache/camel/releases/tag/camel-4.0.0-M3 Please cast your vote. [ ] +1 Release camel-kamelets 4.0.0-M3 [ ] -1 Veto the release (provide specific comments) The vote is open for at least 72 hours. Here's my +1. Thanks, Andrea Cosentino
Re: Camel Jbang & JSON Logging & ExchangeId as mdc/ndc?
Hi
You are welcome to investigate this and see if you can get MDC to work.
You need to enable it first in Camel. And then find out how to map that to
ECS layout in log4j.
On Thu, May 11, 2023 at 8:59 AM Mikael Koskinen wrote:
> Hi,
>
> I'm wondering if it would be possible to include ExchangeId into log
> messages when using Camel Jbang to run integration with JSON Logging?
>
> The idea is to be able to group the log messages by the exchange.
>
> Currently the ExchangeId is included in the "message" field when an
> error happens:
>
> "message": "Failed delivery for (MessageId:
> 4762099352DD338-0001 on ExchangeId:
> 4762099352DD338-0001). Exhausted after delivery attempt: 1
> caught: org.apache.camel.http.base.HttpOperationFailedException: HTTP
> operation failed invoking https://we
>
> The JSON logging seems to use EcsLayout:
>
> {
> "@timestamp": "${json:timestamp}",
> "log.level": "${json:level}",
> "message": "${json:message}",
> "process.thread.name": "${json:thread:name}",
> "log.logger": "${json:logger:name}",
> "labels": "${json:mdc}",
> "tags": "${json:ndc}",
> "error.type": "${json:exception:className}",
> "error.message": "${json:exception:message}",
> "error.stack_trace": "${json:exception:stackTrace:text}"
> }
>
>
> And I think the mdc (labels) or ndc (tags) could be a suitable place
> to hold this information.
>
> Also the idea is that if my integration contains a Log step:
>
> - log:
> message: Handling stuff ${header.stuffNo}
> loggingLevel: DEBUG
>
> When logged using the JSON Logging this also would contain the
> ExchangeId in mdc/ndc.
>
> What do you think?
>
> Best regards,
> Mikael
>
--
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Book on camel 3.20.x
Hi There is no book on Camel 3. The current books are listed at https://camel.apache.org/community/books/ What documentation int he reference page do you think needs updates, and what information are you looking for? Can you maybe provide some examples so we can better understand. And yeah its open source and we love contributions. So anyone is welcome to help with docs, examples etc. https://camel.apache.org/community/contributing/ The CiA2 book is much relevant today as the basic principles of Camel are the same, and a lot of how you do X is also the same/very similar. The source code for the book has been updated and you can find branches for never Camel releases, also 3.20.x https://github.com/camelinaction/camelinaction2/tree/camel-3.20 On Wed, May 10, 2023 at 9:33 PM rishi sharma wrote: > Hi Team, > Is there any book for Apache camel 3.20.x just like camel in action 2. > > Reference documentation does not cover details and a lot of time is getting > invested in figuring out solutions. > > Thanks > Rishi > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Shutdown of camel routes
Hi How do you setup the quickfix engine? Also do you have a chance to try a newer camel release as it may work better there. But yeah we should make it ideally stop the engine before routes so new messages are not feed into camel On Tue, May 9, 2023 at 7:05 PM Gaurav Kumar wrote: > Hi > I am using camel (3.14) with springboot. > > Application is also using camel quickfixj to connect with the > vendor platform via FIX protocol. > > Application has a public camel route that consumes messages from the Fix > session, but when I shutdown the application, the public route stops first > and the quick fix engine stops after 4-5 seconds ( I am using > *DefaultShutDownStrategy*). This is causing the following issues. > > Quick fix engine keeps receiving the messages but because the route is > stopped so the incoming messages are not consumed by route and they didn't; > get a chance to process. > > Is there any way to stop the Quickfix engine first and then stop the route > or any other way to sequence the shutdown? > > > > -- > Regards > Gaurav > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Camel Jbang & JSON Logging & ExchangeId as mdc/ndc?
Hi,
I'm wondering if it would be possible to include ExchangeId into log
messages when using Camel Jbang to run integration with JSON Logging?
The idea is to be able to group the log messages by the exchange.
Currently the ExchangeId is included in the "message" field when an
error happens:
"message": "Failed delivery for (MessageId:
4762099352DD338-0001 on ExchangeId:
4762099352DD338-0001). Exhausted after delivery attempt: 1
caught: org.apache.camel.http.base.HttpOperationFailedException: HTTP
operation failed invoking https://we
The JSON logging seems to use EcsLayout:
{
"@timestamp": "${json:timestamp}",
"log.level": "${json:level}",
"message": "${json:message}",
"process.thread.name": "${json:thread:name}",
"log.logger": "${json:logger:name}",
"labels": "${json:mdc}",
"tags": "${json:ndc}",
"error.type": "${json:exception:className}",
"error.message": "${json:exception:message}",
"error.stack_trace": "${json:exception:stackTrace:text}"
}
And I think the mdc (labels) or ndc (tags) could be a suitable place
to hold this information.
Also the idea is that if my integration contains a Log step:
- log:
message: Handling stuff ${header.stuffNo}
loggingLevel: DEBUG
When logged using the JSON Logging this also would contain the
ExchangeId in mdc/ndc.
What do you think?
Best regards,
Mikael
