[jira] [Updated] (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
]
Claus Ibsen updated CAMEL-21614:
Fix Version/s: 4.8.4
4.10.0
> 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(Redeliver
[jira] [Commented] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency
[
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912789#comment-17912789
]
Claus Ibsen commented on CAMEL-21612:
-
its something in kamelet-main when using local-kamelet-dir that calls the
constructor with wrong order
> [Regression] Camel JMX debugger is no more activated with
> org.apache.camel:camel-debug dependency
> -
>
> Key: CAMEL-21612
> URL: https://issues.apache.org/jira/browse/CAMEL-21612
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> working with 4.8.2
> {noformat}
> jbang '-Dcamel.jbang.version=4.8.2'
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run
> test-with-4_8_2.camel.yaml --dev --logging-level=info
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=.
> 2025-01-13 14:54:41.775 INFO 3939143 --- [ main]
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is
> starting
> 2025-01-13 14:54:42.129 INFO 3939143 --- [ main]
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID
> 3939143. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:54:43.681 INFO 3939143 --- [ main]
> .main.download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from:
> central@https://repo1.maven.org/maven2
> 2025-01-13 14:54:43.907 INFO 3939143 --- [ main]
> org.apache.camel.main.ProfileConfigurer : The application is starting with
> profile: dev
> 2025-01-13 14:54:44.575 INFO 3939143 --- [ main]
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:54:44.576 INFO 3939143 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR
> (Enabling Camel Debugging)
> 2025-01-13 14:54:44.587 INFO 3939143 --- [ main]
> mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
> 2025-01-13 14:54:44.799 INFO 3939143 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2
> (test-with-4_8_2) is starting
> 2025-01-13 14:54:44.972 INFO 3939143 --- [ main]
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled
> (directory: .)
> 2025-01-13 14:54:45.069 INFO 3939143 --- [gerJMXConnector]
> mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening
> at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
> 2025-01-13 14:54:45.197 INFO 3939143 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:54:45.198 INFO 3939143 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:54:45.198 INFO 3939143 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2
> (test-with-4_8_2) started in 398ms (build:0ms init:0ms start:398ms)
> {noformat}
> no more working with Camel 4.9.0:
> {noformat}
> jbang '-Dcamel.jbang.version=4.9.0'
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run
> test-with-4_9_0.camel.yaml --dev --logging-level=info
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=.
> 2025-01-13 14:53:15.468 INFO 3936155 --- [ main]
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is
> starting
> 2025-01-13 14:53:15.974 INFO 3936155 --- [ main]
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID
> 3936155. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:53:16.307 INFO 3936155 --- [ main]
> org.apache.camel.main.ProfileConfigurer : The application is starting with
> profile: dev
> 2025-01-13 14:53:16.901 INFO 3936155 --- [ main]
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:53:17.114 INFO 3936155 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0
> (test-with-4_9_0) is starting
> 2025-01-13 14:53:17.402 INFO 3936155 --- [ main]
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled
> (directory: .)
> 2025-01-13 14:53:17.641 INFO 3936155 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:53:17.641 INFO 3936155 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:53:17.642 INFO 3936155 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9
[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=17912790#comment-17912790 ] Gaelle Fournier commented on CAMEL-21613: - [~tdiesler] I think it would be better (if it is possible with jkube) to have the default value of platform as the local supported value instead of adm64 + arm64. WDYT ? > 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-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=17912778#comment-17912778
]
Nicolas Filotto commented on CAMEL-21614:
-
Thx for reporting, I have an idea of what could be the root cause. I will
propose a fix asap, ideally this week.
> 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
>Priority: Major
>
> 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.Re
[jira] [Assigned] (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 reassigned CAMEL-21614:
---
Assignee: Nicolas Filotto
> 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
>
> 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:808)
> at
> org.apach
[jira] [Updated] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency
[
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-21612:
Regression: Regression
seems link is not created automatically so here is the commit related to the
fix:
https://github.com/apache/camel/commit/d1536c9a9af93f738de06b55754c6b555121f0d6
I tested with _jbang '-Dcamel.jbang.version=4.10.0-SNAPSHOT'
'-Dorg.apache.camel.debugger.suspend
=true' camel@apache/camel run test-with-4_10_0.camel.yaml --dev
--logging-level=info '--dep=org.apache.camel:camel-debug' --fresh_ and the
debugger is started
[~davsclaus] Based on the commit, I'm wondering what was broken exactly. Was it
that no dependency was added when local kamelet dir was specified?
Which features were broken? Any ideas how to provide non-regression tests for
them?
> [Regression] Camel JMX debugger is no more activated with
> org.apache.camel:camel-debug dependency
> -
>
> Key: CAMEL-21612
> URL: https://issues.apache.org/jira/browse/CAMEL-21612
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> working with 4.8.2
> {noformat}
> jbang '-Dcamel.jbang.version=4.8.2'
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run
> test-with-4_8_2.camel.yaml --dev --logging-level=info
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=.
> 2025-01-13 14:54:41.775 INFO 3939143 --- [ main]
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is
> starting
> 2025-01-13 14:54:42.129 INFO 3939143 --- [ main]
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID
> 3939143. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:54:43.681 INFO 3939143 --- [ main]
> .main.download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from:
> central@https://repo1.maven.org/maven2
> 2025-01-13 14:54:43.907 INFO 3939143 --- [ main]
> org.apache.camel.main.ProfileConfigurer : The application is starting with
> profile: dev
> 2025-01-13 14:54:44.575 INFO 3939143 --- [ main]
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:54:44.576 INFO 3939143 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR
> (Enabling Camel Debugging)
> 2025-01-13 14:54:44.587 INFO 3939143 --- [ main]
> mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
> 2025-01-13 14:54:44.799 INFO 3939143 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2
> (test-with-4_8_2) is starting
> 2025-01-13 14:54:44.972 INFO 3939143 --- [ main]
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled
> (directory: .)
> 2025-01-13 14:54:45.069 INFO 3939143 --- [gerJMXConnector]
> mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening
> at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
> 2025-01-13 14:54:45.197 INFO 3939143 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:54:45.198 INFO 3939143 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:54:45.198 INFO 3939143 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2
> (test-with-4_8_2) started in 398ms (build:0ms init:0ms start:398ms)
> {noformat}
> no more working with Camel 4.9.0:
> {noformat}
> jbang '-Dcamel.jbang.version=4.9.0'
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run
> test-with-4_9_0.camel.yaml --dev --logging-level=info
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=.
> 2025-01-13 14:53:15.468 INFO 3936155 --- [ main]
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is
> starting
> 2025-01-13 14:53:15.974 INFO 3936155 --- [ main]
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID
> 3936155. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:53:16.307 INFO 3936155 --- [ main]
> org.apache.camel.main.ProfileConfigurer : The application is starting with
> profile: dev
> 2025-01-13 14:53:16.901 INFO 3936155 --- [ main]
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:53:17.114 INFO 3936155 --- [ main]
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0
> (test-with-4_9_0) is starting
> 2025-01-13 14:53:17
[jira] [Created] (CAMEL-21618) Review documentation for the next LTS release
Otavio Rodolfo Piske created CAMEL-21618: Summary: Review documentation for the next LTS release Key: CAMEL-21618 URL: https://issues.apache.org/jira/browse/CAMEL-21618 Project: Camel Issue Type: Task Components: documentation Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Fix For: 4.10.0 Usual ticket for documentation review. Please add any documentation to be reviewed in the comments. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21618) Review documentation for the next LTS release
[ https://issues.apache.org/jira/browse/CAMEL-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912803#comment-17912803 ] Federico Mariani commented on CAMEL-21618: -- test infra documentation needs to be reviewed after the JUnit decouple, I already updated the latest section https://github.com/apache/camel/blob/44394bee5a08763c63e369ba96dc962d607c2366/docs/user-manual/modules/ROOT/pages/test-infra.adoc but there may be something else to be updated > Review documentation for the next LTS release > - > > Key: CAMEL-21618 > URL: https://issues.apache.org/jira/browse/CAMEL-21618 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.10.0 > > > Usual ticket for documentation review. Please add any documentation to be > reviewed in the comments. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21618) Review documentation for the next LTS release
[ https://issues.apache.org/jira/browse/CAMEL-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912804#comment-17912804 ] Otavio Rodolfo Piske commented on CAMEL-21618: -- Likely to have changed docs: * Camel Jbang * AI components > Review documentation for the next LTS release > - > > Key: CAMEL-21618 > URL: https://issues.apache.org/jira/browse/CAMEL-21618 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.10.0 > > > Usual ticket for documentation review. Please add any documentation to be > reviewed in the comments. -- 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=17912837#comment-17912837
]
Thomas Diesler edited comment on CAMEL-21613 at 1/14/25 11:30 AM:
--
To remind myself ... we default to build strategy Jib and have this in the
templates ...
{code}
linux/amd64
linux/arm64
{code}
See 'jkube.container-image.platforms' in
https://eclipse.dev/jkube/docs/kubernetes-maven-plugin/#build-configuration.
Our general focus should be on easy entry for Camel to K8s i.e. local k8s
first, then your favourite free distro e.g. k3s, then OpenShift. All stuff must
work on OpenShift.
I use DockerDesktop Kubernetes, which allows me to build for both amd64, arm64.
On a remote server, I have not yet seen an arm64 node.
So, yes. Defaulting to the local platform should be fine because it is
guaranteed to work on "local k8s". Building for an alternative platform should
be easy too.
How would you like to configure that? The container trait perhaps?
was (Author: tdiesler):
To remind myself ... we default to build strategy Jib and have this in the
templates ...
{code}
linux/amd64
linux/arm64
{code}
See 'jkube.container-image.platforms' in
https://eclipse.dev/jkube/docs/kubernetes-maven-plugin/#build-configuration.
Our general focus should be on easy entry for Camel to K8s i.e. local k8s
first, then your favourite free distro e.g. k3s, then OpenShift. All stuff must
work on OpenShift.
I use DockerDesktop Kubernetes and, which allows me to build for both amd64,
arm64. On a remote server, I have not yet seen an arm64 node.
So, yes. Defaulting to the local platform should be fine because it is
guaranteed to work on "local k8s". Building for an alternative platform should
be easy too.
How would you like to configure that? The container trait perhaps?
> 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=17912837#comment-17912837
]
Thomas Diesler commented on CAMEL-21613:
To remind myself ... we default to build strategy Jib and have this in the
templates ...
{code}
linux/amd64
linux/arm64
{code}
See 'jkube.container-image.platforms' in
https://eclipse.dev/jkube/docs/kubernetes-maven-plugin/#build-configuration.
Our general focus should be on easy entry for Camel to K8s i.e. local k8s
first, then your favourite free distro e.g. k3s, then OpenShift - all stuff
must work on OpenShift.
I use DockerDesktop Kubernetes and, which allows me to build for both amd64,
arm64. On a remote server, I have not yet seen an arm64 node.
So, yes. Defaulting to the local platform should be fine because it is
guaranteed to work on "local k8s". Building for an alternative platform should
be easy too.
How would you like to configure that? The container trait perhaps?
> 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] [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=17912837#comment-17912837
]
Thomas Diesler edited comment on CAMEL-21613 at 1/14/25 11:30 AM:
--
To remind myself ... we default to build strategy Jib and have this in the
templates ...
{code}
linux/amd64
linux/arm64
{code}
See 'jkube.container-image.platforms' in
https://eclipse.dev/jkube/docs/kubernetes-maven-plugin/#build-configuration.
Our general focus should be on easy entry for Camel to K8s i.e. local k8s
first, then your favourite free distro e.g. k3s, then OpenShift. All stuff must
work on OpenShift.
I use DockerDesktop Kubernetes and, which allows me to build for both amd64,
arm64. On a remote server, I have not yet seen an arm64 node.
So, yes. Defaulting to the local platform should be fine because it is
guaranteed to work on "local k8s". Building for an alternative platform should
be easy too.
How would you like to configure that? The container trait perhaps?
was (Author: tdiesler):
To remind myself ... we default to build strategy Jib and have this in the
templates ...
{code}
linux/amd64
linux/arm64
{code}
See 'jkube.container-image.platforms' in
https://eclipse.dev/jkube/docs/kubernetes-maven-plugin/#build-configuration.
Our general focus should be on easy entry for Camel to K8s i.e. local k8s
first, then your favourite free distro e.g. k3s, then OpenShift - all stuff
must work on OpenShift.
I use DockerDesktop Kubernetes and, which allows me to build for both amd64,
arm64. On a remote server, I have not yet seen an arm64 node.
So, yes. Defaulting to the local platform should be fine because it is
guaranteed to work on "local k8s". Building for an alternative platform should
be easy too.
How would you like to configure that? The container trait perhaps?
> 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] [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=17912837#comment-17912837
]
Thomas Diesler edited comment on CAMEL-21613 at 1/14/25 11:31 AM:
--
To remind myself ... we default to build strategy Jib and have this in the
templates ...
{code}
linux/amd64
linux/arm64
{code}
See 'jkube.container-image.platforms' in
https://eclipse.dev/jkube/docs/kubernetes-maven-plugin/#build-configuration.
Our general focus should be on easy entry for Camel to K8s i.e. local k8s
first, then your favourite free distro e.g. k3s, then OpenShift. All stuff must
work on OpenShift.
I use DockerDesktop Kubernetes, which allows me to build for both amd64 and
arm64. On a remote server, I have not yet seen an arm64 node.
So, yes. Defaulting to the local platform should be fine because it is
guaranteed to work on "local k8s". Building for an alternative platform should
be easy too.
How would you like to configure that? The container trait perhaps?
was (Author: tdiesler):
To remind myself ... we default to build strategy Jib and have this in the
templates ...
{code}
linux/amd64
linux/arm64
{code}
See 'jkube.container-image.platforms' in
https://eclipse.dev/jkube/docs/kubernetes-maven-plugin/#build-configuration.
Our general focus should be on easy entry for Camel to K8s i.e. local k8s
first, then your favourite free distro e.g. k3s, then OpenShift. All stuff must
work on OpenShift.
I use DockerDesktop Kubernetes, which allows me to build for both amd64, arm64.
On a remote server, I have not yet seen an arm64 node.
So, yes. Defaulting to the local platform should be fine because it is
guaranteed to work on "local k8s". Building for an alternative platform should
be easy too.
How would you like to configure that? The container trait perhaps?
> 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] [Assigned] (CAMEL-21539) Vector Database capabilities - Infinispan
[ https://issues.apache.org/jira/browse/CAMEL-21539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton reassigned CAMEL-21539: --- Assignee: James Netherton > 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-21618) Review documentation for the next LTS release
[ https://issues.apache.org/jira/browse/CAMEL-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912809#comment-17912809 ] Claus Ibsen commented on CAMEL-21618: - New components since last LTS > Review documentation for the next LTS release > - > > Key: CAMEL-21618 > URL: https://issues.apache.org/jira/browse/CAMEL-21618 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.10.0 > > > Usual ticket for documentation review. Please add any documentation to be > reviewed in the comments. -- 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=17912827#comment-17912827 ] Claus Ibsen commented on CAMEL-21620: - We can also consider making "when" with inlined outputs part of choice and then its not listed in general outputs for all the EIPs > 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-21621) Regression with k8s-run shutdown
Thomas Diesler created CAMEL-21621:
--
Summary: Regression with k8s-run shutdown
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
{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 - regression with k8s-run shutdown
[
https://issues.apache.org/jira/browse/CAMEL-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-21621:
---
Summary: camel-jbang - regression with k8s-run shutdown (was: Regression
with k8s-run shutdown)
> camel-jbang - regression with k8s-run shutdown
> --
>
> 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
>
> {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] [Comment Edited] (CAMEL-21618) Review documentation for the next LTS release
[ https://issues.apache.org/jira/browse/CAMEL-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912809#comment-17912809 ] Claus Ibsen edited comment on CAMEL-21618 at 1/14/25 9:43 AM: -- New components since last LTS clickup Preview 4.9 Receives events from ClickUp flowable Preview 4.9 Send and receive messages from the Flowable BPMN and CMMN engines. fury Preview 4.9 Serialize and deserialize messages using Apache Fury smooks Preview 4.9 Transform and bind XML as well as non-XML data, including EDI, CSV, JSON, and YAML using Smooks. observability-services Preview 4.9 Camel Observability Services was (Author: davsclaus): New components since last LTS > Review documentation for the next LTS release > - > > Key: CAMEL-21618 > URL: https://issues.apache.org/jira/browse/CAMEL-21618 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.10.0 > > > Usual ticket for documentation review. Please add any documentation to be > reviewed in the comments. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21619) kamelets - Adapt to SB or Q runtime
Claus Ibsen created CAMEL-21619: --- Summary: kamelets - Adapt to SB or Q runtime Key: CAMEL-21619 URL: https://issues.apache.org/jira/browse/CAMEL-21619 Project: Camel Issue Type: Improvement Components: camel-kamelet Reporter: Claus Ibsen Fix For: 4.x When using some kamelets such as database or messaging systems, then the runtime like SB or Q comes with their standard connection pooling. It may be desirable to have a way for a kamelet to adapt and use this from the same kamelet, so we do not have runtime specific kamelets. Also consider camel-main runtime should have a way for connection pooling. This is mostly applicable to only JMS / Artemis / SQL kamelets. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21620) camel-core - Fix onWhen to not include outputs in model
Claus Ibsen created CAMEL-21620: --- Summary: 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 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=17912935#comment-17912935
]
Thomas Diesler commented on CAMEL-21621:
PR: https://github.com/apache/camel/pull/16806
This now constructs a new k8s client with a vertx instance that doesn't have a
shutdown hook
> 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
>
> {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
]
Thomas Diesler updated CAMEL-21621:
---
Summary: camel-jbang - k8s-httpclient-vertx fails in shutdown hook (was:
camel-jbang - cannot use k8s-httpclient-vertx in shutdown hook)
> 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
>
> {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-21623) Expose test-infra services via Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-21623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Mariani updated CAMEL-21623: - Priority: Minor (was: Major) > Expose test-infra services via Camel JBang > -- > > Key: CAMEL-21623 > URL: https://issues.apache.org/jira/browse/CAMEL-21623 > Project: Camel > Issue Type: New Feature >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Minor > > Create a new Camel JBang command that exposes test-infra Services. > The command are the following > * list > ** List all the available services that can be run via Camel JBang > * run $SERVICE > ** Run the service and print the configuration properties to stdout -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21623) Expose test-infra services via Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-21623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Mariani updated CAMEL-21623: - Component/s: camel-jbang test-infra > Expose test-infra services via Camel JBang > -- > > Key: CAMEL-21623 > URL: https://issues.apache.org/jira/browse/CAMEL-21623 > Project: Camel > Issue Type: New Feature > Components: camel-jbang, test-infra >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Minor > > Create a new Camel JBang command that exposes test-infra Services. > The command are the following > * list > ** List all the available services that can be run via Camel JBang > * run $SERVICE > ** Run the service and print the configuration properties to stdout -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21623) Expose test-infra services via Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-21623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Mariani updated CAMEL-21623: - Fix Version/s: 4.10.0 > Expose test-infra services via Camel JBang > -- > > Key: CAMEL-21623 > URL: https://issues.apache.org/jira/browse/CAMEL-21623 > Project: Camel > Issue Type: New Feature > Components: camel-jbang, test-infra >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Minor > Fix For: 4.10.0 > > > Create a new Camel JBang command that exposes test-infra Services. > The command are the following > * list > ** List all the available services that can be run via Camel JBang > * run $SERVICE > ** Run the service and print the configuration properties to stdout -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21623) Expose test-infra services via Camel JBang
Federico Mariani created CAMEL-21623: Summary: Expose test-infra services via Camel JBang Key: CAMEL-21623 URL: https://issues.apache.org/jira/browse/CAMEL-21623 Project: Camel Issue Type: New Feature Reporter: Federico Mariani Create a new Camel JBang command that exposes test-infra Services. The command are the following * list ** List all the available services that can be run via Camel JBang * run $SERVICE ** Run the service and print the configuration properties to stdout -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21623) Expose test-infra services via Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-21623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Mariani reassigned CAMEL-21623: Assignee: Federico Mariani > Expose test-infra services via Camel JBang > -- > > Key: CAMEL-21623 > URL: https://issues.apache.org/jira/browse/CAMEL-21623 > Project: Camel > Issue Type: New Feature >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Major > > Create a new Camel JBang command that exposes test-infra Services. > The command are the following > * list > ** List all the available services that can be run via Camel JBang > * run $SERVICE > ** Run the service and print the configuration properties to stdout -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21621) camel-jbang - cannot use k8sclient-vertx in shutdown hook
[
https://issues.apache.org/jira/browse/CAMEL-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-21621:
---
Summary: camel-jbang - cannot use k8sclient-vertx in shutdown hook (was:
camel-jbang - regression with k8s-run shutdown)
> camel-jbang - cannot use k8sclient-vertx 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
>
> {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 - cannot use k8s-httpclient-vertx in shutdown hook
[
https://issues.apache.org/jira/browse/CAMEL-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-21621:
---
Summary: camel-jbang - cannot use k8s-httpclient-vertx in shutdown hook
(was: camel-jbang - cannot use k8sclient-vertx in shutdown hook)
> camel-jbang - cannot use k8s-httpclient-vertx 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
>
> {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-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=17912895#comment-17912895 ] Gaelle Fournier commented on CAMEL-21613: - I saw this jib configuration as well. I am not sure it is only used by jib: when deploying with docker build strategy I had to make my infra multi-platform compatible (in my case using qemu) or else I ended up with this issue https://issues.apache.org/jira/browse/CAMEL-21464. My idea would be: local platform as default, if anyone want to change we can override by a trait or command parameter. This should configuration should multi-valued and any call to it should completly override the default behavior. That mean if the local platform default is amd64 and we configure by trait/command parameter arm64, we should only build for arm64. In CK we used it in the builder trait ([https://camel.apache.org/camel-k/2.5.x/traits/builder.html)] but since most of the image configuration is done with some parameter `--image-` it might be better to use `--image-platform` > 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] [Created] (CAMEL-21622) camel-tracing - add route id in the tags of the span
Marco Carletti created CAMEL-21622: -- Summary: 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 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-21509) camel-kubernetes - Upgrade to v7 of fabric8-client
[ https://issues.apache.org/jira/browse/CAMEL-21509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912917#comment-17912917 ] Thomas Diesler commented on CAMEL-21509: This seem to break `camel jbang kubernetes run` - see CAMEL-21621 > camel-kubernetes - Upgrade to v7 of fabric8-client > -- > > Key: CAMEL-21509 > URL: https://issues.apache.org/jira/browse/CAMEL-21509 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kubernetes >Reporter: Claus Ibsen >Assignee: James Netherton >Priority: Major > Fix For: 4.10.0 > > > [https://blog.marcnuri.com/fabric8-kubernetes-client-7-0] > > The CEQ project may need to upgrade as well to make this work on Quarkus. > A -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21621) camel-jbang - regression with k8s-run shutdown
[
https://issues.apache.org/jira/browse/CAMEL-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912916#comment-17912916
]
Thomas Diesler commented on CAMEL-21621:
Recreating the k8s client in the k8s-run shutdown hook does not work either
{code}
Exception in thread "Camel Thread #7 - CamelShutdownInterceptor"
java.util.ServiceConfigurationError:
io.fabric8.kubernetes.client.http.HttpClient$Factory: Provider
io.fabric8.kubernetes.client.vertx.VertxHttpClientFactory could not be
instantiated
at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:586)
at
java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:813)
at
java.base/java.util.ServiceLoader$ProviderImpl.get(ServiceLoader.java:729)
at java.base/java.util.ServiceLoader$3.next(ServiceLoader.java:1403)
at java.base/java.lang.Iterable.forEach(Iterable.java:74)
at
io.fabric8.kubernetes.client.utils.HttpClientUtils.getFactory(HttpClientUtils.java:179)
at
io.fabric8.kubernetes.client.utils.HttpClientUtils.getHttpClientFactory(HttpClientUtils.java:167)
at
io.fabric8.kubernetes.client.KubernetesClientBuilder.build(KubernetesClientBuilder.java:76)
at
org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesHelper.getKubernetesClient(KubernetesHelper.java:78)
at
org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesBaseCommand.client(KubernetesBaseCommand.java:137)
at
org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesDelete.doCall(KubernetesDelete.java:91)
at
org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesRun.lambda$installShutdownHook$10(KubernetesRun.java:511)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.IllegalStateException: Shutdown in progress
at
java.base/java.lang.ApplicationShutdownHooks.add(ApplicationShutdownHooks.java:66)
at java.base/java.lang.Runtime.addShutdownHook(Runtime.java:216)
at
io.fabric8.kubernetes.client.vertx.VertxHttpClientFactory.(VertxHttpClientFactory.java:60)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
at
java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:789)
... 11 more
{code}
This code effectively prevents the use of k8s in any shutdown hook
{code}
public VertxHttpClientFactory() {
this(VertxHttpClientFactory.VertxHolder.INSTANCE);
Runtime.getRuntime().addShutdownHook(new Thread(() -> {
if (this.vertx != null) {
this.vertx.close();
}
}));
}
{code}
In Java, shutdown hook are executed in a non-deterministic order from separate
threads.
Any idea on how to fix (or work around) this are very welcome ;-)
> camel-jbang - regression with k8s-run shutdown
> --
>
> 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
>
> {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] [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=17912895#comment-17912895 ] Gaelle Fournier edited comment on CAMEL-21613 at 1/14/25 6:14 PM: -- I saw this jib configuration as well. I am not sure it is only used by jib: when deploying with docker build strategy I had to make my infra multi-platform compatible (in my case using qemu) or else I ended up with this issue https://issues.apache.org/jira/browse/CAMEL-21464. My idea would be: local platform as default, if anyone want to change we can override by a trait or command parameter. This should configuration should multi-valued and any call to it should completly override the default behavior. That mean if the local platform default is amd64 and we configure by trait/command parameter arm64, we should only build for arm64. In CK we used it in the builder trait ([https://camel.apache.org/camel-k/2.5.x/traits/builder.html)] but since most of the image configuration is done with some parameter `--image-` it might be better to use `--image-platform` was (Author: JIRAUSER304516): I saw this jib configuration as well. I am not sure it is only used by jib: when deploying with docker build strategy I had to make my infra multi-platform compatible (in my case using qemu) or else I ended up with this issue https://issues.apache.org/jira/browse/CAMEL-21464. My idea would be: local platform as default, if anyone want to change we can override by a trait or command parameter. This should configuration should multi-valued and any call to it should completly override the default behavior. That mean if the local platform default is amd64 and we configure by trait/command parameter arm64, we should only build for arm64. In CK we used it in the builder trait ([https://camel.apache.org/camel-k/2.5.x/traits/builder.html)] but since most of the image configuration is done with some parameter `--image-` it might be better to use `-image-platform` > 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] [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=17912895#comment-17912895 ] Gaelle Fournier edited comment on CAMEL-21613 at 1/14/25 6:13 PM: -- I saw this jib configuration as well. I am not sure it is only used by jib: when deploying with docker build strategy I had to make my infra multi-platform compatible (in my case using qemu) or else I ended up with this issue https://issues.apache.org/jira/browse/CAMEL-21464. My idea would be: local platform as default, if anyone want to change we can override by a trait or command parameter. This should configuration should multi-valued and any call to it should completly override the default behavior. That mean if the local platform default is amd64 and we configure by trait/command parameter arm64, we should only build for arm64. In CK we used it in the builder trait ([https://camel.apache.org/camel-k/2.5.x/traits/builder.html)] but since most of the image configuration is done with some parameter `--image-` it might be better to use `-image-platform` was (Author: JIRAUSER304516): I saw this jib configuration as well. I am not sure it is only used by jib: when deploying with docker build strategy I had to make my infra multi-platform compatible (in my case using qemu) or else I ended up with this issue https://issues.apache.org/jira/browse/CAMEL-21464. My idea would be: local platform as default, if anyone want to change we can override by a trait or command parameter. This should configuration should multi-valued and any call to it should completly override the default behavior. That mean if the local platform default is amd64 and we configure by trait/command parameter arm64, we should only build for arm64. In CK we used it in the builder trait ([https://camel.apache.org/camel-k/2.5.x/traits/builder.html)] but since most of the image configuration is done with some parameter `--image-` it might be better to use `--image-platform` > 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] [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=17912895#comment-17912895 ] Gaelle Fournier edited comment on CAMEL-21613 at 1/14/25 6:15 PM: -- I saw this jib configuration as well. I am not sure it is only used by jib: when deploying with docker build strategy I had to make my infra multi-platform compatible (in my case using qemu) or else I ended up with this issue https://issues.apache.org/jira/browse/CAMEL-21464. My idea would be: local platform as default, if anyone want to change we can override by a trait or command parameter. This should configuration should multi-valued and any call to it should completly override the default behavior. That mean if the local platform default is amd64 and we configure by trait/command parameter arm64, we should only build for arm64. In CK we used it in the builder trait ([https://camel.apache.org/camel-k/2.5.x/traits/builder.html)] but since most of the image configuration is done with some parameter --image- it might be better to use --image-platform was (Author: JIRAUSER304516): I saw this jib configuration as well. I am not sure it is only used by jib: when deploying with docker build strategy I had to make my infra multi-platform compatible (in my case using qemu) or else I ended up with this issue https://issues.apache.org/jira/browse/CAMEL-21464. My idea would be: local platform as default, if anyone want to change we can override by a trait or command parameter. This should configuration should multi-valued and any call to it should completly override the default behavior. That mean if the local platform default is amd64 and we configure by trait/command parameter arm64, we should only build for arm64. In CK we used it in the builder trait ([https://camel.apache.org/camel-k/2.5.x/traits/builder.html)] but since most of the image configuration is done with some parameter `--image-` it might be better to use `--image-platform` > 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] [Work started] (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 ] Work on CAMEL-21622 started by Marco Carletti. -- > 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)
