[jira] [Updated] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jang-Vijay Singh updated CAMEL-20722: - Attachment: (was: Stats-after-10day-Jun2026-1.png) > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > Attachments: Stable-tests_2024-06-13.txt, > Stats-after-10day-Jun2026.png, Stats-before-10day-Apr2024.png, build-log.txt, > image-2024-06-27-07-57-48-320.png > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jang-Vijay Singh updated CAMEL-20722: - Attachment: image-2024-06-27-07-57-48-320.png > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > Attachments: Stable-tests_2024-06-13.txt, > Stats-after-10day-Jun2026-1.png, Stats-after-10day-Jun2026.png, > Stats-before-10day-Apr2024.png, build-log.txt, > image-2024-06-27-07-57-48-320.png > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jang-Vijay Singh updated CAMEL-20722: - Attachment: Stats-after-10day-Jun2026-1.png > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > Attachments: Stable-tests_2024-06-13.txt, > Stats-after-10day-Jun2026-1.png, Stats-after-10day-Jun2026.png, > Stats-before-10day-Apr2024.png, build-log.txt > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20893) camel-jms: simplify JmsRouteRequestReplyTest
[ https://issues.apache.org/jira/browse/CAMEL-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske reassigned CAMEL-20893: Assignee: Otavio Rodolfo Piske > camel-jms: simplify JmsRouteRequestReplyTest > > > Key: CAMEL-20893 > URL: https://issues.apache.org/jira/browse/CAMEL-20893 > Project: Camel > Issue Type: Task > Components: camel-jms >Affects Versions: 4.7.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > > The > [JmsRouteRequestReplyTest|https://github.com/apache/camel/blob/8112b251c9d7d3e2a8a3322c26cd983842fd525d/components/camel-jms/src/test/java/org/apache/camel/component/jms/JmsRouteRequestReplyTest.java] > test is outdated and unnecessarily complex to the point of making it hard to > do cleanups on other tests (not to mention the occasional flakiness). > > It needs to be refactored for simplicity, speed and ease of maintenance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20893) camel-jms: simplify JmsRouteRequestReplyTest
[ https://issues.apache.org/jira/browse/CAMEL-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-20893. -- Fix Version/s: 4.7.0 (was: 4.x) Resolution: Fixed Fixed with https://github.com/apache/camel/pull/14585. > camel-jms: simplify JmsRouteRequestReplyTest > > > Key: CAMEL-20893 > URL: https://issues.apache.org/jira/browse/CAMEL-20893 > Project: Camel > Issue Type: Task > Components: camel-jms >Affects Versions: 4.7.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > > The > [JmsRouteRequestReplyTest|https://github.com/apache/camel/blob/8112b251c9d7d3e2a8a3322c26cd983842fd525d/components/camel-jms/src/test/java/org/apache/camel/component/jms/JmsRouteRequestReplyTest.java] > test is outdated and unnecessarily complex to the point of making it hard to > do cleanups on other tests (not to mention the occasional flakiness). > > It needs to be refactored for simplicity, speed and ease of maintenance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jang-Vijay Singh updated CAMEL-20722: - Attachment: Stats-after-10day-Jun2026.png > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > Attachments: Stable-tests_2024-06-13.txt, > Stats-after-10day-Jun2026.png, Stats-before-10day-Apr2024.png, build-log.txt > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jang-Vijay Singh updated CAMEL-20722: - Attachment: Stats-before-10day-Apr2024.png > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > Attachments: Stable-tests_2024-06-13.txt, > Stats-after-10day-Jun2026.png, Stats-before-10day-Apr2024.png, build-log.txt > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860344#comment-17860344 ] Otavio Rodolfo Piske commented on CAMEL-20722: -- Looks a lot better since 4 days ago. I still see a recent failure for KafkaBreakOnFirstErrorWithBatchUsingAsyncCommitManagerIT, but overall everything looks much better than before. At this point, I am not sure if it's worth continuing looking at this (unless the fix is quick to implement). IMHO, we can mark this as complete and move on. Thanks [~jvsingh] for the great work stabilizing these tests. > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > Attachments: Stable-tests_2024-06-13.txt, build-log.txt > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20920) RouteLoader: Can't load a valid route with the same location after a previous load error
[
https://issues.apache.org/jira/browse/CAMEL-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20920.
-
Resolution: Fixed
> RouteLoader: Can't load a valid route with the same location after a previous
> load error
>
>
> Key: CAMEL-20920
> URL: https://issues.apache.org/jira/browse/CAMEL-20920
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Raymond
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
> Attachments: routeloader.zip
>
>
> I load XML routes from String as follows:
> {code:java}
> // Create resource from String
> String route = "\n" +
> " \n" +
> " \n" +
> "\n" +
> "XYZ\n" +
> "\n" +
> "";
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> // Load the routes
> RoutesLoader loader = PluginHelper.getRoutesLoader(context);
> loader.updateRoutes(resource); {code}
> In the above code example, I created the resource from String using the
> ResourceHelper class:
> {code:java}
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> {code}
> The _fromString_ method has two parameters "location" and "content". As a
> String doesn't really have a location I just use "dummy.xml" or something
> with an ID like this "123456.xml".
> This works with correct code and when the content has a mistake like invalid
> XML code, it returns an error.
> This is as expected, however when loading the route again with the correct
> XML Code with the same location parameter the loading fails. The loader still
> returns the previous error. When the location is changed to another name to
> route loads correctly.
>
> {color:#cc7832} {color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20920) RouteLoader: Can't load a valid route with the same location after a previous load error
[
https://issues.apache.org/jira/browse/CAMEL-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860343#comment-17860343
]
Claus Ibsen commented on CAMEL-20920:
-
Thanks for reporting and the reproducer
> RouteLoader: Can't load a valid route with the same location after a previous
> load error
>
>
> Key: CAMEL-20920
> URL: https://issues.apache.org/jira/browse/CAMEL-20920
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Raymond
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
> Attachments: routeloader.zip
>
>
> I load XML routes from String as follows:
> {code:java}
> // Create resource from String
> String route = "\n" +
> " \n" +
> " \n" +
> "\n" +
> "XYZ\n" +
> "\n" +
> "";
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> // Load the routes
> RoutesLoader loader = PluginHelper.getRoutesLoader(context);
> loader.updateRoutes(resource); {code}
> In the above code example, I created the resource from String using the
> ResourceHelper class:
> {code:java}
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> {code}
> The _fromString_ method has two parameters "location" and "content". As a
> String doesn't really have a location I just use "dummy.xml" or something
> with an ID like this "123456.xml".
> This works with correct code and when the content has a mistake like invalid
> XML code, it returns an error.
> This is as expected, however when loading the route again with the correct
> XML Code with the same location parameter the loading fails. The loader still
> returns the previous error. When the location is changed to another name to
> route loads correctly.
>
> {color:#cc7832} {color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860338#comment-17860338 ] Claus Ibsen commented on CAMEL-20722: - okay so this is fixed now ? > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > Attachments: Stable-tests_2024-06-13.txt, build-log.txt > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17502) add documentation about event notifier
[ https://issues.apache.org/jira/browse/CAMEL-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17502. - Fix Version/s: 4.7.0 (was: Future) Resolution: Fixed > add documentation about event notifier > -- > > Key: CAMEL-17502 > URL: https://issues.apache.org/jira/browse/CAMEL-17502 > Project: Camel > Issue Type: Improvement > Components: documentation >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > How to use a custom event notifier to listen to camel events, such as context > stopping etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20680) camel-kafka: reduce KafkaBreakOnFirstErrorSeekIssueIT test duration
[ https://issues.apache.org/jira/browse/CAMEL-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860229#comment-17860229 ] Jang-Vijay Singh commented on CAMEL-20680: -- After this PR, KafkaBreakOnFirstErrorSeekIssueIT now also runs stably on ppc64le and main CI with much lower execution time (~50sec) than originally observed (~450 sec): https://github.com/apache/camel/pull/14620 > camel-kafka: reduce KafkaBreakOnFirstErrorSeekIssueIT test duration > --- > > Key: CAMEL-20680 > URL: https://issues.apache.org/jira/browse/CAMEL-20680 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > Fix For: 4.x > > Attachments: image-2024-05-01-08-13-28-056.png > > > The test KafkaBreakOnFirstErrorSeekIssueIT takes a very long time to run. > This consumes unnecessary resources from ASF CI. We should investigate how to > improve it to it runs quickly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20794) Camel-kinesis: Kinesis producer has a very low throughtput
[ https://issues.apache.org/jira/browse/CAMEL-20794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20794. - Resolution: Fixed Thanks for contributing. More is welcome. > Camel-kinesis: Kinesis producer has a very low throughtput > -- > > Key: CAMEL-20794 > URL: https://issues.apache.org/jira/browse/CAMEL-20794 > Project: Camel > Issue Type: Improvement > Components: camel-aws2-kinesis >Reporter: Fan Yang >Assignee: Fan Yang >Priority: Minor > Fix For: 4.7.0 > > > Current kinesis producer can only send on record each time. It neither > supports sending records in batch, nor supports async sending. Therefore, the > throughput of kinesis producer is extremely low. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20827) Add endpoint service location to aws, azure and google componentd
[ https://issues.apache.org/jira/browse/CAMEL-20827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860212#comment-17860212 ] Andrea Cosentino commented on CAMEL-20827: -- I'll complete GCP this week. > Add endpoint service location to aws, azure and google componentd > - > > Key: CAMEL-20827 > URL: https://issues.apache.org/jira/browse/CAMEL-20827 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20913) Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session credentials for Cloudwatch and DynamoDB clients
[ https://issues.apache.org/jira/browse/CAMEL-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20913. -- Resolution: Fixed > Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session > credentials for Cloudwatch and DynamoDB clients > - > > Key: CAMEL-20913 > URL: https://issues.apache.org/jira/browse/CAMEL-20913 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20912) Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients
[ https://issues.apache.org/jira/browse/CAMEL-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20912: - Fix Version/s: 4.7.0 (was: 4.x) > Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and > DynamoDB Clients > --- > > Key: CAMEL-20912 > URL: https://issues.apache.org/jira/browse/CAMEL-20912 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20912) Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients
[ https://issues.apache.org/jira/browse/CAMEL-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20912. -- Resolution: Fixed > Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and > DynamoDB Clients > --- > > Key: CAMEL-20912 > URL: https://issues.apache.org/jira/browse/CAMEL-20912 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20913) Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session credentials for Cloudwatch and DynamoDB clients
[ https://issues.apache.org/jira/browse/CAMEL-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20913: - Fix Version/s: 4.7.0 (was: 4.x) > Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session > credentials for Cloudwatch and DynamoDB clients > - > > Key: CAMEL-20913 > URL: https://issues.apache.org/jira/browse/CAMEL-20913 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work stopped] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-20722 stopped by Jang-Vijay Singh. > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > Attachments: Stable-tests_2024-06-13.txt, build-log.txt > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20923) camel-jbang: Camel JBang is unable to load langchain4j embeddings
Otavio Rodolfo Piske created CAMEL-20923:
Summary: camel-jbang: Camel JBang is unable to load langchain4j
embeddings
Key: CAMEL-20923
URL: https://issues.apache.org/jira/browse/CAMEL-20923
Project: Camel
Issue Type: Task
Components: camel-jbang
Affects Versions: 4.7.0
Reporter: Otavio Rodolfo Piske
Fix For: 4.x
Camel JBang is unable to load langchain4j embeddings
{code:java}
[main][~/code/java/camel-jbang-explain]$ jbang
-Dcamel.jbang.version=4.7.0-SNAPSHOT camel@apache/camel explain whatis
--model-name=granite-code:8b --system-prompt="You are a coding assistant
specialized in Apache Camel" "How can I enable manual commits for the Kafka
component?"
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.apache.camel.jbang.ai.WhatIsCommand.doCall(WhatIsCommand.java:63)
at
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
at
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
at picocli.CommandLine.access$1500(CommandLine.java:148)
at
picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
at
picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
at picocli.CommandLine.execute(CommandLine.java:2174)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:167)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
at main.CamelJBang.main(CamelJBang.java:36)
Caused by: java.lang.RuntimeException: java.lang.NullPointerException: Cannot
invoke "java.io.InputStream.read(byte[], int, int)" because "inputStream" is
null
at
dev.langchain4j.model.embedding.OnnxBertBiEncoder.(OnnxBertBiEncoder.java:42)
at
dev.langchain4j.model.embedding.AbstractInProcessEmbeddingModel.loadFromJar(AbstractInProcessEmbeddingModel.java:22)
at
dev.langchain4j.model.embedding.AllMiniLmL6V2EmbeddingModel.(AllMiniLmL6V2EmbeddingModel.java:18)
... 14 more
Caused by: java.lang.NullPointerException: Cannot invoke
"java.io.InputStream.read(byte[], int, int)" because "inputStream" is null
at
dev.langchain4j.model.embedding.OnnxBertBiEncoder.loadModel(OnnxBertBiEncoder.java:229)
at
dev.langchain4j.model.embedding.OnnxBertBiEncoder.(OnnxBertBiEncoder.java:37)
... 16 more
{code}
This can be triggered by something such as:
{code:java}
@Override
public Integer doCall() throws Exception {
EmbeddingModel embeddingModel = new AllMiniLmL6V2EmbeddingModel();
}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20889) camel-core: Stream is not reset when Message.getBody(class) is invoked ans stream caching is enabled
[
https://issues.apache.org/jira/browse/CAMEL-20889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20889:
Fix Version/s: 4.7.0
> camel-core: Stream is not reset when Message.getBody(class) is invoked ans
> stream caching is enabled
>
>
> Key: CAMEL-20889
> URL: https://issues.apache.org/jira/browse/CAMEL-20889
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Reporter: Luigi De Masi
>Assignee: Luigi De Masi
>Priority: Major
> Fix For: 4.7.0
>
>
> Having the following Camel route on Camel 2.x
> {code:java}
> from("timer:mytimer2?repeatCount=1&delay=1000")
> .routeId("generate-route-marshall")
> .streamCaching()
> .transform(constant("\{\"maskme\":\"json payload\"}"))
> .marshal().json(JsonLibrary.Jackson)
> .process(exchange ->
> {
> LOGGER.info("body class name -> " +
> exchange.getIn().getBody().getClass().getName());
> LOGGER.info("consumed once using .getBody(String.class) -> " +
> exchange.getIn().getBody(String.class));
> LOGGER.info("consumed twice using .getBody(String.class) -> " +
> exchange.getIn().getBody(String.class));
> })
> .to("jms:queue:INCOMING");
> {code}
>
> Shows that the consumption of the message payload in the processor via
> {code:java}
> exchange.getIn().getBody(String.class));\{code}
> works as expected, as the body is shown twice on the logs, as follows.
> {code:java}
> body class name -> org.apache.camel.converter.stream.InputStreamCache
> consumed once using .getBody(String.class) -> "\{\"maskme\":\"json
> payload\"}"
> consumed twice using .getBody(String.class) -> "\{\"maskme\":\"json
> payload\"}"
> {code}
>
> But if you run this same route from Camel 3.x to the latest 4.x one, you
> will get the following output:
> {code:java}
> body class name -> org.apache.camel.converter.stream.InputStreamCache
> consumed once using .getBody(String.class) -> "\{\"maskme\":\"json
> payload\"}"
> consumed once using .getBody(String.class) ->
> {code}
>
> The problem is that on Camel 2.x, when
> {{ exchange.getIn().getBody(String.class))}}
> is called, the
> [org.apache.camel.converter.IOConverterOptimised|https://github.com/apache/camel/blob/camel-2.x/camel-core/src/main/java/org/apache/camel/converter/IOConverterOptimised.java]
> is triggered to convert the body from
> {{org.apache.camel.converter.stream.InputStreamCache}} to
> {{{}java.lang.String{}}}, which at the beginning of the convertion, [it reset
> the
> stream|https://github.com/apache/camel/blob/a05826ece32fbb8e2ba6df0e0ac2a3d5903f9572/camel-core/src/main/java/org/apache/camel/converter/IOConverterOptimised.java#L50]:
>
> {code:java|title=IOConverterOptimised.java}
> public final class IOConverterOptimised {
> private IOConverterOptimised() {
> }
> public static Object convertTo(final Class type, final Exchange
> exchange, final Object value) throws Exception {
> Class fromType = value.getClass();
> if (value instanceof StreamCache) {
> ((StreamCache)value).reset(); // <-- HERE
> }
> {code}
> From Camel 3.x,
> [org.apache.camel.converter.IOConverterOptimised|https://github.com/apache/camel/blob/camel-2.x/camel-core/src/main/java/org/apache/camel/converter/IOConverterOptimised.java]
> has been dropped, and
> [org.apache.camel.converter.IOConverter|https://github.com/apache/camel/blob/4c41ebcb73af761dcebf6e4ebb9a68e768e505a1/core/camel-base/src/main/java/org/apache/camel/converter/IOConverter.java]
> is used instead, which doesn't reset the stream.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20889) camel-core: Stream is not reset when Message.getBody(class) is invoked ans stream caching is enabled
[
https://issues.apache.org/jira/browse/CAMEL-20889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20889.
-
Resolution: Fixed
> camel-core: Stream is not reset when Message.getBody(class) is invoked ans
> stream caching is enabled
>
>
> Key: CAMEL-20889
> URL: https://issues.apache.org/jira/browse/CAMEL-20889
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Reporter: Luigi De Masi
>Assignee: Luigi De Masi
>Priority: Major
> Fix For: 4.7.0
>
>
> Having the following Camel route on Camel 2.x
> {code:java}
> from("timer:mytimer2?repeatCount=1&delay=1000")
> .routeId("generate-route-marshall")
> .streamCaching()
> .transform(constant("\{\"maskme\":\"json payload\"}"))
> .marshal().json(JsonLibrary.Jackson)
> .process(exchange ->
> {
> LOGGER.info("body class name -> " +
> exchange.getIn().getBody().getClass().getName());
> LOGGER.info("consumed once using .getBody(String.class) -> " +
> exchange.getIn().getBody(String.class));
> LOGGER.info("consumed twice using .getBody(String.class) -> " +
> exchange.getIn().getBody(String.class));
> })
> .to("jms:queue:INCOMING");
> {code}
>
> Shows that the consumption of the message payload in the processor via
> {code:java}
> exchange.getIn().getBody(String.class));\{code}
> works as expected, as the body is shown twice on the logs, as follows.
> {code:java}
> body class name -> org.apache.camel.converter.stream.InputStreamCache
> consumed once using .getBody(String.class) -> "\{\"maskme\":\"json
> payload\"}"
> consumed twice using .getBody(String.class) -> "\{\"maskme\":\"json
> payload\"}"
> {code}
>
> But if you run this same route from Camel 3.x to the latest 4.x one, you
> will get the following output:
> {code:java}
> body class name -> org.apache.camel.converter.stream.InputStreamCache
> consumed once using .getBody(String.class) -> "\{\"maskme\":\"json
> payload\"}"
> consumed once using .getBody(String.class) ->
> {code}
>
> The problem is that on Camel 2.x, when
> {{ exchange.getIn().getBody(String.class))}}
> is called, the
> [org.apache.camel.converter.IOConverterOptimised|https://github.com/apache/camel/blob/camel-2.x/camel-core/src/main/java/org/apache/camel/converter/IOConverterOptimised.java]
> is triggered to convert the body from
> {{org.apache.camel.converter.stream.InputStreamCache}} to
> {{{}java.lang.String{}}}, which at the beginning of the convertion, [it reset
> the
> stream|https://github.com/apache/camel/blob/a05826ece32fbb8e2ba6df0e0ac2a3d5903f9572/camel-core/src/main/java/org/apache/camel/converter/IOConverterOptimised.java#L50]:
>
> {code:java|title=IOConverterOptimised.java}
> public final class IOConverterOptimised {
> private IOConverterOptimised() {
> }
> public static Object convertTo(final Class type, final Exchange
> exchange, final Object value) throws Exception {
> Class fromType = value.getClass();
> if (value instanceof StreamCache) {
> ((StreamCache)value).reset(); // <-- HERE
> }
> {code}
> From Camel 3.x,
> [org.apache.camel.converter.IOConverterOptimised|https://github.com/apache/camel/blob/camel-2.x/camel-core/src/main/java/org/apache/camel/converter/IOConverterOptimised.java]
> has been dropped, and
> [org.apache.camel.converter.IOConverter|https://github.com/apache/camel/blob/4c41ebcb73af761dcebf6e4ebb9a68e768e505a1/core/camel-base/src/main/java/org/apache/camel/converter/IOConverter.java]
> is used instead, which doesn't reset the stream.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20920) RouteLoader: Can't load a valid route with the same location after a previous load error
[
https://issues.apache.org/jira/browse/CAMEL-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20920:
---
Assignee: Claus Ibsen
> RouteLoader: Can't load a valid route with the same location after a previous
> load error
>
>
> Key: CAMEL-20920
> URL: https://issues.apache.org/jira/browse/CAMEL-20920
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Raymond
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
> Attachments: routeloader.zip
>
>
> I load XML routes from String as follows:
> {code:java}
> // Create resource from String
> String route = "\n" +
> " \n" +
> " \n" +
> "\n" +
> "XYZ\n" +
> "\n" +
> "";
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> // Load the routes
> RoutesLoader loader = PluginHelper.getRoutesLoader(context);
> loader.updateRoutes(resource); {code}
> In the above code example, I created the resource from String using the
> ResourceHelper class:
> {code:java}
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> {code}
> The _fromString_ method has two parameters "location" and "content". As a
> String doesn't really have a location I just use "dummy.xml" or something
> with an ID like this "123456.xml".
> This works with correct code and when the content has a mistake like invalid
> XML code, it returns an error.
> This is as expected, however when loading the route again with the correct
> XML Code with the same location parameter the loading fails. The loader still
> returns the previous error. When the location is changed to another name to
> route loads correctly.
>
> {color:#cc7832} {color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20920) RouteLoader: Can't load a valid route with the same location after a previous load error
[
https://issues.apache.org/jira/browse/CAMEL-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20920:
Fix Version/s: 4.7.0
> RouteLoader: Can't load a valid route with the same location after a previous
> load error
>
>
> Key: CAMEL-20920
> URL: https://issues.apache.org/jira/browse/CAMEL-20920
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Raymond
>Priority: Minor
> Fix For: 4.7.0
>
> Attachments: routeloader.zip
>
>
> I load XML routes from String as follows:
> {code:java}
> // Create resource from String
> String route = "\n" +
> " \n" +
> " \n" +
> "\n" +
> "XYZ\n" +
> "\n" +
> "";
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> // Load the routes
> RoutesLoader loader = PluginHelper.getRoutesLoader(context);
> loader.updateRoutes(resource); {code}
> In the above code example, I created the resource from String using the
> ResourceHelper class:
> {code:java}
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> {code}
> The _fromString_ method has two parameters "location" and "content". As a
> String doesn't really have a location I just use "dummy.xml" or something
> with an ID like this "123456.xml".
> This works with correct code and when the content has a mistake like invalid
> XML code, it returns an error.
> This is as expected, however when loading the route again with the correct
> XML Code with the same location parameter the loading fails. The loader still
> returns the previous error. When the location is changed to another name to
> route loads correctly.
>
> {color:#cc7832} {color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20917) camel-jbang: Camel Jbang is unable to load external plugins
[
https://issues.apache.org/jira/browse/CAMEL-20917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske resolved CAMEL-20917.
--
Resolution: Fixed
Fixed with the linked PRs.
> camel-jbang: Camel Jbang is unable to load external plugins
> ---
>
> Key: CAMEL-20917
> URL: https://issues.apache.org/jira/browse/CAMEL-20917
> Project: Camel
> Issue Type: Task
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.7.0
>
>
> When trying to load a plugin defined as:
> {code:xml}
> org.apache.camel.jbang.ai
> camel-jbang-plugin-explain
> 1.0.0-SNAPSHOT
> {code}
> Then adding it to JBang as:
> {code:shell}
> jbang -Dcamel.jbang.version=4.7.0-SNAPSHOT camel@apache/camel plugin add -g
> org.apache.camel.jbang.ai -a camel-jbang-plugin-explain -v 1.0.0-SNAPSHOT -d
> "Explain things using AI" explain
> {code}
> Then, JBang fails to load the plugin with the following error:
> {code:java}
> Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not
> find artifact org.apache.camel:camel-jbang-plugin-explain:jar:4.7.0-SNAPSHOT
> in apache-snapshot (https://repository.apache.org/snapshots)
> {code}
> This happens because the group and version are hard-coded in the PluginHelper
> class.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20917) camel-jbang: Camel Jbang is unable to load external plugins
[
https://issues.apache.org/jira/browse/CAMEL-20917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860131#comment-17860131
]
Otavio Rodolfo Piske commented on CAMEL-20917:
--
Yes it is. Let me close this one.
> camel-jbang: Camel Jbang is unable to load external plugins
> ---
>
> Key: CAMEL-20917
> URL: https://issues.apache.org/jira/browse/CAMEL-20917
> Project: Camel
> Issue Type: Task
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.7.0
>
>
> When trying to load a plugin defined as:
> {code:xml}
> org.apache.camel.jbang.ai
> camel-jbang-plugin-explain
> 1.0.0-SNAPSHOT
> {code}
> Then adding it to JBang as:
> {code:shell}
> jbang -Dcamel.jbang.version=4.7.0-SNAPSHOT camel@apache/camel plugin add -g
> org.apache.camel.jbang.ai -a camel-jbang-plugin-explain -v 1.0.0-SNAPSHOT -d
> "Explain things using AI" explain
> {code}
> Then, JBang fails to load the plugin with the following error:
> {code:java}
> Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not
> find artifact org.apache.camel:camel-jbang-plugin-explain:jar:4.7.0-SNAPSHOT
> in apache-snapshot (https://repository.apache.org/snapshots)
> {code}
> This happens because the group and version are hard-coded in the PluginHelper
> class.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20917) camel-jbang: Camel Jbang is unable to load external plugins
[
https://issues.apache.org/jira/browse/CAMEL-20917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860125#comment-17860125
]
Claus Ibsen commented on CAMEL-20917:
-
I think this has been fixed now
> camel-jbang: Camel Jbang is unable to load external plugins
> ---
>
> Key: CAMEL-20917
> URL: https://issues.apache.org/jira/browse/CAMEL-20917
> Project: Camel
> Issue Type: Task
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.7.0
>
>
> When trying to load a plugin defined as:
> {code:xml}
> org.apache.camel.jbang.ai
> camel-jbang-plugin-explain
> 1.0.0-SNAPSHOT
> {code}
> Then adding it to JBang as:
> {code:shell}
> jbang -Dcamel.jbang.version=4.7.0-SNAPSHOT camel@apache/camel plugin add -g
> org.apache.camel.jbang.ai -a camel-jbang-plugin-explain -v 1.0.0-SNAPSHOT -d
> "Explain things using AI" explain
> {code}
> Then, JBang fails to load the plugin with the following error:
> {code:java}
> Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not
> find artifact org.apache.camel:camel-jbang-plugin-explain:jar:4.7.0-SNAPSHOT
> in apache-snapshot (https://repository.apache.org/snapshots)
> {code}
> This happens because the group and version are hard-coded in the PluginHelper
> class.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20794) Camel-kinesis: Kinesis producer has a very low throughtput
[ https://issues.apache.org/jira/browse/CAMEL-20794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860126#comment-17860126 ] Claus Ibsen commented on CAMEL-20794: - a PR for to add some details in the doc is welcome > Camel-kinesis: Kinesis producer has a very low throughtput > -- > > Key: CAMEL-20794 > URL: https://issues.apache.org/jira/browse/CAMEL-20794 > Project: Camel > Issue Type: Improvement > Components: camel-aws2-kinesis >Reporter: Fan Yang >Assignee: Fan Yang >Priority: Minor > Fix For: 4.7.0 > > > Current kinesis producer can only send on record each time. It neither > supports sending records in batch, nor supports async sending. Therefore, the > throughput of kinesis producer is extremely low. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20922) Camel-crypto: Extract PGPdataFormat to another component
[ https://issues.apache.org/jira/browse/CAMEL-20922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20922. - Resolution: Fixed > Camel-crypto: Extract PGPdataFormat to another component > > > Key: CAMEL-20922 > URL: https://issues.apache.org/jira/browse/CAMEL-20922 > Project: Camel > Issue Type: Improvement > Components: camel-crypto >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 4.7.0 > > > In order to run crypto component on FIPS systems we have to use BC-FIPS > instead of standard bouncycastle. > * PGPDataFormat uses BC APIs but does not require any BC security provider, > therefore BCFIPS can not be used as a replacement for PGP APIs. > * Another restriction is that BC and BCFIps can not co-exist on the > classpath. > * Therefore crypto component can not contain PGP, to allow BC-FIPS > substitution > The new component with PGP data format should be called probably > camel-crypto-pgp > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20918) Salesforce component does not resubscribe after exception
[ https://issues.apache.org/jira/browse/CAMEL-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860094#comment-17860094 ] Claus Ibsen commented on CAMEL-20918: - Can you update the details about this. And give 4.4.3 a try when its released later this week > Salesforce component does not resubscribe after exception > - > > Key: CAMEL-20918 > URL: https://issues.apache.org/jira/browse/CAMEL-20918 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.22.2, 4.4.2, 4.6.0 >Reporter: Bartosz Popiela >Priority: Major > > TODO will be updated -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20922) Camel-crypto: Extract PGPdataFormat to another component
[ https://issues.apache.org/jira/browse/CAMEL-20922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20922: Fix Version/s: 4.7.0 > Camel-crypto: Extract PGPdataFormat to another component > > > Key: CAMEL-20922 > URL: https://issues.apache.org/jira/browse/CAMEL-20922 > Project: Camel > Issue Type: New Feature > Components: camel-crypto >Affects Versions: 4.7.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 4.7.0 > > > In order to run crypto component on FIPS systems we have to use BC-FIPS > instead of standard bouncycastle. > * PGPDataFormat uses BC APIs but does not require any BC security provider, > therefore BCFIPS can not be used as a replacement for PGP APIs. > * Another restriction is that BC and BCFIps can not co-exist on the > classpath. > * Therefore crypto component can not contain PGP, to allow BC-FIPS > substitution > The new component with PGP data format should be called probably > camel-crypto-pgp > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20922) Camel-crypto: Extract PGPdataFormat to another component
[ https://issues.apache.org/jira/browse/CAMEL-20922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20922: Issue Type: Improvement (was: Task) > Camel-crypto: Extract PGPdataFormat to another component > > > Key: CAMEL-20922 > URL: https://issues.apache.org/jira/browse/CAMEL-20922 > Project: Camel > Issue Type: Improvement > Components: camel-crypto >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 4.7.0 > > > In order to run crypto component on FIPS systems we have to use BC-FIPS > instead of standard bouncycastle. > * PGPDataFormat uses BC APIs but does not require any BC security provider, > therefore BCFIPS can not be used as a replacement for PGP APIs. > * Another restriction is that BC and BCFIps can not co-exist on the > classpath. > * Therefore crypto component can not contain PGP, to allow BC-FIPS > substitution > The new component with PGP data format should be called probably > camel-crypto-pgp > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20922) Camel-crypto: Extract PGPdataFormat to another component
[ https://issues.apache.org/jira/browse/CAMEL-20922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20922: Issue Type: Task (was: New Feature) > Camel-crypto: Extract PGPdataFormat to another component > > > Key: CAMEL-20922 > URL: https://issues.apache.org/jira/browse/CAMEL-20922 > Project: Camel > Issue Type: Task > Components: camel-crypto >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 4.7.0 > > > In order to run crypto component on FIPS systems we have to use BC-FIPS > instead of standard bouncycastle. > * PGPDataFormat uses BC APIs but does not require any BC security provider, > therefore BCFIPS can not be used as a replacement for PGP APIs. > * Another restriction is that BC and BCFIps can not co-exist on the > classpath. > * Therefore crypto component can not contain PGP, to allow BC-FIPS > substitution > The new component with PGP data format should be called probably > camel-crypto-pgp > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20922) Camel-crypto: Extract PGPdataFormat to another component
[ https://issues.apache.org/jira/browse/CAMEL-20922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20922: Affects Version/s: (was: 4.7.0) > Camel-crypto: Extract PGPdataFormat to another component > > > Key: CAMEL-20922 > URL: https://issues.apache.org/jira/browse/CAMEL-20922 > Project: Camel > Issue Type: New Feature > Components: camel-crypto >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 4.7.0 > > > In order to run crypto component on FIPS systems we have to use BC-FIPS > instead of standard bouncycastle. > * PGPDataFormat uses BC APIs but does not require any BC security provider, > therefore BCFIPS can not be used as a replacement for PGP APIs. > * Another restriction is that BC and BCFIps can not co-exist on the > classpath. > * Therefore crypto component can not contain PGP, to allow BC-FIPS > substitution > The new component with PGP data format should be called probably > camel-crypto-pgp > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-20905) camel-djl - Support more model applications
[ https://issues.apache.org/jira/browse/CAMEL-20905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-20905 started by Tadayoshi Sato. -- > camel-djl - Support more model applications > --- > > Key: CAMEL-20905 > URL: https://issues.apache.org/jira/browse/CAMEL-20905 > Project: Camel > Issue Type: New Feature > Components: camel-ai >Affects Versions: 4.6.0 >Reporter: Tadayoshi Sato >Assignee: Tadayoshi Sato >Priority: Major > > Currently, the following applications are only supported: > - Image Classification > - Object Detection > There are many more applications and the component should support them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20922) Camel-crypto: Extract PGPdataFormat to another component
Jiri Ondrusek created CAMEL-20922: - Summary: Camel-crypto: Extract PGPdataFormat to another component Key: CAMEL-20922 URL: https://issues.apache.org/jira/browse/CAMEL-20922 Project: Camel Issue Type: New Feature Components: camel-crypto Affects Versions: 4.7.0 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek In order to run crypto component on FIPS systems we have to use BC-FIPS instead of standard bouncycastle. * PGPDataFormat uses BC APIs but does not require any BC security provider, therefore BCFIPS can not be used as a replacement for PGP APIs. * Another restriction is that BC and BCFIps can not co-exist on the classpath. * Therefore crypto component can not contain PGP, to allow BC-FIPS substitution The new component with PGP data format should be called probably camel-crypto-pgp -- This message was sent by Atlassian Jira (v8.20.10#820010)
