[jira] [Commented] (CAMEL-21620) camel-core - Fix onWhen to not include outputs in model
[ https://issues.apache.org/jira/browse/CAMEL-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913319#comment-17913319 ] Claus Ibsen commented on CAMEL-21620: - The interceptSendToEndpoint is a bit tricky to refactor to resolve this > camel-core - Fix onWhen to not include outputs in model > --- > > Key: CAMEL-21620 > URL: https://issues.apache.org/jira/browse/CAMEL-21620 > Project: Camel > Issue Type: Task > Components: camel-core, dsl >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.10.0 > > > Only when in choice should have outputs. The onWhen used in filter, doCatch, > intercept, onCompletion should be a predicate only without outputs. However > since it reused the when from choice the model has outputs. Its a bit tricky > to fix due to the model being old and classic spring xml XSD. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21614) Simple expressions execute forever. Thread is RUNNABLE for ever. Issue appears with bean expressions inside simple expressions on SimpleLRUCache
[
https://issues.apache.org/jira/browse/CAMEL-21614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Filotto resolved CAMEL-21614.
-
Resolution: Fixed
> Simple expressions execute forever. Thread is RUNNABLE for ever. Issue
> appears with bean expressions inside simple expressions on SimpleLRUCache
>
>
> Key: CAMEL-21614
> URL: https://issues.apache.org/jira/browse/CAMEL-21614
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.8.2
> Environment: jdk-21.0.2+13 (Eclipse Temurin)
> Spring Boot 3.3.6
> Camel 4.8.2
>Reporter: Jannik Schmeier
>Assignee: Nicolas Filotto
>Priority: Major
> Fix For: 4.8.4, 4.10.0
>
>
> This is a Follow-Up on this issue: CAMEL-21467
> Unfortunately we are still experiencing the same issue with threads getting
> stuck in the state RUNNABLE. It seems like the frequency of the issue has
> greatly decreased though. We have had it twice in about a month.
>
> Threaddump:
> {noformat}
> "Camel (camel-1) thread #4 - timer://my-timer" - Thread t@65
> java.lang.Thread.State: RUNNABLE
> at
> org.apache.camel.support.cache.SimpleLRUCache$OperationContext.close(SimpleLRUCache.java:309)
> at
> org.apache.camel.support.cache.SimpleLRUCache.put(SimpleLRUCache.java:104)
> at
> org.apache.camel.support.cache.SimpleSoftCache.put(SimpleSoftCache.java:114)
> at
> org.apache.camel.component.bean.BeanComponent.addBeanInfoToCache(BeanComponent.java:96)
> at org.apache.camel.component.bean.BeanInfo.(BeanInfo.java:169)
> at
> org.apache.camel.component.bean.ConstantBeanHolder.(ConstantBeanHolder.java:50)
> at
> org.apache.camel.language.bean.BeanExpression.createBeanHolder(BeanExpression.java:303)
> at
> org.apache.camel.language.bean.BeanExpression.init(BeanExpression.java:175)
> at
> org.apache.camel.language.bean.BeanLanguage.createExpression(BeanLanguage.java:148)
> at
> org.apache.camel.language.simple.SimpleExpressionBuilder$KeyedOgnlExpressionAdapter.evaluate(SimpleExpressionBuilder.java:1251)
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45)
> at
> org.apache.camel.support.builder.ExpressionBuilder$62.evaluate(ExpressionBuilder.java:2105)
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45)
> at org.apache.camel.processor.LogProcessor.process(LogProcessor.java:71)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:808)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:714)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:84)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:178)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.processTransacted(CamelInternalProcessor.java:390)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:320)
> at org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:102)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:84)
> at
> org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:32)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.processTransacted(CamelInternalProcessor.java:390)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:320)
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:102)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:208)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:
[jira] [Commented] (CAMEL-21539) Vector Database capabilities - Infinispan
[
https://issues.apache.org/jira/browse/CAMEL-21539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913279#comment-17913279
]
James Netherton commented on CAMEL-21539:
-
I have a POC where I can store and query an embedding created by Langchain4j.
It works in a similar way to the Langchain4j Infinispan embedding store. I
added options so you can configure the vector dimension, similarity and the
distance value to use in kNN searches.
Example usage with langchain4j-embeddings:
{code:java}
// Store an embedding
from("direct:put")
.to("langchain4j-embeddings:test")
.transform(new DataType("infinispan:embeddings"))
.to("infinispan:test%s?embeddingStoreDimension=3");
// Query embeddings using a pre-baked kNN query
from("direct:query")
.to("langchain4j-embeddings:test")
.setHeader(InfinispanConstants.OPERATION).constant(InfinispanOperation.QUERY)
.transform(new DataType("infinispan:embeddings"))
.to("infinispan:test?embeddingStoreDimension=3");
{code}
[~zbendhiba] WDYT?
> Vector Database capabilities - Infinispan
> -
>
> Key: CAMEL-21539
> URL: https://issues.apache.org/jira/browse/CAMEL-21539
> Project: Camel
> Issue Type: New Feature
>Reporter: Zineb Bendhiba
>Assignee: James Netherton
>Priority: Major
>
> Implement Vector search capabilities for Infinispan.
> Also add the langchain4j Embeddings DataFormat for Infinispan + an
> Integration test in the langchain4j embeddings directory
> https://github.com/apache/camel/tree/main/components/camel-ai/camel-langchain4j-embeddings/src/test/java/org/apache/camel/component/langchain4j/embeddings
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21624) Issue with Kafka Appender when using multiline YAML configuration for bootstrap.servers
[
https://issues.apache.org/jira/browse/CAMEL-21624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21624:
Issue Type: Improvement (was: Bug)
> Issue with Kafka Appender when using multiline YAML configuration for
> bootstrap.servers
> ---
>
> Key: CAMEL-21624
> URL: https://issues.apache.org/jira/browse/CAMEL-21624
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
>Affects Versions: 4.9.0
>Reporter: Nadina Florea
>Priority: Minor
>
> Hello,
> I recently encountered an issue in my application that uses Apache Camel
> 4.9.0 along with the Kafka component (camel-kafka) for message processing.
> The issue arises due to the interaction between Camel’s Kafka configuration
> and Kafka Appender when *bootstrap.servers is defined using a {_}multiline
> syntax in a YAML configuration file{_}.*
> Environment:
> • Apache Camel Version: 4.9.0
> • Spring Boot Version: 3.4.1
> • Kafka Clients Version: 3.8.1
> • Java Version: 17
> Steps to Reproduce:
> 1. Define bootstrap.servers in application.yaml using multiline syntax:
> {code:java}
> camel:
> component:
> kafka:
> brokers: >-
> broker1:9092,
> broker2:9092{code}
> 2. Use the following setup in logback-spring.xml to configure Kafka Appender:
> {code:java}
>
>
>
> bootstrap.servers=${brokers}
>
> {code}
> 3. Run the application.
> Observed Behavior:
> The application fails to start with the following error:
> _*org.apache.camel.RuntimeCamelException:
> org.apache.kafka.common.config.ConfigException: Invalid url in
> bootstrap.servers: broker2:9092*_
> Expected Behavior:
> The bootstrap.servers property should be processed correctly, even if defined
> in a multiline YAML syntax, as it worked with older Kafka Clients versions
> (e.g., 3.7.x).
> After investigating, I suspect the following change in Kafka Clients 3.8.x:
> • Starting with Kafka Clients 3.8.x, stricter validation for
> _bootstrap.servers_ was introduced via KAFKA-17584. This validation now
> rejects newline characters or other formatting inconsistencies.
> • While this is expected behavior, the way Camel propagates the
> camel.component.kafka.brokers property to Kafka Appender through
> logback-spring.xml seems to preserve newline characters, which results in
> invalid configuration values.
> Additional Notes:
> • When I updated my YAML configuration to write *bootstrap.servers on a
> single line* (e.g., broker1:9092,broker2:9092), the issue was resolved.
> • _Applications that use Spring Kafka directly without Camel are not affected
> by this issue._
>
> When configuring numerous brokers in the _bootstrap.servers_ property, it is
> difficult to read and manage when placed on a single line.
>
> Is this behavior intentional or should Camel consider providing a more
> flexible way to handle multiline configs in the future?
> Thank you!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21624) Issue with Kafka Appender when using multiline YAML configuration for bootstrap.servers
[
https://issues.apache.org/jira/browse/CAMEL-21624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913309#comment-17913309
]
Claus Ibsen commented on CAMEL-21624:
-
You should ask the Apache Kafka project as they changed their behaviour. Camel
Spring Boot just configures the values using standard Spring Boot
auto-configuration. So change your configuration to be a single line to make it
work.
The camel-kafka component can be improved to try to remove new-line in this
option, you are welcome to attempt to do that and send a PR.
> Issue with Kafka Appender when using multiline YAML configuration for
> bootstrap.servers
> ---
>
> Key: CAMEL-21624
> URL: https://issues.apache.org/jira/browse/CAMEL-21624
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 4.9.0
>Reporter: Nadina Florea
>Priority: Major
>
> Hello,
> I recently encountered an issue in my application that uses Apache Camel
> 4.9.0 along with the Kafka component (camel-kafka) for message processing.
> The issue arises due to the interaction between Camel’s Kafka configuration
> and Kafka Appender when *bootstrap.servers is defined using a {_}multiline
> syntax in a YAML configuration file{_}.*
> Environment:
> • Apache Camel Version: 4.9.0
> • Spring Boot Version: 3.4.1
> • Kafka Clients Version: 3.8.1
> • Java Version: 17
> Steps to Reproduce:
> 1. Define bootstrap.servers in application.yaml using multiline syntax:
> {code:java}
> camel:
> component:
> kafka:
> brokers: >-
> broker1:9092,
> broker2:9092{code}
> 2. Use the following setup in logback-spring.xml to configure Kafka Appender:
> {code:java}
>
>
>
> bootstrap.servers=${brokers}
>
> {code}
> 3. Run the application.
> Observed Behavior:
> The application fails to start with the following error:
> _*org.apache.camel.RuntimeCamelException:
> org.apache.kafka.common.config.ConfigException: Invalid url in
> bootstrap.servers: broker2:9092*_
> Expected Behavior:
> The bootstrap.servers property should be processed correctly, even if defined
> in a multiline YAML syntax, as it worked with older Kafka Clients versions
> (e.g., 3.7.x).
> After investigating, I suspect the following change in Kafka Clients 3.8.x:
> • Starting with Kafka Clients 3.8.x, stricter validation for
> _bootstrap.servers_ was introduced via KAFKA-17584. This validation now
> rejects newline characters or other formatting inconsistencies.
> • While this is expected behavior, the way Camel propagates the
> camel.component.kafka.brokers property to Kafka Appender through
> logback-spring.xml seems to preserve newline characters, which results in
> invalid configuration values.
> Additional Notes:
> • When I updated my YAML configuration to write *bootstrap.servers on a
> single line* (e.g., broker1:9092,broker2:9092), the issue was resolved.
> • _Applications that use Spring Kafka directly without Camel are not affected
> by this issue._
>
> When configuring numerous brokers in the _bootstrap.servers_ property, it is
> difficult to read and manage when placed on a single line.
>
> Is this behavior intentional or should Camel consider providing a more
> flexible way to handle multiline configs in the future?
> Thank you!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21624) Issue with Kafka Appender when using multiline YAML configuration for bootstrap.servers
[
https://issues.apache.org/jira/browse/CAMEL-21624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21624:
Priority: Minor (was: Major)
> Issue with Kafka Appender when using multiline YAML configuration for
> bootstrap.servers
> ---
>
> Key: CAMEL-21624
> URL: https://issues.apache.org/jira/browse/CAMEL-21624
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 4.9.0
>Reporter: Nadina Florea
>Priority: Minor
>
> Hello,
> I recently encountered an issue in my application that uses Apache Camel
> 4.9.0 along with the Kafka component (camel-kafka) for message processing.
> The issue arises due to the interaction between Camel’s Kafka configuration
> and Kafka Appender when *bootstrap.servers is defined using a {_}multiline
> syntax in a YAML configuration file{_}.*
> Environment:
> • Apache Camel Version: 4.9.0
> • Spring Boot Version: 3.4.1
> • Kafka Clients Version: 3.8.1
> • Java Version: 17
> Steps to Reproduce:
> 1. Define bootstrap.servers in application.yaml using multiline syntax:
> {code:java}
> camel:
> component:
> kafka:
> brokers: >-
> broker1:9092,
> broker2:9092{code}
> 2. Use the following setup in logback-spring.xml to configure Kafka Appender:
> {code:java}
>
>
>
> bootstrap.servers=${brokers}
>
> {code}
> 3. Run the application.
> Observed Behavior:
> The application fails to start with the following error:
> _*org.apache.camel.RuntimeCamelException:
> org.apache.kafka.common.config.ConfigException: Invalid url in
> bootstrap.servers: broker2:9092*_
> Expected Behavior:
> The bootstrap.servers property should be processed correctly, even if defined
> in a multiline YAML syntax, as it worked with older Kafka Clients versions
> (e.g., 3.7.x).
> After investigating, I suspect the following change in Kafka Clients 3.8.x:
> • Starting with Kafka Clients 3.8.x, stricter validation for
> _bootstrap.servers_ was introduced via KAFKA-17584. This validation now
> rejects newline characters or other formatting inconsistencies.
> • While this is expected behavior, the way Camel propagates the
> camel.component.kafka.brokers property to Kafka Appender through
> logback-spring.xml seems to preserve newline characters, which results in
> invalid configuration values.
> Additional Notes:
> • When I updated my YAML configuration to write *bootstrap.servers on a
> single line* (e.g., broker1:9092,broker2:9092), the issue was resolved.
> • _Applications that use Spring Kafka directly without Camel are not affected
> by this issue._
>
> When configuring numerous brokers in the _bootstrap.servers_ property, it is
> difficult to read and manage when placed on a single line.
>
> Is this behavior intentional or should Camel consider providing a more
> flexible way to handle multiline configs in the future?
> Thank you!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21624) Issue with Kafka Appender when using multiline YAML configuration for bootstrap.servers
Nadina Florea created CAMEL-21624:
-
Summary: Issue with Kafka Appender when using multiline YAML
configuration for bootstrap.servers
Key: CAMEL-21624
URL: https://issues.apache.org/jira/browse/CAMEL-21624
Project: Camel
Issue Type: Bug
Components: camel-kafka
Affects Versions: 4.9.0
Reporter: Nadina Florea
Hello,
I recently encountered an issue in my application that uses Apache Camel 4.9.0
along with the Kafka component (camel-kafka) for message processing. The issue
arises due to the interaction between Camel’s Kafka configuration and Kafka
Appender when *bootstrap.servers is defined using a {_}multiline syntax in a
YAML configuration file{_}.*
Environment:
• Apache Camel Version: 4.9.0
• Spring Boot Version: 3.4.1
• Kafka Clients Version: 3.8.1
• Java Version: 17
Steps to Reproduce:
1. Define bootstrap.servers in application.yaml using multiline syntax:
{code:java}
camel:
component:
kafka:
brokers: >-
broker1:9092,
broker2:9092{code}
2. Use the following setup in logback-spring.xml to configure Kafka Appender:
{code:java}
bootstrap.servers=${brokers}
{code}
3. Run the application.
Observed Behavior:
The application fails to start with the following error:
_*org.apache.camel.RuntimeCamelException:
org.apache.kafka.common.config.ConfigException: Invalid url in
bootstrap.servers: broker2:9092*_
Expected Behavior:
The bootstrap.servers property should be processed correctly, even if defined
in a multiline YAML syntax, as it worked with older Kafka Clients versions
(e.g., 3.7.x).
After investigating, I suspect the following change in Kafka Clients 3.8.x:
• Starting with Kafka Clients 3.8.x, stricter validation for
_bootstrap.servers_ was introduced via KAFKA-17584. This validation now rejects
newline characters or other formatting inconsistencies.
• While this is expected behavior, the way Camel propagates the
camel.component.kafka.brokers property to Kafka Appender through
logback-spring.xml seems to preserve newline characters, which results in
invalid configuration values.
Additional Notes:
• When I updated my YAML configuration to write *bootstrap.servers on a single
line* (e.g., broker1:9092,broker2:9092), the issue was resolved.
• _Applications that use Spring Kafka directly without Camel are not affected
by this issue._
When configuring numerous brokers in the _bootstrap.servers_ property, it is
difficult to read and manage when placed on a single line.
Is this behavior intentional or should Camel consider providing a more flexible
way to handle multiline configs in the future?
Thank you!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21621) camel-jbang - k8s-httpclient-vertx fails in shutdown hook
[
https://issues.apache.org/jira/browse/CAMEL-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-21621.
--
Resolution: Fixed
> camel-jbang - k8s-httpclient-vertx fails in shutdown hook
> -
>
> Key: CAMEL-21621
> URL: https://issues.apache.org/jira/browse/CAMEL-21621
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.10.0
>
>
> {code}
> Exception in thread "Camel Thread #7 - CamelShutdownInterceptor"
> java.lang.RuntimeException: java.lang.IllegalStateException: Client is closed
> at
> org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesRun.lambda$installShutdownHook$10(KubernetesRun.java:514)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.lang.IllegalStateException: Client is closed
> at
> io.vertx.core.http.impl.HttpClientImpl.checkClosed(HttpClientImpl.java:405)
> at
> io.vertx.core.http.impl.HttpClientImpl.doRequest(HttpClientImpl.java:281)
> at
> io.vertx.core.http.impl.HttpClientImpl.request(HttpClientImpl.java:191)
> at
> io.fabric8.kubernetes.client.vertx.VertxHttpRequest.consumeBytes(VertxHttpRequest.java:124)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21621) camel-jbang - k8s-httpclient-vertx fails in shutdown hook
[
https://issues.apache.org/jira/browse/CAMEL-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21621:
-
Fix Version/s: 4.10.0
> camel-jbang - k8s-httpclient-vertx fails in shutdown hook
> -
>
> Key: CAMEL-21621
> URL: https://issues.apache.org/jira/browse/CAMEL-21621
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.10.0
>
>
> {code}
> Exception in thread "Camel Thread #7 - CamelShutdownInterceptor"
> java.lang.RuntimeException: java.lang.IllegalStateException: Client is closed
> at
> org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesRun.lambda$installShutdownHook$10(KubernetesRun.java:514)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.lang.IllegalStateException: Client is closed
> at
> io.vertx.core.http.impl.HttpClientImpl.checkClosed(HttpClientImpl.java:405)
> at
> io.vertx.core.http.impl.HttpClientImpl.doRequest(HttpClientImpl.java:281)
> at
> io.vertx.core.http.impl.HttpClientImpl.request(HttpClientImpl.java:191)
> at
> io.fabric8.kubernetes.client.vertx.VertxHttpRequest.consumeBytes(VertxHttpRequest.java:124)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21620) camel-core - Fix onWhen to not include outputs in model
[ https://issues.apache.org/jira/browse/CAMEL-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913586#comment-17913586 ] Claus Ibsen commented on CAMEL-21620: - The choice when/otherwise and doTry / doCatch / doFinally is more complex. So lets get this work merged first. > camel-core - Fix onWhen to not include outputs in model > --- > > Key: CAMEL-21620 > URL: https://issues.apache.org/jira/browse/CAMEL-21620 > Project: Camel > Issue Type: Task > Components: camel-core, dsl >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.10.0 > > > Only when in choice should have outputs. The onWhen used in filter, doCatch, > intercept, onCompletion should be a predicate only without outputs. However > since it reused the when from choice the model has outputs. Its a bit tricky > to fix due to the model being old and classic spring xml XSD. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21626) hashicorp vault cloud component
Claus Ibsen created CAMEL-21626:
---
Summary: hashicorp vault cloud component
Key: CAMEL-21626
URL: https://issues.apache.org/jira/browse/CAMEL-21626
Project: Camel
Issue Type: New Feature
Components: camel-hashicorp-vault
Reporter: Claus Ibsen
Fix For: 4.x
Our current component is for on-prem hashicorp. If you use their cloud solution
then you cannot use what we have today in Camel.
I dont know if the cloud can use the java library or something else may be
needed.
But it would be good to have a security vault integration with this so you can
use
{code:java}
{{hashicorp-cloud:myKey}} {code}
placeholders in Camel routes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21620) camel-core - Fix onWhen to not include outputs in model
[ https://issues.apache.org/jira/browse/CAMEL-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913345#comment-17913345 ] Claus Ibsen edited comment on CAMEL-21620 at 1/15/25 8:47 PM: -- TODO: Make when special for choice only. TODO: Avoid onWhen/onFallback generated as processors into the XML XSD *DONE* was (Author: davsclaus): TODO: Make when special for choice only. TODO: Avoid when/onWhen/onFallback generated as processors into the XML XSD > camel-core - Fix onWhen to not include outputs in model > --- > > Key: CAMEL-21620 > URL: https://issues.apache.org/jira/browse/CAMEL-21620 > Project: Camel > Issue Type: Task > Components: camel-core, dsl >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.10.0 > > > Only when in choice should have outputs. The onWhen used in filter, doCatch, > intercept, onCompletion should be a predicate only without outputs. However > since it reused the when from choice the model has outputs. Its a bit tricky > to fix due to the model being old and classic spring xml XSD. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21625) camel k8s run may not cleanup properly on openshift
Thomas Diesler created CAMEL-21625:
--
Summary: camel k8s run may not cleanup properly on openshift
Key: CAMEL-21625
URL: https://issues.apache.org/jira/browse/CAMEL-21625
Project: Camel
Issue Type: Bug
Components: camel-jbang
Reporter: Thomas Diesler
Assignee: Thomas Diesler
{code}
Exception in thread "Camel Thread #7 - CamelShutdownInterceptor"
java.lang.RuntimeException: java.io.FileNotFoundException: Unable to resolve
Kubernetes manifest file type `yml` in folder:
.camel-jbang-run/timer-log/target/kubernetes
at
org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesRun.lambda$installShutdownHook$10(KubernetesRun.java:514)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.io.FileNotFoundException: Unable to resolve Kubernetes manifest
file type `yml` in folder: .camel-jbang-run/timer-log/target/kubernetes
at
org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesHelper.resolveKubernetesManifest(KubernetesHelper.java:207)
at
org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesHelper.resolveKubernetesManifest(KubernetesHelper.java:194)
at
org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesDelete.doCall(KubernetesDelete.java:86)
at
org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesRun.lambda$installShutdownHook$10(KubernetesRun.java:511)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21620) camel-core - Fix onWhen to not include outputs in model
[ https://issues.apache.org/jira/browse/CAMEL-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913319#comment-17913319 ] Claus Ibsen edited comment on CAMEL-21620 at 1/15/25 3:12 PM: -- The interceptSendToEndpoint is a bit tricky to refactor to resolve this *DONE* was (Author: davsclaus): The interceptSendToEndpoint is a bit tricky to refactor to resolve this > camel-core - Fix onWhen to not include outputs in model > --- > > Key: CAMEL-21620 > URL: https://issues.apache.org/jira/browse/CAMEL-21620 > Project: Camel > Issue Type: Task > Components: camel-core, dsl >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.10.0 > > > Only when in choice should have outputs. The onWhen used in filter, doCatch, > intercept, onCompletion should be a predicate only without outputs. However > since it reused the when from choice the model has outputs. Its a bit tricky > to fix due to the model being old and classic spring xml XSD. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21621) camel-jbang - k8s-httpclient-vertx fails in shutdown hook
[
https://issues.apache.org/jira/browse/CAMEL-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913347#comment-17913347
]
Thomas Diesler commented on CAMEL-21621:
CrossRef: https://github.com/fabric8io/kubernetes-client/issues/6792
> camel-jbang - k8s-httpclient-vertx fails in shutdown hook
> -
>
> Key: CAMEL-21621
> URL: https://issues.apache.org/jira/browse/CAMEL-21621
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.10.0
>
>
> {code}
> Exception in thread "Camel Thread #7 - CamelShutdownInterceptor"
> java.lang.RuntimeException: java.lang.IllegalStateException: Client is closed
> at
> org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesRun.lambda$installShutdownHook$10(KubernetesRun.java:514)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.lang.IllegalStateException: Client is closed
> at
> io.vertx.core.http.impl.HttpClientImpl.checkClosed(HttpClientImpl.java:405)
> at
> io.vertx.core.http.impl.HttpClientImpl.doRequest(HttpClientImpl.java:281)
> at
> io.vertx.core.http.impl.HttpClientImpl.request(HttpClientImpl.java:191)
> at
> io.fabric8.kubernetes.client.vertx.VertxHttpRequest.consumeBytes(VertxHttpRequest.java:124)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21614) Simple expressions execute forever. Thread is RUNNABLE for ever. Issue appears with bean expressions inside simple expressions on SimpleLRUCache
[
https://issues.apache.org/jira/browse/CAMEL-21614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913349#comment-17913349
]
Nicolas Filotto commented on CAMEL-21614:
-
[~shmyer] I published new snapshots (4.8.4-SNAPSHOT) with the fix into
https://repository.apache.org/content/repositories/snapshots, feel free to test
them and provide a feedback.
> Simple expressions execute forever. Thread is RUNNABLE for ever. Issue
> appears with bean expressions inside simple expressions on SimpleLRUCache
>
>
> Key: CAMEL-21614
> URL: https://issues.apache.org/jira/browse/CAMEL-21614
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.8.2
> Environment: jdk-21.0.2+13 (Eclipse Temurin)
> Spring Boot 3.3.6
> Camel 4.8.2
>Reporter: Jannik Schmeier
>Assignee: Nicolas Filotto
>Priority: Major
> Fix For: 4.8.4, 4.10.0
>
>
> This is a Follow-Up on this issue: CAMEL-21467
> Unfortunately we are still experiencing the same issue with threads getting
> stuck in the state RUNNABLE. It seems like the frequency of the issue has
> greatly decreased though. We have had it twice in about a month.
>
> Threaddump:
> {noformat}
> "Camel (camel-1) thread #4 - timer://my-timer" - Thread t@65
> java.lang.Thread.State: RUNNABLE
> at
> org.apache.camel.support.cache.SimpleLRUCache$OperationContext.close(SimpleLRUCache.java:309)
> at
> org.apache.camel.support.cache.SimpleLRUCache.put(SimpleLRUCache.java:104)
> at
> org.apache.camel.support.cache.SimpleSoftCache.put(SimpleSoftCache.java:114)
> at
> org.apache.camel.component.bean.BeanComponent.addBeanInfoToCache(BeanComponent.java:96)
> at org.apache.camel.component.bean.BeanInfo.(BeanInfo.java:169)
> at
> org.apache.camel.component.bean.ConstantBeanHolder.(ConstantBeanHolder.java:50)
> at
> org.apache.camel.language.bean.BeanExpression.createBeanHolder(BeanExpression.java:303)
> at
> org.apache.camel.language.bean.BeanExpression.init(BeanExpression.java:175)
> at
> org.apache.camel.language.bean.BeanLanguage.createExpression(BeanLanguage.java:148)
> at
> org.apache.camel.language.simple.SimpleExpressionBuilder$KeyedOgnlExpressionAdapter.evaluate(SimpleExpressionBuilder.java:1251)
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45)
> at
> org.apache.camel.support.builder.ExpressionBuilder$62.evaluate(ExpressionBuilder.java:2105)
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45)
> at org.apache.camel.processor.LogProcessor.process(LogProcessor.java:71)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:808)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:714)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:84)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:178)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.processTransacted(CamelInternalProcessor.java:390)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:320)
> at org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:102)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:84)
> at
> org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:32)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.processTransacted(CamelInternalProcessor.java:390)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:320)
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.jav
[jira] [Commented] (CAMEL-21539) Vector Database capabilities - Infinispan
[ https://issues.apache.org/jira/browse/CAMEL-21539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913362#comment-17913362 ] Zineb Bendhiba commented on CAMEL-21539: that sounds great ! Many thanks [~jamesnetherton] > Vector Database capabilities - Infinispan > - > > Key: CAMEL-21539 > URL: https://issues.apache.org/jira/browse/CAMEL-21539 > Project: Camel > Issue Type: New Feature >Reporter: Zineb Bendhiba >Assignee: James Netherton >Priority: Major > > Implement Vector search capabilities for Infinispan. > Also add the langchain4j Embeddings DataFormat for Infinispan + an > Integration test in the langchain4j embeddings directory > https://github.com/apache/camel/tree/main/components/camel-ai/camel-langchain4j-embeddings/src/test/java/org/apache/camel/component/langchain4j/embeddings -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21624) Issue with Kafka Appender when using multiline YAML configuration for bootstrap.servers
[
https://issues.apache.org/jira/browse/CAMEL-21624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913336#comment-17913336
]
Nadina Florea commented on CAMEL-21624:
---
Thank you for your quick response, [~davsclaus]! I agree that this should
ideally be fixed at the Kafka level.
To address this, I've created KAFKA-18543. There are also similar issues, such
as: KAFKA-18171
I hope this will be analyzed soon at the Kafka level.
> Issue with Kafka Appender when using multiline YAML configuration for
> bootstrap.servers
> ---
>
> Key: CAMEL-21624
> URL: https://issues.apache.org/jira/browse/CAMEL-21624
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
>Affects Versions: 4.9.0
>Reporter: Nadina Florea
>Priority: Minor
>
> Hello,
> I recently encountered an issue in my application that uses Apache Camel
> 4.9.0 along with the Kafka component (camel-kafka) for message processing.
> The issue arises due to the interaction between Camel’s Kafka configuration
> and Kafka Appender when *bootstrap.servers is defined using a {_}multiline
> syntax in a YAML configuration file{_}.*
> Environment:
> • Apache Camel Version: 4.9.0
> • Spring Boot Version: 3.4.1
> • Kafka Clients Version: 3.8.1
> • Java Version: 17
> Steps to Reproduce:
> 1. Define bootstrap.servers in application.yaml using multiline syntax:
> {code:java}
> camel:
> component:
> kafka:
> brokers: >-
> broker1:9092,
> broker2:9092{code}
> 2. Use the following setup in logback-spring.xml to configure Kafka Appender:
> {code:java}
>
>
>
> bootstrap.servers=${brokers}
>
> {code}
> 3. Run the application.
> Observed Behavior:
> The application fails to start with the following error:
> _*org.apache.camel.RuntimeCamelException:
> org.apache.kafka.common.config.ConfigException: Invalid url in
> bootstrap.servers: broker2:9092*_
> Expected Behavior:
> The bootstrap.servers property should be processed correctly, even if defined
> in a multiline YAML syntax, as it worked with older Kafka Clients versions
> (e.g., 3.7.x).
> After investigating, I suspect the following change in Kafka Clients 3.8.x:
> • Starting with Kafka Clients 3.8.x, stricter validation for
> _bootstrap.servers_ was introduced via KAFKA-17584. This validation now
> rejects newline characters or other formatting inconsistencies.
> • While this is expected behavior, the way Camel propagates the
> camel.component.kafka.brokers property to Kafka Appender through
> logback-spring.xml seems to preserve newline characters, which results in
> invalid configuration values.
> Additional Notes:
> • When I updated my YAML configuration to write *bootstrap.servers on a
> single line* (e.g., broker1:9092,broker2:9092), the issue was resolved.
> • _Applications that use Spring Kafka directly without Camel are not affected
> by this issue._
>
> When configuring numerous brokers in the _bootstrap.servers_ property, it is
> difficult to read and manage when placed on a single line.
>
> Is this behavior intentional or should Camel consider providing a more
> flexible way to handle multiline configs in the future?
> Thank you!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21620) camel-core - Fix onWhen to not include outputs in model
[ https://issues.apache.org/jira/browse/CAMEL-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913345#comment-17913345 ] Claus Ibsen commented on CAMEL-21620: - TODO: Make when special for choice only. TODO: Avoid when/onWhen generated as processors into the XML XSD > camel-core - Fix onWhen to not include outputs in model > --- > > Key: CAMEL-21620 > URL: https://issues.apache.org/jira/browse/CAMEL-21620 > Project: Camel > Issue Type: Task > Components: camel-core, dsl >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.10.0 > > > Only when in choice should have outputs. The onWhen used in filter, doCatch, > intercept, onCompletion should be a predicate only without outputs. However > since it reused the when from choice the model has outputs. Its a bit tricky > to fix due to the model being old and classic spring xml XSD. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-21622) camel-tracing - add route id in the tags of the span
[ https://issues.apache.org/jira/browse/CAMEL-21622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Carletti closed CAMEL-21622. -- > camel-tracing - add route id in the tags of the span > > > Key: CAMEL-21622 > URL: https://issues.apache.org/jira/browse/CAMEL-21622 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Affects Versions: 4.9.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > Fix For: 4.10.0 > > > it would be nice to have the route id in the trace span to easily associate > the span with the route implementation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21622) camel-tracing - add route id in the tags of the span
[ https://issues.apache.org/jira/browse/CAMEL-21622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Carletti resolved CAMEL-21622. Resolution: Implemented > camel-tracing - add route id in the tags of the span > > > Key: CAMEL-21622 > URL: https://issues.apache.org/jira/browse/CAMEL-21622 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Affects Versions: 4.9.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > Fix For: 4.10.0 > > > it would be nice to have the route id in the trace span to easily associate > the span with the route implementation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21614) Simple expressions execute forever. Thread is RUNNABLE for ever. Issue appears with bean expressions inside simple expressions on SimpleLRUCache
[
https://issues.apache.org/jira/browse/CAMEL-21614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913357#comment-17913357
]
Jannik Schmeier commented on CAMEL-21614:
-
Thanks, I will deploy by the end of this week and let you know next week if
anything popped up.
> Simple expressions execute forever. Thread is RUNNABLE for ever. Issue
> appears with bean expressions inside simple expressions on SimpleLRUCache
>
>
> Key: CAMEL-21614
> URL: https://issues.apache.org/jira/browse/CAMEL-21614
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.8.2
> Environment: jdk-21.0.2+13 (Eclipse Temurin)
> Spring Boot 3.3.6
> Camel 4.8.2
>Reporter: Jannik Schmeier
>Assignee: Nicolas Filotto
>Priority: Major
> Fix For: 4.8.4, 4.10.0
>
>
> This is a Follow-Up on this issue: CAMEL-21467
> Unfortunately we are still experiencing the same issue with threads getting
> stuck in the state RUNNABLE. It seems like the frequency of the issue has
> greatly decreased though. We have had it twice in about a month.
>
> Threaddump:
> {noformat}
> "Camel (camel-1) thread #4 - timer://my-timer" - Thread t@65
> java.lang.Thread.State: RUNNABLE
> at
> org.apache.camel.support.cache.SimpleLRUCache$OperationContext.close(SimpleLRUCache.java:309)
> at
> org.apache.camel.support.cache.SimpleLRUCache.put(SimpleLRUCache.java:104)
> at
> org.apache.camel.support.cache.SimpleSoftCache.put(SimpleSoftCache.java:114)
> at
> org.apache.camel.component.bean.BeanComponent.addBeanInfoToCache(BeanComponent.java:96)
> at org.apache.camel.component.bean.BeanInfo.(BeanInfo.java:169)
> at
> org.apache.camel.component.bean.ConstantBeanHolder.(ConstantBeanHolder.java:50)
> at
> org.apache.camel.language.bean.BeanExpression.createBeanHolder(BeanExpression.java:303)
> at
> org.apache.camel.language.bean.BeanExpression.init(BeanExpression.java:175)
> at
> org.apache.camel.language.bean.BeanLanguage.createExpression(BeanLanguage.java:148)
> at
> org.apache.camel.language.simple.SimpleExpressionBuilder$KeyedOgnlExpressionAdapter.evaluate(SimpleExpressionBuilder.java:1251)
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45)
> at
> org.apache.camel.support.builder.ExpressionBuilder$62.evaluate(ExpressionBuilder.java:2105)
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45)
> at org.apache.camel.processor.LogProcessor.process(LogProcessor.java:71)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:808)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:714)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:84)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:178)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.processTransacted(CamelInternalProcessor.java:390)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:320)
> at org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:102)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:84)
> at
> org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:32)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.processTransacted(CamelInternalProcessor.java:390)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:320)
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:102)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.jav
[jira] [Comment Edited] (CAMEL-21620) camel-core - Fix onWhen to not include outputs in model
[ https://issues.apache.org/jira/browse/CAMEL-21620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913345#comment-17913345 ] Claus Ibsen edited comment on CAMEL-21620 at 1/15/25 4:03 PM: -- TODO: Make when special for choice only. TODO: Avoid when/onWhen/onFallback generated as processors into the XML XSD was (Author: davsclaus): TODO: Make when special for choice only. TODO: Avoid when/onWhen generated as processors into the XML XSD > camel-core - Fix onWhen to not include outputs in model > --- > > Key: CAMEL-21620 > URL: https://issues.apache.org/jira/browse/CAMEL-21620 > Project: Camel > Issue Type: Task > Components: camel-core, dsl >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.10.0 > > > Only when in choice should have outputs. The onWhen used in filter, doCatch, > intercept, onCompletion should be a predicate only without outputs. However > since it reused the when from choice the model has outputs. Its a bit tricky > to fix due to the model being old and classic spring xml XSD. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21613) Camel-Jbang Kubernetes Plugin: allow to choose image platform options
[ https://issues.apache.org/jira/browse/CAMEL-21613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913216#comment-17913216 ] Thomas Diesler edited comment on CAMEL-21613 at 1/15/25 8:48 AM: - It should be possible to remove the platform def in pom.xml and instead use `-Djkube.container-image.platforms` It'd be interesting to know what Jib chooses when no prop is given at all. Generally, I'd prefer to use JKube config options when available instead of duplicating stuff in "our" camel config was (Author: tdiesler): It should be possible to remove the platform def in pom.xml and instead use `-Djkube.container-image.platforms` It'd be interesting to know what Jib chooses when no prop is given at all. > Camel-Jbang Kubernetes Plugin: allow to choose image platform options > - > > Key: CAMEL-21613 > URL: https://issues.apache.org/jira/browse/CAMEL-21613 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Gaelle Fournier >Assignee: Thomas Diesler >Priority: Minor > > We should be able to configure for which architecture platform(s) we cant to > build the container. > > Currently we build the container image (with docker, JIB or podman) for both > linux/amd64 and linux/arm64. That mean we need the user to be able to do > multi-platform build. > While it is available out of the box for JIB (and maybe podman), for docker > it requires some specific tools like Qemu/buildx. We need to allow the user > to override the default configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21613) Camel-Jbang Kubernetes Plugin: allow to choose image platform options
[ https://issues.apache.org/jira/browse/CAMEL-21613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913216#comment-17913216 ] Thomas Diesler commented on CAMEL-21613: It should be possible to remove the platform def in pom.xml and instead use `-Djkube.container-image.platforms` It'd be interesting to know what Jib chooses when no prop is given at all. > Camel-Jbang Kubernetes Plugin: allow to choose image platform options > - > > Key: CAMEL-21613 > URL: https://issues.apache.org/jira/browse/CAMEL-21613 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Gaelle Fournier >Assignee: Thomas Diesler >Priority: Minor > > We should be able to configure for which architecture platform(s) we cant to > build the container. > > Currently we build the container image (with docker, JIB or podman) for both > linux/amd64 and linux/arm64. That mean we need the user to be able to do > multi-platform build. > While it is available out of the box for JIB (and maybe podman), for docker > it requires some specific tools like Qemu/buildx. We need to allow the user > to override the default configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
