[jira] [Resolved] (CAMEL-21402) Enhance Camel's testing capabilities of MockEndpoint with Expressions
[ https://issues.apache.org/jira/browse/CAMEL-21402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21402. - Resolution: Fixed See PR https://github.com/apache/camel/pull/16280 > Enhance Camel's testing capabilities of MockEndpoint with Expressions > - > > Key: CAMEL-21402 > URL: https://issues.apache.org/jira/browse/CAMEL-21402 > Project: Camel > Issue Type: Improvement > Components: camel-mock >Reporter: Dmitrii Kriukov >Assignee: Dmitrii Kriukov >Priority: Minor > Fix For: 4.9.0 > > > My test case was: partially random value in an added header. It's difficult > to test the exact value with existing API, so I was thinking about verifying > against a regex. This option requires usage of Expressions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21455) camel-beanio - Upgrade to 3.2.0
[ https://issues.apache.org/jira/browse/CAMEL-21455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21455. - Resolution: Fixed > camel-beanio - Upgrade to 3.2.0 > --- > > Key: CAMEL-21455 > URL: https://issues.apache.org/jira/browse/CAMEL-21455 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-beanio >Affects Versions: 4.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.8.2, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21455) camel-beanio - Upgrade to 3.2.0
Claus Ibsen created CAMEL-21455: --- Summary: camel-beanio - Upgrade to 3.2.0 Key: CAMEL-21455 URL: https://issues.apache.org/jira/browse/CAMEL-21455 Project: Camel Issue Type: Dependency upgrade Components: camel-beanio Affects Versions: 4.8.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.8.2, 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21442) camel-jbang - export is no more working when a previous run with an xsl file on the classpath occured
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-21442:
Attachment: example-test-with-xsl-before-export.zip
> camel-jbang - export is no more working when a previous run with an xsl file
> on the classpath occured
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
> 'test-with-xsl.camel.yaml'
> * create an empty dummy.xsl file
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> *.xsl
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
> successfully and then calling mvn quarkus:dev is working fine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21442) camel-jbang - export is no more working when a previous run with an xsl file on the classpath occured
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898163#comment-17898163
]
Aurélien Pupier edited comment on CAMEL-21442 at 11/14/24 7:50 AM:
---
About kamelet-dir, hitting same kind of problem that the project structure
needs to be reinvented. Usually users are creating kamelet at the same level
than Camel routes. Also the Camel Jbang init is not giving any guidance and by
default creating at the same level. So providing --kamelet-dir to current dir
is the way to have it working by default.
using `jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
*.xsl` is giving the same result. The *.xsl is used to select additional files
to add the classpath, not to select files to run.
Added the project after the 3 steps [^example-test-with-xsl-before-export.zip]
:
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
'test-with-xsl.camel.yaml'
* create an empty dummy.xsl file
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=. *.xsl
was (Author: apupier):
About kamelet-dir, hitting same kind of problem that the project structure
needs to be reinvented. Usually users are creating kamelet at the same level
than Camel routes. Also the Camel Jbang init is not giving any guidance and by
default creating at the same level. So providing --kamelet-dir to current dir
is the way to have it working by default.
using `jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
*.xsl` is giving the same result. The *.xsl is used to select additional files
to add the classpath, not to select files to run.
Added the project after the 3 steps:
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
'test-with-xsl.camel.yaml'
* create an empty dummy.xsl file
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=. *.xsl
> camel-jbang - export is no more working when a previous run with an xsl file
> on the classpath occured
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
> 'test-with-xsl.camel.yaml'
> * create an empty dummy.xsl file
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> *.xsl
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.comm
[jira] [Comment Edited] (CAMEL-21442) camel-jbang - export is no more working when a previous run occured with local-kamelet-dir set to current dir
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898212#comment-17898212
]
Aurélien Pupier edited comment on CAMEL-21442 at 11/14/24 9:57 AM:
---
note that `jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
--runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT --local-kamelet-dir=.`
is working when there wasn't a run done, so when there is no
.camel-jbang/camel-jbang-run.properties
EDIT: in fact it seems that the parameter is ignored and it is workign by the
side effect that the kamelet is at same level than the Camel route file
was (Author: apupier):
note that `jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
--runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT --local-kamelet-dir=.`
is working when there wasn't a run done, so when there is no
.camel-jbang/camel-jbang-run.properties
> camel-jbang - export is no more working when a previous run occured with
> local-kamelet-dir set to current dir
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Assignee: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init 'test.yaml'
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
> successfully and then calling mvn quarkus:dev is working fine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21442) camel-jbang - export is no more working when a previous run occured with local-kamelet-dir set to current dir
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898212#comment-17898212
]
Aurélien Pupier commented on CAMEL-21442:
-
note that `jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
--runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT --local-kamelet-dir=.`
is working when there wasn't a run done, so when there is no
.camel-jbang/camel-jbang-run.properties
> camel-jbang - export is no more working when a previous run occured with
> local-kamelet-dir set to current dir
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Assignee: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init 'test.yaml'
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
> successfully and then calling mvn quarkus:dev is working fine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21384) [camel-micrometer] Analyse the possibility to harmonize the metrics endpoint
[
https://issues.apache.org/jira/browse/CAMEL-21384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pasquale Congiusti updated CAMEL-21384:
---
Fix Version/s: 4.10.0
> [camel-micrometer] Analyse the possibility to harmonize the metrics endpoint
>
>
> Key: CAMEL-21384
> URL: https://issues.apache.org/jira/browse/CAMEL-21384
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 4.x
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Minor
> Fix For: 4.10.0
>
>
> I've been testing the Camel-micrometer component with the different runtimes
> we have. So far, each of the runtime requires a different set of
> configuration and it exposes the metrics in a different endpoint:
> {code}
> Camel MAIN
> (application.properties)
> camel.server.enabled=true
> camel.server.metricsEnabled=true
> camel.metrics.enabled=true
> $ camel run test.yaml application.properties
> URL --> http://localhost:8080/q/metrics
> Camel QUARKUS
> Blank application.properties
> $ camel run test.yaml --runtime quarkus --dep
> mvn:io.quarkus:quarkus-micrometer-registry-prometheus --dep camel-micrometer
> URL --> http://localhost:8080/q/metrics
> Camel SPRINGBOOT
> (application.properties)
> management.endpoints.web.exposure.include=prometheus
> $ camel run test.yaml application.properties --runtime spring-boot --dep
> mvn:io.micrometer:micrometer-registry-prometheus --dep camel-micrometer
> URL --> http://localhost:8080/actuator/prometheus
> {code}
> We should understand if it is feasible to harmonize somehow the configuration
> to be able to spit the metrics to the same endpoint OOTB.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work started] (CAMEL-21384) [camel-micrometer] Analyse the possibility to harmonize the metrics endpoint
[
https://issues.apache.org/jira/browse/CAMEL-21384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-21384 started by Pasquale Congiusti.
--
> [camel-micrometer] Analyse the possibility to harmonize the metrics endpoint
>
>
> Key: CAMEL-21384
> URL: https://issues.apache.org/jira/browse/CAMEL-21384
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 4.x
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Minor
>
> I've been testing the Camel-micrometer component with the different runtimes
> we have. So far, each of the runtime requires a different set of
> configuration and it exposes the metrics in a different endpoint:
> {code}
> Camel MAIN
> (application.properties)
> camel.server.enabled=true
> camel.server.metricsEnabled=true
> camel.metrics.enabled=true
> $ camel run test.yaml application.properties
> URL --> http://localhost:8080/q/metrics
> Camel QUARKUS
> Blank application.properties
> $ camel run test.yaml --runtime quarkus --dep
> mvn:io.quarkus:quarkus-micrometer-registry-prometheus --dep camel-micrometer
> URL --> http://localhost:8080/q/metrics
> Camel SPRINGBOOT
> (application.properties)
> management.endpoints.web.exposure.include=prometheus
> $ camel run test.yaml application.properties --runtime spring-boot --dep
> mvn:io.micrometer:micrometer-registry-prometheus --dep camel-micrometer
> URL --> http://localhost:8080/actuator/prometheus
> {code}
> We should understand if it is feasible to harmonize somehow the configuration
> to be able to spit the metrics to the same endpoint OOTB.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21432) multicast function executes for ever. Thread is RUNNABLE for ever. Issue appears with multicast operating on SimpleLRUCache
[
https://issues.apache.org/jira/browse/CAMEL-21432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Filotto resolved CAMEL-21432.
-
Resolution: Fixed
> multicast function executes for ever. Thread is RUNNABLE for ever. Issue
> appears with multicast operating on SimpleLRUCache
> -
>
> Key: CAMEL-21432
> URL: https://issues.apache.org/jira/browse/CAMEL-21432
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.4.3
> Environment: |
> ||Virtual Machine: |OpenJDK 64-Bit Server VM version 17.0.13+11-LTS|
> ||Vendor: |Red Hat, Inc.|
> |
>
> Processing Application Thread: IBM MQ Consumer.
> Camel Version: 4.4.3
>Reporter: Abhi Ashok
>Assignee: Nicolas Filotto
>Priority: Minor
> Fix For: 4.4.5, 4.8.2, 4.9.0
>
> Attachments: image-2024-11-11-14-31-06-831.png
>
>
> multicast function used in a Camel Route never returns back occasionally.
> Route Code snippet:
> from(getProcessMessageURI())
> .routeId(getSourceId() + ".businessRoute")
> .autoStartup(this.getConfigValue(getRouteAutoStartup()))
> .transacted(this.getPropagationRequiredPolicy())
> .setHeader("DESTINATION_URI").simple(this.getConfigValue(getOutputQueue()))
> .process(new InputMessageProcessor(this.getConfigValue(getOutputQueue(
> .bean(new JTEConfigReader(getConfigXml()), "addJTEConfig(${body})")
> .bean(DMUtilityProcessor.class) exchange
> .bean(TranslatorExchangeController.class)
> .removeHeaders("JMS*")
> *.multicast()*
> .to(directOutput(), directPersist());
>
> *Thread dump shows that the Processing Thread remains in RUNNABLE state.*
> *All Stuck instance of Threaddump shows access to
> SimpleLRUCache$OperationContext.close, where it gets stuck.*
>
> Thread Dump:
> Name: Camel (camelContext) thread #11 -
> JmsConsumer[IFM.RTR.IFM.ITE.BFM.AKNKRAW.EXPRESS]
> State: *RUNNABLE*
> Total blocked: 13,338 Total waited: 13,968
> Stack trace:
> org.apache.camel.support.cache{*}.SimpleLRUCache{*}$OperationContext.close(SimpleLRUCache.java:318)
> org.apache.camel.support.cache.SimpleLRUCache.putIfAbsent(SimpleLRUCache.java:125)
> org.apache.camel.processor.MulticastProcessor.wrapInErrorHandler(MulticastProcessor.java:1074)
> org.apache.camel.processor.MulticastProcessor.createProcessorExchangePair(MulticastProcessor.java:1023)
> org.apache.camel.processor.{*}MulticastProcessor{*}.createProcessorExchangePairs(MulticastProcessor.java:990)
> org.apache.camel.processor.MulticastProcessor.doProcess(MulticastProcessor.java:324)
> org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:316)
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:840)
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:746)
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
> org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:84)
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:200)
> org.apache.camel.impl.engine.CamelInternalProcessor.processTransacted(CamelInternalProcessor.java:397)
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:327)
> org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:102)
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
> org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:84)
> org.apache.camel.spring.spi.TransactionErrorHandler.processByErrorHandler(TransactionErrorHandler.java:244)
> org.apache.camel.spring.spi.TransactionErrorHandler.process(TransactionErrorHandler.java:119)
> org.apache.camel.spring.spi.TransactionErrorHandler.process(TransactionErrorHandler.java:132)
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:840)
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:746)
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFrom
[jira] [Commented] (CAMEL-21442) camel-jbang - export is no more working when a previous run with an xsl file on the classpath occured
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898202#comment-17898202
]
Aurélien Pupier commented on CAMEL-21442:
-
now im reproducing without the xsl so I will simplify the steps and update the
title. It is related only to the kamelet-dir parameter
> camel-jbang - export is no more working when a previous run with an xsl file
> on the classpath occured
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
> 'test-with-xsl.camel.yaml'
> * create an empty dummy.xsl file
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> *.xsl
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
> successfully and then calling mvn quarkus:dev is working fine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21442) camel-jbang - export is no more working when a previous run with an xsl file on the classpath occured
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898200#comment-17898200
]
Aurélien Pupier commented on CAMEL-21442:
-
when using a name for the Camel route file without 'xsl' in it, the error
stacktrace is slightly different (or a coincidence and just picking one or the
other?):
{noformat}
java.nio.file.NoSuchFileException:
.camel-jbang/work/src/main/resources/kamelets/my.xsl
at
java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
at
java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
at java.base/java.nio.file.Files.copy(Files.java:1304)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
at
org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
at
org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
at
org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
at
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
at
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
at picocli.CommandLine.access$1500(CommandLine.java:148)
at
picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
at
picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
at picocli.CommandLine.execute(CommandLine.java:2174)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
at main.CamelJBang.main(CamelJBang.java:36)
{noformat}
> camel-jbang - export is no more working when a previous run with an xsl file
> on the classpath occured
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
> 'test-with-xsl.camel.yaml'
> * create an empty dummy.xsl file
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> *.xsl
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.cam
[jira] [Updated] (CAMEL-21442) camel-jbang - export is no more working when a previous run occured with local-kamelet-dir set to current dir
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-21442:
Summary: camel-jbang - export is no more working when a previous run
occured with local-kamelet-dir set to current dir (was: camel-jbang - export
is no more working when a previous run with an xsl file on the classpath
occured)
> camel-jbang - export is no more working when a previous run occured with
> local-kamelet-dir set to current dir
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
> 'test-with-xsl.camel.yaml'
> * create an empty dummy.xsl file
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> *.xsl
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
> successfully and then calling mvn quarkus:dev is working fine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21442) camel-jbang - export is no more working when a previous run occured with local-kamelet-dir set to current dir
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-21442:
Description:
it is a regression introduced in Camel 4.8.1, it is working fine with Camel
4.8.0
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init 'test.yaml'
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
--runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
{noformat}
Reusing existing run data
Exporting as Quarkus project to: .
java.nio.file.NoSuchFileException:
.camel-jbang/work/src/main/resources/kamelets/test.camel.yaml
at
java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
at
java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
at java.base/java.nio.file.Files.copy(Files.java:1304)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
at
org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
at
org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
at
org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
at
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
at
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
at picocli.CommandLine.access$1500(CommandLine.java:148)
at
picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
at
picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
at picocli.CommandLine.execute(CommandLine.java:2174)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
at main.CamelJBang.main(CamelJBang.java:36)
{noformat}
Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
--runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
successfully and then calling mvn quarkus:dev is working fine
was:
it is a regression introduced in Camel 4.8.1, it is working fine with Camel
4.8.0
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
'test-with-xsl.camel.yaml'
* create an empty dummy.xsl file
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=. *.xsl
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
--runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
{noformat}
Reusing existing run data
Exporting as Quarkus project to: .
java.nio.file.NoSuchFileException:
.camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
at
java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
at
java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
at java.base/java.nio.file.Files.copy(Files.java:1304)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
at
org.apache.camel.dsl.jbang.core.commands.ExportQu
[jira] [Commented] (CAMEL-21442) camel-jbang - export is no more working when a previous run with an xsl file on the classpath occured
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898201#comment-17898201
]
Aurélien Pupier commented on CAMEL-21442:
-
when commenting out the line `camel.jbang.localKameletDir=file\:.` in the
.camel-jbang/camel-jbang-run.properties file, the export is working
> camel-jbang - export is no more working when a previous run with an xsl file
> on the classpath occured
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
> 'test-with-xsl.camel.yaml'
> * create an empty dummy.xsl file
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> *.xsl
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
> successfully and then calling mvn quarkus:dev is working fine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work started] (CAMEL-21442) camel-jbang - export is no more working when a previous run occured with local-kamelet-dir set to current dir
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-21442 started by Aurélien Pupier.
---
> camel-jbang - export is no more working when a previous run occured with
> local-kamelet-dir set to current dir
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Assignee: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init 'test.yaml'
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
> successfully and then calling mvn quarkus:dev is working fine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21442) camel-jbang - export is no more working when a previous run occured with local-kamelet-dir set to current dir
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier reassigned CAMEL-21442:
---
Assignee: Aurélien Pupier
> camel-jbang - export is no more working when a previous run occured with
> local-kamelet-dir set to current dir
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Assignee: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init 'test.yaml'
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
> successfully and then calling mvn quarkus:dev is working fine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20503) camel-http OAuth2 support for caching / refreshing tokens
[ https://issues.apache.org/jira/browse/CAMEL-20503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20503. - Resolution: Fixed > camel-http OAuth2 support for caching / refreshing tokens > - > > Key: CAMEL-20503 > URL: https://issues.apache.org/jira/browse/CAMEL-20503 > Project: Camel > Issue Type: New Feature > Components: camel-http >Affects Versions: 4.4.0 >Reporter: Joshua Grisham >Assignee: Ivan Kulaga >Priority: Major > Fix For: 4.9.0 > > > Currently the OAuth2 support in camel-http will retrieve a new token with > every single HTTP Request > It is typically a more preferred pattern to actually cache the access tokens > (per the same issuer, + for the same client_id + the same requested scopes) > as fetching tokens can be an expensive operation, plus that access tokens can > often have a relatively long expiration time which Camel could actually take > advantage of. > Some examples: > * Google's > [OAuth2Credentials|https://cloud.google.com/java/docs/reference/google-auth-library/latest/com.google.auth.oauth2.OAuth2Credentials] > class supports token caching and refresh (see: > [https://github.com/googleapis/google-auth-library-java/blob/main/oauth2_http/java/com/google/auth/oauth2/OAuth2Credentials.java]) > * Spring Security's OAuth2 client also does this "under the covers" (though > is a bit more complicated): > [https://github.com/spring-projects/spring-security/tree/main/oauth2/oauth2-client/src/main/java/org/springframework/security/oauth2/client] > The assumption is that users might want to be able to configure the behavior > of this somehow, so maybe it would be good to add some additional properties > to control if a cache is used at all and/or how "early" tokens should be > refreshed before their expiration time, if the token refresh mechanism should > be used instead of just requesting a totally new access token from scratch, > etc > It may also be worth to break this effort into smaller deliveries: > * first to add a token cache and then request new tokens only when old ones > are expired (depending on various config parameters) > * second to add a refresh mechanism to actually use the OAuth2 Refresh flow > instead of just fetching a totally new Access Token (with all appropriate > checks that a refresh token was actually given by the token provider from the > beginning etc...) see: > [https://datatracker.ietf.org/doc/html/rfc6749#section-1.5] and > [https://datatracker.ietf.org/doc/html/rfc6749#section-6] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21449) Potential ConcurrentModificationException in MainHelper.setPropertiesOnTarget(MainHelper.java:323)
Aurélien Pupier created CAMEL-21449:
---
Summary: Potential ConcurrentModificationException in
MainHelper.setPropertiesOnTarget(MainHelper.java:323)
Key: CAMEL-21449
URL: https://issues.apache.org/jira/browse/CAMEL-21449
Project: Camel
Issue Type: Bug
Components: camel-main
Affects Versions: 4.8.1
Reporter: Aurélien Pupier
revealed sometimes by test
org.apache.camel.main.MainThreadPoolTest.testCustomThreadPool :
{noformat}
java.util.ConcurrentModificationException
at
java.base/java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1521)
at java.base/java.util.TreeMap$KeyIterator.next(TreeMap.java:1575)
at
org.apache.camel.main.MainHelper.setPropertiesOnTarget(MainHelper.java:323)
at
org.apache.camel.main.MainSupportModelConfigurer.setThreadPoolProperties(MainSupportModelConfigurer.java:173)
at
org.apache.camel.main.BaseMainSupport.doConfigureCamelContextFromMainConfiguration(BaseMainSupport.java:1348)
at
org.apache.camel.main.BaseMainSupport.autoconfigure(BaseMainSupport.java:559)
at org.apache.camel.main.MainSupport.autoconfigure(MainSupport.java:79)
at
org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:885)
at
org.apache.camel.main.MainSupport.initCamelContext(MainSupport.java:346)
at org.apache.camel.main.Main.doInit(Main.java:133)
at
org.apache.camel.support.service.BaseService.init(BaseService.java:85)
at
org.apache.camel.support.service.BaseService.start(BaseService.java:115)
at
org.apache.camel.main.MainThreadPoolTest.testCustomThreadPool(MainThreadPoolTest.java:64)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21371) camel-core - Add converter for Reader to InputStream
[ https://issues.apache.org/jira/browse/CAMEL-21371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Mariani updated CAMEL-21371: - Fix Version/s: 4.8.2 > camel-core - Add converter for Reader to InputStream > > > Key: CAMEL-21371 > URL: https://issues.apache.org/jira/browse/CAMEL-21371 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.8.2, 4.9.0 > > > We have BufferedReader but we need for plain Reader -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21454) camel-main - Do not trigger JVM shutdown hook if already shutting down
[ https://issues.apache.org/jira/browse/CAMEL-21454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21454. - Resolution: Fixed > camel-main - Do not trigger JVM shutdown hook if already shutting down > -- > > Key: CAMEL-21454 > URL: https://issues.apache.org/jira/browse/CAMEL-21454 > Project: Camel > Issue Type: Improvement > Components: camel-main >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > For example during testing camel-main you can see JVM shutdown hook because > per test method can trigger this message. > However the app is shutting down cleanly so we dont need to show this logging. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21454) camel-main - Do not trigger JVM shutdown hook if already shutting down
Claus Ibsen created CAMEL-21454: --- Summary: camel-main - Do not trigger JVM shutdown hook if already shutting down Key: CAMEL-21454 URL: https://issues.apache.org/jira/browse/CAMEL-21454 Project: Camel Issue Type: Improvement Components: camel-main Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.9.0 For example during testing camel-main you can see JVM shutdown hook because per test method can trigger this message. However the app is shutting down cleanly so we dont need to show this logging. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21449) Potential ConcurrentModificationException in MainHelper.setPropertiesOnTarget(MainHelper.java:323)
[
https://issues.apache.org/jira/browse/CAMEL-21449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898323#comment-17898323
]
Claus Ibsen commented on CAMEL-21449:
-
This is hard to reproduce, even when setting @RepeatTest(2000) on the test
methods. Have you seen this more than once ?
> Potential ConcurrentModificationException in
> MainHelper.setPropertiesOnTarget(MainHelper.java:323)
> --
>
> Key: CAMEL-21449
> URL: https://issues.apache.org/jira/browse/CAMEL-21449
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
>
> revealed sometimes by test
> org.apache.camel.main.MainThreadPoolTest.testCustomThreadPool :
> {noformat}
> java.util.ConcurrentModificationException
> at
> java.base/java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1521)
> at java.base/java.util.TreeMap$KeyIterator.next(TreeMap.java:1575)
> at
> org.apache.camel.main.MainHelper.setPropertiesOnTarget(MainHelper.java:323)
> at
> org.apache.camel.main.MainSupportModelConfigurer.setThreadPoolProperties(MainSupportModelConfigurer.java:173)
> at
> org.apache.camel.main.BaseMainSupport.doConfigureCamelContextFromMainConfiguration(BaseMainSupport.java:1348)
> at
> org.apache.camel.main.BaseMainSupport.autoconfigure(BaseMainSupport.java:559)
> at org.apache.camel.main.MainSupport.autoconfigure(MainSupport.java:79)
> at
> org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:885)
> at
> org.apache.camel.main.MainSupport.initCamelContext(MainSupport.java:346)
> at org.apache.camel.main.Main.doInit(Main.java:133)
> at
> org.apache.camel.support.service.BaseService.init(BaseService.java:85)
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:115)
> at
> org.apache.camel.main.MainThreadPoolTest.testCustomThreadPool(MainThreadPoolTest.java:64)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21449) Potential ConcurrentModificationException in MainHelper.setPropertiesOnTarget(MainHelper.java:323)
[
https://issues.apache.org/jira/browse/CAMEL-21449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898333#comment-17898333
]
Aurélien Pupier commented on CAMEL-21449:
-
I think I already seen this test failed in the past (but not had time to
checked the stacktrace error nor report in the tracker).
In the little history of 5 builds on CI, it failed a single time.
Also in success for me locally when trying with @RepeatedTest(1)
> Potential ConcurrentModificationException in
> MainHelper.setPropertiesOnTarget(MainHelper.java:323)
> --
>
> Key: CAMEL-21449
> URL: https://issues.apache.org/jira/browse/CAMEL-21449
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
>
> revealed sometimes by test
> org.apache.camel.main.MainThreadPoolTest.testCustomThreadPool :
> {noformat}
> java.util.ConcurrentModificationException
> at
> java.base/java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1521)
> at java.base/java.util.TreeMap$KeyIterator.next(TreeMap.java:1575)
> at
> org.apache.camel.main.MainHelper.setPropertiesOnTarget(MainHelper.java:323)
> at
> org.apache.camel.main.MainSupportModelConfigurer.setThreadPoolProperties(MainSupportModelConfigurer.java:173)
> at
> org.apache.camel.main.BaseMainSupport.doConfigureCamelContextFromMainConfiguration(BaseMainSupport.java:1348)
> at
> org.apache.camel.main.BaseMainSupport.autoconfigure(BaseMainSupport.java:559)
> at org.apache.camel.main.MainSupport.autoconfigure(MainSupport.java:79)
> at
> org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:885)
> at
> org.apache.camel.main.MainSupport.initCamelContext(MainSupport.java:346)
> at org.apache.camel.main.Main.doInit(Main.java:133)
> at
> org.apache.camel.support.service.BaseService.init(BaseService.java:85)
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:115)
> at
> org.apache.camel.main.MainThreadPoolTest.testCustomThreadPool(MainThreadPoolTest.java:64)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21392) camel-jbang - Add support for --cluster-type=k3s
[ https://issues.apache.org/jira/browse/CAMEL-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved CAMEL-21392. Resolution: Fixed Done > camel-jbang - Add support for --cluster-type=k3s > > > Key: CAMEL-21392 > URL: https://issues.apache.org/jira/browse/CAMEL-21392 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.9.0 > > > K3S is a popular Kubernetes distribution built for IoT & Edge computing. > https://k3s.io -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21451) Migrate to JKube generated resources for all runtimes
[ https://issues.apache.org/jira/browse/CAMEL-21451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898248#comment-17898248 ] Claus Ibsen commented on CAMEL-21451: - Yes this makes it consistent and much easier to maintain at Apache Camel and for end users to have similar experience. jkube is very flexible and can also do advanced via its fragement files. > Migrate to JKube generated resources for all runtimes > - > > Key: CAMEL-21451 > URL: https://issues.apache.org/jira/browse/CAMEL-21451 > Project: Camel > Issue Type: Task > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > > The team decided (in Brno) to commonly use JKube to generate k8s resource > definitions. One set of documentation, properties, extension points for users > and tools to integrate with. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21450) Show how to use Ansible to create a private k3s cloud
Thomas Diesler created CAMEL-21450: -- Summary: Show how to use Ansible to create a private k3s cloud Key: CAMEL-21450 URL: https://issues.apache.org/jira/browse/CAMEL-21450 Project: Camel Issue Type: Task Components: documentation Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21451) Migrate to JKube generated resources for all runtimes
Thomas Diesler created CAMEL-21451: -- Summary: Migrate to JKube generated resources for all runtimes Key: CAMEL-21451 URL: https://issues.apache.org/jira/browse/CAMEL-21451 Project: Camel Issue Type: Task Components: camel-jbang Reporter: Thomas Diesler Assignee: Thomas Diesler The team decided (in Brno) to commonly use JKube to generate k8s resource definitions. One set of documentation, properties, extension points for users and tools to integrate with. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21452) camel-test-infra: decouple the infrastructure from the testing API
[
https://issues.apache.org/jira/browse/CAMEL-21452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-21452:
-
Estimated Complexity: (was: Unknown)
> camel-test-infra: decouple the infrastructure from the testing API
> --
>
> Key: CAMEL-21452
> URL: https://issues.apache.org/jira/browse/CAMEL-21452
> Project: Camel
> Issue Type: Task
> Components: camel-test-infra
>Reporter: Otavio Rodolfo Piske
>Priority: Major
>
> It turns out that the test infrastructure management code on the test-infra
> could be useful in multiple other scenarios (i.e.: for Camel JBang). However,
> there's a small set of classes that are bound to the test API used by Camel.
> These APIs would make re-purposing the test infra harder and inelegant for
> users of that code.
> It should be relatively simple to decouple this API (high-level steps,
> details may vary slightly):
> 1. Split
> {{{color:#00}org.apache.camel.test.infra.common.services{color}.TestService}}
> in 2 parts: one named {{InfrastructureService}} for the infrastructure code
> (containing {{{}registerProperties{}}}, {{{}initialize{}}}, {{shutdown}} and
> {{{}close{}}}) and another retaining the {{TestService}} name (containing the
> {{beforeAll}} and {{afterAll}} callbacks from JUnit's
> {{{}BeforeAllCallback{}}}, {color:#00}{{AfterAllCallback}}
> interfaces){color}
> {color:#00}2. Rename the existing {{Service}} to
> {{TestService}} (i.e.: {{{}ElasticSearchTestService{}}}) and make sure
> it implements the {{TestService}} API{color}
> {color:#00}3. Create a new Service and make sure it DOES NOT
> implement the {{TestService}} API
> {color}
> {color:#00}4. Move the infrastructure code to {{src/main}}{color}
> {color:#00}5. Keep the Camel-specific test infra code (i.e.:
> TestService) within {{src/test}}{color}
>
> Repeat for all services in the test-infra.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21452) camel-test-infra: decouple the infrastructure from the testing API
Otavio Rodolfo Piske created CAMEL-21452:
Summary: camel-test-infra: decouple the infrastructure from the
testing API
Key: CAMEL-21452
URL: https://issues.apache.org/jira/browse/CAMEL-21452
Project: Camel
Issue Type: Task
Components: camel-test-infra
Reporter: Otavio Rodolfo Piske
It turns out that the test infrastructure management code on the test-infra
could be useful in multiple other scenarios (i.e.: for Camel JBang). However,
there's a small set of classes that are bound to the test API used by Camel.
These APIs would make re-purposing the test infra harder and inelegant for
users of that code.
It should be relatively simple to decouple this API (high-level steps, details
may vary slightly):
1. Split
{{{color:#00}org.apache.camel.test.infra.common.services{color}.TestService}}
in 2 parts: one named {{InfrastructureService}} for the infrastructure code
(containing {{{}registerProperties{}}}, {{{}initialize{}}}, {{shutdown}} and
{{{}close{}}}) and another retaining the {{TestService}} name (containing the
{{beforeAll}} and {{afterAll}} callbacks from JUnit's
{{{}BeforeAllCallback{}}}, {color:#00}{{AfterAllCallback}}
interfaces){color}
{color:#00}2. Rename the existing {{Service}} to
{{TestService}} (i.e.: {{{}ElasticSearchTestService{}}}) and make sure it
implements the {{TestService}} API{color}
{color:#00}3. Create a new Service and make sure it DOES NOT
implement the {{TestService}} API
{color}
{color:#00}4. Move the infrastructure code to {{src/main}}{color}
{color:#00}5. Keep the Camel-specific test infra code (i.e.:
TestService) within {{src/test}}{color}
Repeat for all services in the test-infra.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21452) camel-test-infra: decouple the infrastructure from the testing API
[
https://issues.apache.org/jira/browse/CAMEL-21452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-21452:
-
Affects Version/s: 4.9.0
> camel-test-infra: decouple the infrastructure from the testing API
> --
>
> Key: CAMEL-21452
> URL: https://issues.apache.org/jira/browse/CAMEL-21452
> Project: Camel
> Issue Type: Task
> Components: camel-test-infra
>Affects Versions: 4.9.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
>
> It turns out that the test infrastructure management code on the test-infra
> could be useful in multiple other scenarios (i.e.: for Camel JBang). However,
> there's a small set of classes that are bound to the test API used by Camel.
> These APIs would make re-purposing the test infra harder and inelegant for
> users of that code.
> It should be relatively simple to decouple this API (high-level steps,
> details may vary slightly):
> 1. Split
> {{{color:#00}org.apache.camel.test.infra.common.services{color}.TestService}}
> in 2 parts: one named {{InfrastructureService}} for the infrastructure code
> (containing {{{}registerProperties{}}}, {{{}initialize{}}}, {{shutdown}} and
> {{{}close{}}}) and another retaining the {{TestService}} name (containing the
> {{beforeAll}} and {{afterAll}} callbacks from JUnit's
> {{{}BeforeAllCallback{}}}, {color:#00}{{AfterAllCallback}}
> interfaces){color}
> {color:#00}2. Rename the existing {{Service}} to
> {{TestService}} (i.e.: {{{}ElasticSearchTestService{}}}) and make sure
> it implements the {{TestService}} API{color}
> {color:#00}3. Create a new Service and make sure it DOES NOT
> implement the {{TestService}} API
> {color}
> {color:#00}4. Move the infrastructure code to {{src/main}}{color}
> {color:#00}5. Keep the Camel-specific test infra code (i.e.:
> TestService) within {{src/test}}{color}
>
> Repeat for all services in the test-infra.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21452) camel-test-infra: decouple the infrastructure from the testing API
[
https://issues.apache.org/jira/browse/CAMEL-21452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-21452:
-
Fix Version/s: 4.10.0
> camel-test-infra: decouple the infrastructure from the testing API
> --
>
> Key: CAMEL-21452
> URL: https://issues.apache.org/jira/browse/CAMEL-21452
> Project: Camel
> Issue Type: Task
> Components: camel-test-infra
>Affects Versions: 4.9.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.10.0
>
>
> It turns out that the test infrastructure management code on the test-infra
> could be useful in multiple other scenarios (i.e.: for Camel JBang). However,
> there's a small set of classes that are bound to the test API used by Camel.
> These APIs would make re-purposing the test infra harder and inelegant for
> users of that code.
> It should be relatively simple to decouple this API (high-level steps,
> details may vary slightly):
> 1. Split
> {{{color:#00}org.apache.camel.test.infra.common.services{color}.TestService}}
> in 2 parts: one named {{InfrastructureService}} for the infrastructure code
> (containing {{{}registerProperties{}}}, {{{}initialize{}}}, {{shutdown}} and
> {{{}close{}}}) and another retaining the {{TestService}} name (containing the
> {{beforeAll}} and {{afterAll}} callbacks from JUnit's
> {{{}BeforeAllCallback{}}}, {color:#00}{{AfterAllCallback}}
> interfaces){color}
> {color:#00}2. Rename the existing {{Service}} to
> {{TestService}} (i.e.: {{{}ElasticSearchTestService{}}}) and make sure
> it implements the {{TestService}} API{color}
> {color:#00}3. Create a new Service and make sure it DOES NOT
> implement the {{TestService}} API
> {color}
> {color:#00}4. Move the infrastructure code to {{src/main}}{color}
> {color:#00}5. Keep the Camel-specific test infra code (i.e.:
> TestService) within {{src/test}}{color}
>
> Repeat for all services in the test-infra.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21453) Camel-Spring-Boot: Kubernetes Configmaps Trigger context reloading on update
Andrea Cosentino created CAMEL-21453: Summary: Camel-Spring-Boot: Kubernetes Configmaps Trigger context reloading on update Key: CAMEL-21453 URL: https://issues.apache.org/jira/browse/CAMEL-21453 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 Related to CAMEL-21166 -- This message was sent by Atlassian Jira (v8.20.10#820010)
