[jira] [Updated] (CAMEL-21505) Binary files get corrupt when using 'base64' content transfer encoding due to String assignment of the decoded byte[]
[ https://issues.apache.org/jira/browse/CAMEL-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21505: Priority: Minor (was: Major) > Binary files get corrupt when using 'base64' content transfer encoding due to > String assignment of the decoded byte[] > - > > Key: CAMEL-21505 > URL: https://issues.apache.org/jira/browse/CAMEL-21505 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 4.8.1 > Environment: Windows and Docker > Java 21 Temurin >Reporter: Meinolf S-D >Priority: Minor > Attachments: image-2024-12-03-12-29-47-487.png > > > Binary files get corrupt when using *base64* content transfer encoding due to > String assignment of the decoded byte[] > This can easily be tested sending a .zip file to Camel AS2 listener. > After some investigation the issue seems to be in the EntityUtil.decode > method. > As shown in the screenshot the decoded (binary) byte[] is assigned to a new > String which result into corrupt date in case of binary content. > !image-2024-12-03-12-29-47-487.png! > In addition there are new line characters in the encoded base64 encoded > String data object. > In case of using transfer encoding type *binary* > java.nio.charset.MalformedInputException: Input length = 1 it thrown which > might be OK. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21500) camel-observability-services - Is missing in camel-catalog
[ https://issues.apache.org/jira/browse/CAMEL-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21500. - Resolution: Fixed > camel-observability-services - Is missing in camel-catalog > -- > > Key: CAMEL-21500 > URL: https://issues.apache.org/jira/browse/CAMEL-21500 > Project: Camel > Issue Type: Task > Components: camel-catalog >Affects Versions: 4.9.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.10.0 > > > Should be generated as an other kind and included in the catalog -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21505) camel-as2: Binary files get corrupt when using 'base64' content transfer encoding
[ https://issues.apache.org/jira/browse/CAMEL-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21505: Summary: camel-as2: Binary files get corrupt when using 'base64' content transfer encoding (was: Binary files get corrupt when using 'base64' content transfer encoding due to String assignment of the decoded byte[]) > camel-as2: Binary files get corrupt when using 'base64' content transfer > encoding > - > > Key: CAMEL-21505 > URL: https://issues.apache.org/jira/browse/CAMEL-21505 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 4.8.1 > Environment: Windows and Docker > Java 21 Temurin >Reporter: Meinolf S-D >Priority: Minor > Fix For: 4.8.3, 4.10.0 > > Attachments: image-2024-12-03-12-29-47-487.png > > > Binary files get corrupt when using *base64* content transfer encoding due to > String assignment of the decoded byte[] > This can easily be tested sending a .zip file to Camel AS2 listener. > After some investigation the issue seems to be in the EntityUtil.decode > method. > As shown in the screenshot the decoded (binary) byte[] is assigned to a new > String which result into corrupt date in case of binary content. > !image-2024-12-03-12-29-47-487.png! > In addition there are new line characters in the encoded base64 encoded > String data object. > In case of using transfer encoding type *binary* > java.nio.charset.MalformedInputException: Input length = 1 it thrown which > might be OK. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21505) Binary files get corrupt when using 'base64' content transfer encoding due to String assignment of the decoded byte[]
[ https://issues.apache.org/jira/browse/CAMEL-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902598#comment-17902598 ] Claus Ibsen commented on CAMEL-21505: - You are welcome to send a PR with a potential fix for review > Binary files get corrupt when using 'base64' content transfer encoding due to > String assignment of the decoded byte[] > - > > Key: CAMEL-21505 > URL: https://issues.apache.org/jira/browse/CAMEL-21505 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 4.8.1 > Environment: Windows and Docker > Java 21 Temurin >Reporter: Meinolf S-D >Priority: Minor > Attachments: image-2024-12-03-12-29-47-487.png > > > Binary files get corrupt when using *base64* content transfer encoding due to > String assignment of the decoded byte[] > This can easily be tested sending a .zip file to Camel AS2 listener. > After some investigation the issue seems to be in the EntityUtil.decode > method. > As shown in the screenshot the decoded (binary) byte[] is assigned to a new > String which result into corrupt date in case of binary content. > !image-2024-12-03-12-29-47-487.png! > In addition there are new line characters in the encoded base64 encoded > String data object. > In case of using transfer encoding type *binary* > java.nio.charset.MalformedInputException: Input length = 1 it thrown which > might be OK. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21505) Binary files get corrupt when using 'base64' content transfer encoding due to String assignment of the decoded byte[]
[ https://issues.apache.org/jira/browse/CAMEL-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21505: Fix Version/s: 4.8.3 4.10.0 > Binary files get corrupt when using 'base64' content transfer encoding due to > String assignment of the decoded byte[] > - > > Key: CAMEL-21505 > URL: https://issues.apache.org/jira/browse/CAMEL-21505 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 4.8.1 > Environment: Windows and Docker > Java 21 Temurin >Reporter: Meinolf S-D >Priority: Minor > Fix For: 4.8.3, 4.10.0 > > Attachments: image-2024-12-03-12-29-47-487.png > > > Binary files get corrupt when using *base64* content transfer encoding due to > String assignment of the decoded byte[] > This can easily be tested sending a .zip file to Camel AS2 listener. > After some investigation the issue seems to be in the EntityUtil.decode > method. > As shown in the screenshot the decoded (binary) byte[] is assigned to a new > String which result into corrupt date in case of binary content. > !image-2024-12-03-12-29-47-487.png! > In addition there are new line characters in the encoded base64 encoded > String data object. > In case of using transfer encoding type *binary* > java.nio.charset.MalformedInputException: Input length = 1 it thrown which > might be OK. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21495) camel-quarkus: REST route inlining works incorrectly when testing
[
https://issues.apache.org/jira/browse/CAMEL-21495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902622#comment-17902622
]
Claus Ibsen commented on CAMEL-21495:
-
[~jamesnetherton] something to look into for CEQ
> camel-quarkus: REST route inlining works incorrectly when testing
> -
>
> Key: CAMEL-21495
> URL: https://issues.apache.org/jira/browse/CAMEL-21495
> Project: Camel
> Issue Type: Bug
> Components: camel-rest-openapi
>Affects Versions: 4.8.1
>Reporter: Sami Peltola
>Priority: Minor
> Attachments: quarkus-camel-rest-inline-issue.zip
>
>
> h2. The Issue: REST-route inlining works incorrectly/inconsistently when
> testing
> Encountered when running tests, sometimes the wrong subroute gets inlined to
> the rest-route and causes failures.
> Referring to:
> [https://camel.apache.org/manual/rest-dsl.html#_inline_rest_dsl_as_a_single_route]
> I've attached an example project. When running the tests, a test called
> "FailingTest" should have "camel.rest.inline-routes" enabled and should fail,
> as opposed to "SucceedingTest" which has the option disabled and does not
> fail.
> It seems like when inlining the routes, the subroute "get-from-db-route" gets
> inlined when actually route "quarkuscamelexampleservice-http-get-route"
> should be inlined as it is the subroute that is called from the REST-route.
> For some reason, the tests failing also seems a bit flaky, so you might have
> to run all the tests in a loop to replicate the issue, i've included a script
> "run-test-in-loop.sh".
> When the test fails, it only shows routes:
> {code:java}
> 2024-12-02 10:45:20,687 INFO [org.apa.cam.qua.cor.CamelBootstrapRecorder]
> (main) Apache Camel Quarkus 3.16.0 is starting
> 2024-12-02 10:45:20,687 INFO [org.apa.cam.mai.MainSupport] (main) Apache
> Camel (Main) 4.8.1 is starting
> 2024-12-02 10:45:20,716 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> Auto-configuration summary
> 2024-12-02 10:45:20,716 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> [MicroProfilePropertiesSource] camel.main.dumpRoutes = xml
> 2024-12-02 10:45:20,716 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> [JVM System Property] camel.rest.inlineRoutes = true
> 2024-12-02 10:45:20,882 INFO [org.apa.cam.imp.eng.AbstractCamelContext]
> (main) Apache Camel 4.8.1 (camel-1) is starting
> 2024-12-02 10:45:20,894 INFO [org.apa.cam.imp.DefaultDumpRoutesStrategy]
> (main) Dumping 5 routes as XML
> 2024-12-02 10:45:20,895 INFO [org.apa.cam.imp.DefaultDumpRoutesStrategy]
> (main)
>
>
>
> java.lang.Exception
>
>
> Error with database backend:
> ${exception.message}
>
>
>
>
>
>
> {code}
>
> Sometimes it works correctly, and shows how it actually should have inlined
> the routes with the route "subroute-for-get" not being inlined to the
> REST-route,but instead existing as a separate route in the context:
> {code:java}
> 2024-12-02 10:40:11,095 INFO [org.apa.cam.qua.cor.CamelBootstrapRecorder]
> (main) Apache Camel Quarkus 3.16.0 is starting
> 2024-12-02 10:40:11,096 INFO [org.apa.cam.mai.MainSupport] (main) Apache
> Camel (Main) 4.8.1 is starting
> 2024-12-02 10:40:11,198 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> Auto-configuration summary
> 2024-12-02 10:40:11,198 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> [MicroProfilePropertiesSource] camel.main.dumpRoutes = xml
> 2024-12-02 10:40:11,199 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> [JVM System Property] camel.rest.inlineRoutes = true
> 2024-12-02 10:40:11,857 INFO [org.apa.cam.imp.eng.AbstractCamelContext]
> (main) Apache Camel 4.8.1 (camel-1) is starting
> 2024-12-02 10:40:11,923 INFO [org.apa.cam.imp.DefaultDumpRoutesStrategy]
> (main) Dumping 6 routes as XML
> 2024-12-02 10:40:11,924 INFO [org.apa.cam.imp.DefaultDumpRoutesStrategy]
> (main)
>
>
>
> java.lang.Exception
>
>
> Error with database backend:
> ${exception.message}
>
>
>
>
>
>
>
>
>
> java.lang.Exception
>
>
> Error with http backend: ${exception.message}
>
>
>
>
>
>
> {code}
> I have not had any issues when running in quarkus dev-mode, so i am assuming
> this only affects testing.
> h2. Workaround
> For tests, disabled inlining the routes with:
> {code:java}
> camel.rest.inline-routes = false
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21504) camel-spring-boot - MicrometerTagsAutoConfiguration class puts http method in uri tag
[
https://issues.apache.org/jira/browse/CAMEL-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902620#comment-17902620
]
Claus Ibsen commented on CAMEL-21504:
-
[~Federico Mariani] something possible to look into for CSB
> camel-spring-boot - MicrometerTagsAutoConfiguration class puts http method in
> uri tag
> -
>
> Key: CAMEL-21504
> URL: https://issues.apache.org/jira/browse/CAMEL-21504
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
>Affects Versions: 4.4.4, 4.8.1
>Reporter: Nikola Dangubic
>Priority: Minor
> Fix For: 4.8.3, 4.10.0
>
>
> [MicrometerTagsAutoConfiguration|https://github.com/apache/camel-spring-boot/blob/cf415a2c4dc1e6f7b14412d641e4fefd42786081/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java]
> probably has copy/paste error where instead of uri it puts http method in
> map for metrics
> {code:java}
> return KeyValue.of("uri", context.getCarrier().getMethod()); {code}
> and output looks like
> {code:java}
> # TYPE http_server_requests_active_seconds summary
> http_server_requests_active_seconds_count{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0
> http_server_requests_active_seconds_sum{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0.0 {code}
> One would expect uri value for uri tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21504) camel-spring-boot - MicrometerTagsAutoConfiguration class puts http method in uri tag
[
https://issues.apache.org/jira/browse/CAMEL-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21504:
Fix Version/s: 4.8.3
4.10.0
> camel-spring-boot - MicrometerTagsAutoConfiguration class puts http method in
> uri tag
> -
>
> Key: CAMEL-21504
> URL: https://issues.apache.org/jira/browse/CAMEL-21504
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
>Affects Versions: 4.4.4, 4.8.1
>Reporter: Nikola Dangubic
>Priority: Minor
> Fix For: 4.8.3, 4.10.0
>
>
> [MicrometerTagsAutoConfiguration|https://github.com/apache/camel-spring-boot/blob/cf415a2c4dc1e6f7b14412d641e4fefd42786081/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java]
> probably has copy/paste error where instead of uri it puts http method in
> map for metrics
> {code:java}
> return KeyValue.of("uri", context.getCarrier().getMethod()); {code}
> and output looks like
> {code:java}
> # TYPE http_server_requests_active_seconds summary
> http_server_requests_active_seconds_count{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0
> http_server_requests_active_seconds_sum{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0.0 {code}
> One would expect uri value for uri tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21504) camel-spring-boot - MicrometerTagsAutoConfiguration class puts http method in uri tag
[
https://issues.apache.org/jira/browse/CAMEL-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902619#comment-17902619
]
Claus Ibsen commented on CAMEL-21504:
-
Thanks for the pointer to the JIRA.
> camel-spring-boot - MicrometerTagsAutoConfiguration class puts http method in
> uri tag
> -
>
> Key: CAMEL-21504
> URL: https://issues.apache.org/jira/browse/CAMEL-21504
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
>Affects Versions: 4.4.4, 4.8.1
>Reporter: Nikola Dangubic
>Priority: Minor
> Fix For: 4.8.3, 4.10.0
>
>
> [MicrometerTagsAutoConfiguration|https://github.com/apache/camel-spring-boot/blob/cf415a2c4dc1e6f7b14412d641e4fefd42786081/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java]
> probably has copy/paste error where instead of uri it puts http method in
> map for metrics
> {code:java}
> return KeyValue.of("uri", context.getCarrier().getMethod()); {code}
> and output looks like
> {code:java}
> # TYPE http_server_requests_active_seconds summary
> http_server_requests_active_seconds_count{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0
> http_server_requests_active_seconds_sum{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0.0 {code}
> One would expect uri value for uri tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21503) camel-langchain4j-chat: remove function calling
[ https://issues.apache.org/jira/browse/CAMEL-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21503: Component/s: camel-ai > camel-langchain4j-chat: remove function calling > --- > > Key: CAMEL-21503 > URL: https://issues.apache.org/jira/browse/CAMEL-21503 > Project: Camel > Issue Type: Task > Components: camel-ai >Affects Versions: 4.9.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.10.0 > > > Function calling features were moved to the tools component as part of > CAMEL-21153. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21499) Error while loading Spring XML context when using MOXy as the JAXB implementation
[
https://issues.apache.org/jira/browse/CAMEL-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902621#comment-17902621
]
Claus Ibsen commented on CAMEL-21499:
-
We only support what camel out of the box with Camel, which is sun JAXB
> Error while loading Spring XML context when using MOXy as the JAXB
> implementation
> -
>
> Key: CAMEL-21499
> URL: https://issues.apache.org/jira/browse/CAMEL-21499
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-xml
>Affects Versions: 4.8.0
>Reporter: Adriano Machado
>Priority: Minor
>
> The following error message is shown on a unit test after upgrading the Camel
> version from 4.4.0 to 4.8.0:
> {code:java}
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> Caused by: jakarta.xml.bind.JAXBException:
> Exception Description: An attempt was made to set more than one XmlAnyElement
> property on class [org.apache.camel.model.app.BeansDefinition]. Property
> [blueprintBeans] cannot be set as XmlAnyElement, because property
> [springBeans] is already set as XmlAnyElement.
> - with linked exception:
> [Exception [EclipseLink-50032] (Eclipse Persistence Services -
> 4.0.4.v202407190748-059428cdd2583c46f1f3e50d235854840a6fa9a7):
> org.eclipse.persistence.exceptions.JAXBException
> Exception Description: An attempt was made to set more than one XmlAnyElement
> property on class [org.apache.camel.model.app.BeansDefinition]. Property
> [blueprintBeans] cannot be set as XmlAnyElement, because property
> [springBeans] is already set as XmlAnyElement.]
> at
> org.eclipse.persistence.jaxb.JAXBContext$ContextPathInput.createContextState(JAXBContext.java:994)
> at
> org.eclipse.persistence.jaxb.JAXBContext$ContextPathInput.createContextState(JAXBContext.java:923)
> at
> org.eclipse.persistence.jaxb.JAXBContext.(JAXBContext.java:208)
> at
> org.eclipse.persistence.jaxb.JAXBContextFactory.createContext(JAXBContextFactory.java:131)
> at
> org.eclipse.persistence.jaxb.XMLBindingContextFactory.createContext(XMLBindingContextFactory.java:61)
> at jakarta.xml.bind.ContextFinder.find(ContextFinder.java:322)
> at jakarta.xml.bind.JAXBContext.newInstance(JAXBContext.java:392)
> at jakarta.xml.bind.JAXBContext.newInstance(JAXBContext.java:349)
> at
> org.apache.camel.xml.jaxb.DefaultModelJAXBContextFactory.newJAXBContext(DefaultModelJAXBContextFactory.java:44)
> at
> org.apache.camel.spring.xml.handler.CamelNamespaceHandler.getJaxbContext(CamelNamespaceHandler.java:206)
> at
> org.apache.camel.spring.xml.handler.CamelNamespaceHandler$CamelContextBeanDefinitionParser.doParse(CamelNamespaceHandler.java:428)
> ... 72 more
> Caused by: Exception [EclipseLink-50032] (Eclipse Persistence Services -
> 4.0.4.v202407190748-059428cdd2583c46f1f3e50d235854840a6fa9a7):
> org.eclipse.persistence.exceptions.JAXBException
> Exception Description: An attempt was made to set more than one XmlAnyElement
> property on class [org.apache.camel.model.app.BeansDefinition]. Property
> [blueprintBeans] cannot be set as XmlAnyElement, because property
> [springBeans] is already set as XmlAnyElement.
> at
> org.eclipse.persistence.exceptions.JAXBException.xmlAnyElementAlreadySet(JAXBException.java:489)
> at
> org.eclipse.persistence.jaxb.compiler.AnnotationsProcessor.finalizeProperties(AnnotationsProcessor.java:1036)
> at
> org.eclipse.persistence.jaxb.compiler.AnnotationsProcessor.processClassesAndProperties(AnnotationsProcessor.java:309)
> at
> org.eclipse.persistence.jaxb.compiler.Generator.(Generator.java:112)
> at
> org.eclipse.persistence.jaxb.JAXBContext$ContextPathInput.createContextState(JAXBContext.java:991)
> ... 82 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21503) camel-langchain4j-chat: remove function calling
[ https://issues.apache.org/jira/browse/CAMEL-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-21503: - Component/s: camel-langchain4j-chat > camel-langchain4j-chat: remove function calling > --- > > Key: CAMEL-21503 > URL: https://issues.apache.org/jira/browse/CAMEL-21503 > Project: Camel > Issue Type: Task > Components: camel-ai, camel-langchain4j-chat >Affects Versions: 4.9.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.10.0 > > > Function calling features were moved to the tools component as part of > CAMEL-21153. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21495) camel-quarkus: REST route inlining works incorrectly when testing
[
https://issues.apache.org/jira/browse/CAMEL-21495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902623#comment-17902623
]
Claus Ibsen commented on CAMEL-21495:
-
Sami, can you try to build an vanilla project to help identify if its only when
using Quarkus or not.
> camel-quarkus: REST route inlining works incorrectly when testing
> -
>
> Key: CAMEL-21495
> URL: https://issues.apache.org/jira/browse/CAMEL-21495
> Project: Camel
> Issue Type: Bug
> Components: camel-rest-openapi
>Affects Versions: 4.8.1
>Reporter: Sami Peltola
>Priority: Minor
> Attachments: quarkus-camel-rest-inline-issue.zip
>
>
> h2. The Issue: REST-route inlining works incorrectly/inconsistently when
> testing
> Encountered when running tests, sometimes the wrong subroute gets inlined to
> the rest-route and causes failures.
> Referring to:
> [https://camel.apache.org/manual/rest-dsl.html#_inline_rest_dsl_as_a_single_route]
> I've attached an example project. When running the tests, a test called
> "FailingTest" should have "camel.rest.inline-routes" enabled and should fail,
> as opposed to "SucceedingTest" which has the option disabled and does not
> fail.
> It seems like when inlining the routes, the subroute "get-from-db-route" gets
> inlined when actually route "quarkuscamelexampleservice-http-get-route"
> should be inlined as it is the subroute that is called from the REST-route.
> For some reason, the tests failing also seems a bit flaky, so you might have
> to run all the tests in a loop to replicate the issue, i've included a script
> "run-test-in-loop.sh".
> When the test fails, it only shows routes:
> {code:java}
> 2024-12-02 10:45:20,687 INFO [org.apa.cam.qua.cor.CamelBootstrapRecorder]
> (main) Apache Camel Quarkus 3.16.0 is starting
> 2024-12-02 10:45:20,687 INFO [org.apa.cam.mai.MainSupport] (main) Apache
> Camel (Main) 4.8.1 is starting
> 2024-12-02 10:45:20,716 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> Auto-configuration summary
> 2024-12-02 10:45:20,716 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> [MicroProfilePropertiesSource] camel.main.dumpRoutes = xml
> 2024-12-02 10:45:20,716 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> [JVM System Property] camel.rest.inlineRoutes = true
> 2024-12-02 10:45:20,882 INFO [org.apa.cam.imp.eng.AbstractCamelContext]
> (main) Apache Camel 4.8.1 (camel-1) is starting
> 2024-12-02 10:45:20,894 INFO [org.apa.cam.imp.DefaultDumpRoutesStrategy]
> (main) Dumping 5 routes as XML
> 2024-12-02 10:45:20,895 INFO [org.apa.cam.imp.DefaultDumpRoutesStrategy]
> (main)
>
>
>
> java.lang.Exception
>
>
> Error with database backend:
> ${exception.message}
>
>
>
>
>
>
> {code}
>
> Sometimes it works correctly, and shows how it actually should have inlined
> the routes with the route "subroute-for-get" not being inlined to the
> REST-route,but instead existing as a separate route in the context:
> {code:java}
> 2024-12-02 10:40:11,095 INFO [org.apa.cam.qua.cor.CamelBootstrapRecorder]
> (main) Apache Camel Quarkus 3.16.0 is starting
> 2024-12-02 10:40:11,096 INFO [org.apa.cam.mai.MainSupport] (main) Apache
> Camel (Main) 4.8.1 is starting
> 2024-12-02 10:40:11,198 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> Auto-configuration summary
> 2024-12-02 10:40:11,198 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> [MicroProfilePropertiesSource] camel.main.dumpRoutes = xml
> 2024-12-02 10:40:11,199 INFO [org.apa.cam.mai.BaseMainSupport] (main)
> [JVM System Property] camel.rest.inlineRoutes = true
> 2024-12-02 10:40:11,857 INFO [org.apa.cam.imp.eng.AbstractCamelContext]
> (main) Apache Camel 4.8.1 (camel-1) is starting
> 2024-12-02 10:40:11,923 INFO [org.apa.cam.imp.DefaultDumpRoutesStrategy]
> (main) Dumping 6 routes as XML
> 2024-12-02 10:40:11,924 INFO [org.apa.cam.imp.DefaultDumpRoutesStrategy]
> (main)
>
>
>
> java.lang.Exception
>
>
> Error with database backend:
> ${exception.message}
>
>
>
>
>
>
>
>
>
> java.lang.Exception
>
>
> Error with http backend: ${exception.message}
>
>
>
>
>
>
> {code}
> I have not had any issues when running in quarkus dev-mode, so i am assuming
> this only affects testing.
> h2. Workaround
> For tests, disabled inlining the routes with:
> {code:java}
> camel.rest.inline-routes = false
> {code}
--
This message was sent b
[jira] [Commented] (CAMEL-21486) camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000
[ https://issues.apache.org/jira/browse/CAMEL-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902636#comment-17902636 ] Thomas Diesler commented on CAMEL-21486: This will be a recurring problem for must stuff we do on main. Before I redo much of this work, I'd like to hear from [~gfournier] whether it is possible to upgrade the foundation i.e. the Traits API > camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000 > - > > Key: CAMEL-21486 > URL: https://issues.apache.org/jira/browse/CAMEL-21486 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.1 >Reporter: Andrea Cosentino >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.3, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21506) camel-pdf: type converter doesn't work with the file component
Otavio Rodolfo Piske created CAMEL-21506:
Summary: camel-pdf: type converter doesn't work with the file
component
Key: CAMEL-21506
URL: https://issues.apache.org/jira/browse/CAMEL-21506
Project: Camel
Issue Type: Bug
Components: camel-pdf
Affects Versions: 4.8.2
Reporter: Otavio Rodolfo Piske
Assignee: Otavio Rodolfo Piske
Fix For: 4.8.3, 4.10.0
The following route breaks the code:
{code:java}
- route:
id: route-4165
from:
id: from-1263
uri: file:pdf
parameters:
include: .*\.pdf
steps:
- to:
id: to-1793
uri: pdf:extractText
parameters: {}
- log:
id: log-2285
message: ${body}{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21456) Camel-Jbang Kubernetes Plugin Ingress add TLS
[ https://issues.apache.org/jira/browse/CAMEL-21456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaelle Fournier resolved CAMEL-21456. - Fix Version/s: 4.x Resolution: Fixed > Camel-Jbang Kubernetes Plugin Ingress add TLS > - > > Key: CAMEL-21456 > URL: https://issues.apache.org/jira/browse/CAMEL-21456 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.x >Reporter: Gaelle Fournier >Assignee: Gaelle Fournier >Priority: Minor > Fix For: 4.x > > > Camel jbang kubernetes plugin trait Ingress does not yet allow for > configuration of TLS, as is available in CK > ([https://camel.apache.org/camel-k/2.5.x/traits/ingress.html).] > The Ingress model class is already up to date. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21505) Binary files get corrupt when using 'base64' content transfer encoding due to String assignment of the decoded byte[]
Meinolf S-D created CAMEL-21505: --- Summary: Binary files get corrupt when using 'base64' content transfer encoding due to String assignment of the decoded byte[] Key: CAMEL-21505 URL: https://issues.apache.org/jira/browse/CAMEL-21505 Project: Camel Issue Type: Bug Components: camel-as2 Affects Versions: 4.8.1 Environment: Windows and Docker Java 21 Temurin Reporter: Meinolf S-D Attachments: image-2024-12-03-12-29-47-487.png Binary files get corrupt when using *base64* content transfer encoding due to String assignment of the decoded byte[] This can easily be tested sending a .zip file to Camel AS2 listener. After some investigation the issue seems to be in the EntityUtil.decode method. As shown in the screenshot the decoded (binary) byte[] is assigned to a new String which result into corrupt date in case of binary content. !image-2024-12-03-12-29-47-487.png! In addition there are new line characters in the encoded base64 encoded String data object. In case of using transfer encoding type *binary* java.nio.charset.MalformedInputException: Input length = 1 it thrown which might be OK. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21456) Camel-Jbang Kubernetes Plugin Ingress add TLS
[ https://issues.apache.org/jira/browse/CAMEL-21456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21456: Fix Version/s: 4.10.0 (was: 4.x) > Camel-Jbang Kubernetes Plugin Ingress add TLS > - > > Key: CAMEL-21456 > URL: https://issues.apache.org/jira/browse/CAMEL-21456 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.x >Reporter: Gaelle Fournier >Assignee: Gaelle Fournier >Priority: Minor > Fix For: 4.10.0 > > > Camel jbang kubernetes plugin trait Ingress does not yet allow for > configuration of TLS, as is available in CK > ([https://camel.apache.org/camel-k/2.5.x/traits/ingress.html).] > The Ingress model class is already up to date. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21499) Error while loading Spring XML context when using Eclipselink MOXy as the JAXB implementation
[
https://issues.apache.org/jira/browse/CAMEL-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adriano Machado updated CAMEL-21499:
Summary: Error while loading Spring XML context when using Eclipselink MOXy
as the JAXB implementation (was: Error while loading Spring XML context when
using MOXy as the JAXB implementation)
> Error while loading Spring XML context when using Eclipselink MOXy as the
> JAXB implementation
> -
>
> Key: CAMEL-21499
> URL: https://issues.apache.org/jira/browse/CAMEL-21499
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-xml
>Affects Versions: 4.8.0
>Reporter: Adriano Machado
>Priority: Minor
>
> The following error message is shown on a unit test after upgrading the Camel
> version from 4.4.0 to 4.8.0:
> {code:java}
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> Caused by: jakarta.xml.bind.JAXBException:
> Exception Description: An attempt was made to set more than one XmlAnyElement
> property on class [org.apache.camel.model.app.BeansDefinition]. Property
> [blueprintBeans] cannot be set as XmlAnyElement, because property
> [springBeans] is already set as XmlAnyElement.
> - with linked exception:
> [Exception [EclipseLink-50032] (Eclipse Persistence Services -
> 4.0.4.v202407190748-059428cdd2583c46f1f3e50d235854840a6fa9a7):
> org.eclipse.persistence.exceptions.JAXBException
> Exception Description: An attempt was made to set more than one XmlAnyElement
> property on class [org.apache.camel.model.app.BeansDefinition]. Property
> [blueprintBeans] cannot be set as XmlAnyElement, because property
> [springBeans] is already set as XmlAnyElement.]
> at
> org.eclipse.persistence.jaxb.JAXBContext$ContextPathInput.createContextState(JAXBContext.java:994)
> at
> org.eclipse.persistence.jaxb.JAXBContext$ContextPathInput.createContextState(JAXBContext.java:923)
> at
> org.eclipse.persistence.jaxb.JAXBContext.(JAXBContext.java:208)
> at
> org.eclipse.persistence.jaxb.JAXBContextFactory.createContext(JAXBContextFactory.java:131)
> at
> org.eclipse.persistence.jaxb.XMLBindingContextFactory.createContext(XMLBindingContextFactory.java:61)
> at jakarta.xml.bind.ContextFinder.find(ContextFinder.java:322)
> at jakarta.xml.bind.JAXBContext.newInstance(JAXBContext.java:392)
> at jakarta.xml.bind.JAXBContext.newInstance(JAXBContext.java:349)
> at
> org.apache.camel.xml.jaxb.DefaultModelJAXBContextFactory.newJAXBContext(DefaultModelJAXBContextFactory.java:44)
> at
> org.apache.camel.spring.xml.handler.CamelNamespaceHandler.getJaxbContext(CamelNamespaceHandler.java:206)
> at
> org.apache.camel.spring.xml.handler.CamelNamespaceHandler$CamelContextBeanDefinitionParser.doParse(CamelNamespaceHandler.java:428)
> ... 72 more
> Caused by: Exception [EclipseLink-50032] (Eclipse Persistence Services -
> 4.0.4.v202407190748-059428cdd2583c46f1f3e50d235854840a6fa9a7):
> org.eclipse.persistence.exceptions.JAXBException
> Exception Description: An attempt was made to set more than one XmlAnyElement
> property on class [org.apache.camel.model.app.BeansDefinition]. Property
> [blueprintBeans] cannot be set as XmlAnyElement, because property
> [springBeans] is already set as XmlAnyElement.
> at
> org.eclipse.persistence.exceptions.JAXBException.xmlAnyElementAlreadySet(JAXBException.java:489)
> at
> org.eclipse.persistence.jaxb.compiler.AnnotationsProcessor.finalizeProperties(AnnotationsProcessor.java:1036)
> at
> org.eclipse.persistence.jaxb.compiler.AnnotationsProcessor.processClassesAndProperties(AnnotationsProcessor.java:309)
> at
> org.eclipse.persistence.jaxb.compiler.Generator.(Generator.java:112)
> at
> org.eclipse.persistence.jaxb.JAXBContext$ContextPathInput.createContextState(JAXBContext.java:991)
> ... 82 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21507) Camel-Jbang Kubernetes Plugin: Use new Trait model
[ https://issues.apache.org/jira/browse/CAMEL-21507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaelle Fournier reassigned CAMEL-21507: --- Assignee: Gaelle Fournier > Camel-Jbang Kubernetes Plugin: Use new Trait model > -- > > Key: CAMEL-21507 > URL: https://issues.apache.org/jira/browse/CAMEL-21507 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.8.2 >Reporter: Gaelle Fournier >Assignee: Gaelle Fournier >Priority: Major > Fix For: 4.8.3 > > > To avoid maintenance effort for camel-jbang kubernetes plugib on LTS 4.8.x, > the current Trait model needs to be backported on 4.8.x. > This means any work from these issues compatible with 4.8.x: > * https://issues.apache.org/jira/browse/CAMEL-21152 > * https://issues.apache.org/jira/browse/CAMEL-21278 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21486) camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000
[ https://issues.apache.org/jira/browse/CAMEL-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902537#comment-17902537 ] Thomas Diesler commented on CAMEL-21486: I can take a closer look at this again. AFAIR, there were some major incompatibilies that prevented the backport > camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000 > - > > Key: CAMEL-21486 > URL: https://issues.apache.org/jira/browse/CAMEL-21486 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.1 >Reporter: Andrea Cosentino >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.3, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21502) camel-langchain4j-tools: fix incorrect documentation
[ https://issues.apache.org/jira/browse/CAMEL-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-21502: - Affects Version/s: 4.8.1 > camel-langchain4j-tools: fix incorrect documentation > > > Key: CAMEL-21502 > URL: https://issues.apache.org/jira/browse/CAMEL-21502 > Project: Camel > Issue Type: Task > Components: camel-langchain4j-tools >Affects Versions: 4.8.1 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > > Some bits of the documentation still refer to "langchain4j-chat". These > should be fixed to use the tools component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21486) camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000
[ https://issues.apache.org/jira/browse/CAMEL-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902563#comment-17902563 ] Thomas Diesler edited comment on CAMEL-21486 at 12/3/24 9:15 AM: - There are a number of camel-jbang kubernetes commits that could not be backported because of an incompatibility with the traits model (see the linked dependency). I guess we need to ask [~gfournier] whether this can be backported first. CAMEL-21486: camel-jbang - cannot push to image-registry.openshift-image-registry.svc:5000 (#16398) Thomas Diesler* 28.11.24, 18:09 [CAMEL-21464] camel k8s run ... may lead to exec format error (#16345) Thomas Diesler* 21.11.24, 14:28 Camel-21457: Add knative service timeout on jbang plugin kubernetes Gaelle Fournier* 18.11.24, 16:49 CAMEL-21278: Remove unused code in Trait Model Gaelle Fournier* 02.10.24, 10:42 [CAMEL-21451] Migrate to JKube generated resources for all runtimes Thomas Diesler* 15.11.24, 15:39 chore: camel-jbang kubernetes plugin - remove docker requirement on export command (#16276) Gaëlle Fournier* 14.11.24, 12:27 (chores) camel-jbang: minor cleanups Otavio R. Piske* 09.11.24, 16:46 (chores) camel-jbang: disable resource intensive tests Otavio Rodolfo Piske 08.11.24, 14:30 [CAMEL-21392] Add support for --cluster-type=k3s Thomas Diesler* 29.10.24, 07:03 was (Author: tdiesler): There are a number of camel-jbang kubernetes commits that could not be backported because of an incompatibility with the traits model (see the linked dependency). I guess we need to ask [~gfournier] whether this can be backported first. ``` CAMEL-21486: camel-jbang - cannot push to image-registry.openshift-image-registry.svc:5000 (#16398) Thomas Diesler* 28.11.24, 18:09 [CAMEL-21464] camel k8s run ... may lead to exec format error (#16345) Thomas Diesler* 21.11.24, 14:28 Camel-21457: Add knative service timeout on jbang plugin kubernetes Gaelle Fournier* 18.11.24, 16:49 CAMEL-21278: Remove unused code in Trait Model Gaelle Fournier* 02.10.24, 10:42 [CAMEL-21451] Migrate to JKube generated resources for all runtimes Thomas Diesler* 15.11.24, 15:39 chore: camel-jbang kubernetes plugin - remove docker requirement on export command (#16276) Gaëlle Fournier* 14.11.24, 12:27 (chores) camel-jbang: minor cleanups Otavio R. Piske* 09.11.24, 16:46 (chores) camel-jbang: disable resource intensive tests Otavio Rodolfo Piske 08.11.24, 14:30 [CAMEL-21392] Add support for --cluster-type=k3s Thomas Diesler* 29.10.24, 07:03 ``` > camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000 > - > > Key: CAMEL-21486 > URL: https://issues.apache.org/jira/browse/CAMEL-21486 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.1 >Reporter: Andrea Cosentino >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.3, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21503) camel-langchain4j-chat: remove function calling
[ https://issues.apache.org/jira/browse/CAMEL-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-21503: - Fix Version/s: 4.10.0 > camel-langchain4j-chat: remove function calling > --- > > Key: CAMEL-21503 > URL: https://issues.apache.org/jira/browse/CAMEL-21503 > Project: Camel > Issue Type: Task >Affects Versions: 4.9.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.10.0 > > > Function calling features were moved to the tools component as part of > CAMEL-21153. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21486) camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000
[ https://issues.apache.org/jira/browse/CAMEL-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902563#comment-17902563 ] Thomas Diesler commented on CAMEL-21486: There are a number of camel-jbang kubernetes commits that could not be backported because of an incompatibility with the traits model (see the linked dependency). I guess we need to ask [~gfournier] whether this can be backported first. ``` CAMEL-21486: camel-jbang - cannot push to image-registry.openshift-image-registry.svc:5000 (#16398) Thomas Diesler* 28.11.24, 18:09 [CAMEL-21464] camel k8s run ... may lead to exec format error (#16345) Thomas Diesler* 21.11.24, 14:28 Camel-21457: Add knative service timeout on jbang plugin kubernetes Gaelle Fournier* 18.11.24, 16:49 CAMEL-21278: Remove unused code in Trait Model Gaelle Fournier* 02.10.24, 10:42 [CAMEL-21451] Migrate to JKube generated resources for all runtimes Thomas Diesler* 15.11.24, 15:39 chore: camel-jbang kubernetes plugin - remove docker requirement on export command (#16276) Gaëlle Fournier* 14.11.24, 12:27 (chores) camel-jbang: minor cleanups Otavio R. Piske* 09.11.24, 16:46 (chores) camel-jbang: disable resource intensive tests Otavio Rodolfo Piske 08.11.24, 14:30 [CAMEL-21392] Add support for --cluster-type=k3s Thomas Diesler* 29.10.24, 07:03 ``` > camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000 > - > > Key: CAMEL-21486 > URL: https://issues.apache.org/jira/browse/CAMEL-21486 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.1 >Reporter: Andrea Cosentino >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.3, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21502) camel-langchain4j-tools: fix incorrect documentation
[ https://issues.apache.org/jira/browse/CAMEL-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-21502: - Fix Version/s: 4.10.0 > camel-langchain4j-tools: fix incorrect documentation > > > Key: CAMEL-21502 > URL: https://issues.apache.org/jira/browse/CAMEL-21502 > Project: Camel > Issue Type: Task > Components: camel-langchain4j-tools >Affects Versions: 4.8.1, 4.9.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.8.3, 4.10.0 > > > Some bits of the documentation still refer to "langchain4j-chat". These > should be fixed to use the tools component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21502) camel-langchain4j-tools: fix incorrect documentation
[ https://issues.apache.org/jira/browse/CAMEL-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-21502: - Affects Version/s: 4.9.0 > camel-langchain4j-tools: fix incorrect documentation > > > Key: CAMEL-21502 > URL: https://issues.apache.org/jira/browse/CAMEL-21502 > Project: Camel > Issue Type: Task > Components: camel-langchain4j-tools >Affects Versions: 4.8.1, 4.9.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.8.3 > > > Some bits of the documentation still refer to "langchain4j-chat". These > should be fixed to use the tools component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21503) camel-langchain4j-chat: remove function calling
[ https://issues.apache.org/jira/browse/CAMEL-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-21503: - Affects Version/s: 4.9.0 > camel-langchain4j-chat: remove function calling > --- > > Key: CAMEL-21503 > URL: https://issues.apache.org/jira/browse/CAMEL-21503 > Project: Camel > Issue Type: Task >Affects Versions: 4.9.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > > Function calling features were moved to the tools component as part of > CAMEL-21153. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21486) camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000
[ https://issues.apache.org/jira/browse/CAMEL-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902575#comment-17902575 ] Claus Ibsen commented on CAMEL-21486: - Would it be possible to do a new fix just for 4.8.x that ensures that this bug is fixed (if the bug is in fact on 4.8.x at all). Without backporting cleanly or having to do other backports from traits etc. If not then we can also say that this is only being fixed from 4.9 onwards. > camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000 > - > > Key: CAMEL-21486 > URL: https://issues.apache.org/jira/browse/CAMEL-21486 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.1 >Reporter: Andrea Cosentino >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.3, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21501) Saxon xslt concat does not work correctly on whitespaces
[
https://issues.apache.org/jira/browse/CAMEL-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21501.
-
Resolution: Invalid
This is not a Camel bug. We regular upgrade dependencies when they are released
on maven central.
> Saxon xslt concat does not work correctly on whitespaces
>
>
> Key: CAMEL-21501
> URL: https://issues.apache.org/jira/browse/CAMEL-21501
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.4, 4.8.1
>Reporter: Nathan
>Priority: Minor
>
> There is a bug in saxon HE starting from saxon HE 10. The xslt concat
> function with multi parameters: concat(s,s,...) does not correctly concat
> consecutive whitespaces.
> concat('x', ' ', ' ', 'y') gives 'x y', it removes one of the whitespaces.
> This has been documented in https://saxonica.plan.io/issues/6494
> There is no release in Saxon HE yet, but once it's available a dependency
> upgrade should be done.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21502) camel-langchain4j-tools: fix incorrect documentation
Otavio Rodolfo Piske created CAMEL-21502: Summary: camel-langchain4j-tools: fix incorrect documentation Key: CAMEL-21502 URL: https://issues.apache.org/jira/browse/CAMEL-21502 Project: Camel Issue Type: Task Components: camel-langchain4j-tools Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Some bits of the documentation still refer to "langchain4j-chat". These should be fixed to use the tools component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21503) camel-langchain4j-chat: remove function calling
Otavio Rodolfo Piske created CAMEL-21503: Summary: camel-langchain4j-chat: remove function calling Key: CAMEL-21503 URL: https://issues.apache.org/jira/browse/CAMEL-21503 Project: Camel Issue Type: Task Reporter: Otavio Rodolfo Piske Function calling features were moved to the tools component as part of CAMEL-21153. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21502) camel-langchain4j-tools: fix incorrect documentation
[ https://issues.apache.org/jira/browse/CAMEL-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-21502: - Fix Version/s: 4.8.3 > camel-langchain4j-tools: fix incorrect documentation > > > Key: CAMEL-21502 > URL: https://issues.apache.org/jira/browse/CAMEL-21502 > Project: Camel > Issue Type: Task > Components: camel-langchain4j-tools >Affects Versions: 4.8.1 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.8.3 > > > Some bits of the documentation still refer to "langchain4j-chat". These > should be fixed to use the tools component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21464) camel k8s run ... may lead to exec format error
[
https://issues.apache.org/jira/browse/CAMEL-21464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler resolved CAMEL-21464.
Resolution: Fixed
Done
> camel k8s run ... may lead to exec format error
> ---
>
> Key: CAMEL-21464
> URL: https://issues.apache.org/jira/browse/CAMEL-21464
> Project: Camel
> Issue Type: Task
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
>
> {code}
> camel kubernetes run timer-log-route.yaml --logs \
>--gav=examples:timer-log:1.0.0 \
>--image-registry k3s-registry:30443 \
> --trait container.image-pull-policy=Always \
> --trait container.image-push=true \
> --trait service.type=NodePort \
>--runtime=camel-main
> ...
> Run: kubectl get pod -l app.kubernetes.io/name=timer-log
> Kubernetes v1.30 https://207.244.234.85:6443/
> Pod 'timer-log-774df9dd8d-wxd9s' in phase Running
> exec /opt/java/openjdk/bin/java: exec format error
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21418) camel-rest - Client request validation and multiple values in Accept header
[
https://issues.apache.org/jira/browse/CAMEL-21418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21418.
-
Resolution: Fixed
> camel-rest - Client request validation and multiple values in Accept header
> ---
>
> Key: CAMEL-21418
> URL: https://issues.apache.org/jira/browse/CAMEL-21418
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.8.1
>Reporter: Olivier Jacquemart
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.8.3, 4.10.0
>
>
> I have a problem regarding a rest route and a client sending multiple values
> in the Accept header. The route has the client request validation enabled.
> {code:java}
> # succeeds
> $ curl -v -H "Accept: application/json" localhost:8080/api/hello
> {"message":"hello world"}
> # fails
> $ curl -v -H "Accept: application/xml, application/json"
> localhost:8080/api/hello
> Response status is https://http.cat/406
> {code}
> After a quick debug, I ended up in the [RestUtil
> |https://github.com/apache/camel/blob/main/core/camel-support/src/main/java/org/apache/camel/support/http/RestUtil.java]
> class that returns false by default. It considers the accept header like
> invalid then and gives the 406.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21464) camel k8s run ... may lead to exec format error
[
https://issues.apache.org/jira/browse/CAMEL-21464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-21464:
---
Fix Version/s: 4.9.0
> camel k8s run ... may lead to exec format error
> ---
>
> Key: CAMEL-21464
> URL: https://issues.apache.org/jira/browse/CAMEL-21464
> Project: Camel
> Issue Type: Task
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.9.0
>
>
> {code}
> camel kubernetes run timer-log-route.yaml --logs \
>--gav=examples:timer-log:1.0.0 \
>--image-registry k3s-registry:30443 \
> --trait container.image-pull-policy=Always \
> --trait container.image-push=true \
> --trait service.type=NodePort \
>--runtime=camel-main
> ...
> Run: kubectl get pod -l app.kubernetes.io/name=timer-log
> Kubernetes v1.30 https://207.244.234.85:6443/
> Pod 'timer-log-774df9dd8d-wxd9s' in phase Running
> exec /opt/java/openjdk/bin/java: exec format error
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21504) camel-spring-boot - MicrometerTagsAutoConfiguration class puts http method in uri tag
[
https://issues.apache.org/jira/browse/CAMEL-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902587#comment-17902587
]
Nikola Dangubic commented on CAMEL-21504:
-
Understandable for full uris. I would expect behaviour like commented in
https://issues.apache.org/jira/browse/CAMEL-19136
> camel-spring-boot - MicrometerTagsAutoConfiguration class puts http method in
> uri tag
> -
>
> Key: CAMEL-21504
> URL: https://issues.apache.org/jira/browse/CAMEL-21504
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
>Affects Versions: 4.4.4, 4.8.1
>Reporter: Nikola Dangubic
>Priority: Minor
>
> [MicrometerTagsAutoConfiguration|https://github.com/apache/camel-spring-boot/blob/cf415a2c4dc1e6f7b14412d641e4fefd42786081/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java]
> probably has copy/paste error where instead of uri it puts http method in
> map for metrics
> {code:java}
> return KeyValue.of("uri", context.getCarrier().getMethod()); {code}
> and output looks like
> {code:java}
> # TYPE http_server_requests_active_seconds summary
> http_server_requests_active_seconds_count{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0
> http_server_requests_active_seconds_sum{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0.0 {code}
> One would expect uri value for uri tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21486) camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000
[ https://issues.apache.org/jira/browse/CAMEL-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902650#comment-17902650 ] Gaelle Fournier commented on CAMEL-21486: - I think it would be a good idea to backport the new Trait model to 4.8.x for the next 4.8.3. As [~tdiesler] indicates it will be recurring for bugfixes. BTW the original work was this https://issues.apache.org/jira/browse/CAMEL-21152, but having a the most recent compatible version would probably be better. Except for removing unused parameters and adding some missing functionalities I haven't been doing any big refactoring on the Trait to avoid any issue for backport. > camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000 > - > > Key: CAMEL-21486 > URL: https://issues.apache.org/jira/browse/CAMEL-21486 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.1 >Reporter: Andrea Cosentino >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.3, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21507) Camel-Jbang Kubernetes Plugin: Use new Trait model
Gaelle Fournier created CAMEL-21507: --- Summary: Camel-Jbang Kubernetes Plugin: Use new Trait model Key: CAMEL-21507 URL: https://issues.apache.org/jira/browse/CAMEL-21507 Project: Camel Issue Type: Improvement Components: camel-jbang Affects Versions: 4.8.2 Reporter: Gaelle Fournier Fix For: 4.8.3 To avoid maintenance effort for camel-jbang kubernetes plugib on LTS 4.8.x, the current Trait model needs to be backported on 4.8.x. This means any work from these issues compatible with 4.8.x: * https://issues.apache.org/jira/browse/CAMEL-21152 * https://issues.apache.org/jira/browse/CAMEL-21278 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21467) 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-21467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902547#comment-17902547 ] Jannik Schmeier commented on CAMEL-21467: - No issues with the snapshot version since Friday. > Simple expressions execute forever. Thread is RUNNABLE for ever. Issue > appears with bean expressions inside simple expressions on SimpleLRUCache > > > Key: CAMEL-21467 > URL: https://issues.apache.org/jira/browse/CAMEL-21467 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 4.8.1 >Reporter: Jannik Schmeier >Assignee: Nicolas Filotto >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > Similar to CAMEL-21432, occasionally my camel route gets stuck on > SimpleLRUCache. > The thread dump suggests, that this has to do with simple and bean > expressions. I've had two encounters with this issue in two different > applications: > *First encounter:* > "Camel (camel-1) thread #2 - JmsConsumer[]" - Thread t@58 > java.lang.Thread.State: RUNNABLE > at > org.apache.camel.support.cache.SimpleLRUCache$OperationContext.close(SimpleLRUCache.java:318) > at > org.apache.camel.support.cache.SimpleLRUCache.put(SimpleLRUCache.java:106) > 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.invokeOgnlMethod(BeanExpression.java:435) > at > org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:218) > at > org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:232) > at > org.apache.camel.language.simple.SimpleExpressionBuilder$KeyedOgnlExpressionAdapter.evaluate(SimpleExpressionBuilder.java:1253) > at > org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45) > at > org.apache.camel.model.language.ExpressionDefinition.evaluate(ExpressionDefinition.java:252) > at > org.apache.camel.support.builder.ValueBuilder.evaluate(ValueBuilder.java:55) > at > org.apache.camel.support.builder.BinaryPredicateSupport.matchesReturningFailureMessage(BinaryPredicateSupport.java:67) > at > org.apache.camel.support.builder.BinaryPredicateSupport.matches(BinaryPredicateSupport.java:56) > at > org.apache.camel.processor.FilterProcessor.matches(FilterProcessor.java:89) > at > org.apache.camel.processor.FilterProcessor.process(FilterProcessor.java:72) > 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.spring.spi.TransactionErrorHandler.processByErrorHandler(TransactionErrorHandler.java:244) > at > org.apache.camel.spring.spi.TransactionErrorHandler.process(TransactionErrorHandler.java:119) > at > org.apache.camel.spring.spi.TransactionErrorHandler.process(TransactionErrorHandler.java:132)
[jira] [Created] (CAMEL-21501) Saxon xslt concat does not work correctly on whitespaces
Nathan created CAMEL-21501:
--
Summary: Saxon xslt concat does not work correctly on whitespaces
Key: CAMEL-21501
URL: https://issues.apache.org/jira/browse/CAMEL-21501
Project: Camel
Issue Type: Bug
Components: camel-saxon
Affects Versions: 4.8.1, 4.4.4
Reporter: Nathan
There is a bug in saxon HE starting from saxon HE 10. The xslt concat function
with multi parameters: concat(s,s,...) does not correctly concat consecutive
whitespaces.
concat('x', ' ', ' ', 'y') gives 'x y', it removes one of the whitespaces.
This has been documented in https://saxonica.plan.io/issues/6494
There is no release in Saxon HE yet, but once it's available a dependency
upgrade should be done.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21467) 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-21467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902572#comment-17902572 ] Nicolas Filotto commented on CAMEL-21467: - Thx for the feedback, let us know if it is still good after a week or more. But please note that since versions 4.8.2 and 4.9 are both under vote, if it happens again, you will need to create another ticket > Simple expressions execute forever. Thread is RUNNABLE for ever. Issue > appears with bean expressions inside simple expressions on SimpleLRUCache > > > Key: CAMEL-21467 > URL: https://issues.apache.org/jira/browse/CAMEL-21467 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 4.8.1 >Reporter: Jannik Schmeier >Assignee: Nicolas Filotto >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > Similar to CAMEL-21432, occasionally my camel route gets stuck on > SimpleLRUCache. > The thread dump suggests, that this has to do with simple and bean > expressions. I've had two encounters with this issue in two different > applications: > *First encounter:* > "Camel (camel-1) thread #2 - JmsConsumer[]" - Thread t@58 > java.lang.Thread.State: RUNNABLE > at > org.apache.camel.support.cache.SimpleLRUCache$OperationContext.close(SimpleLRUCache.java:318) > at > org.apache.camel.support.cache.SimpleLRUCache.put(SimpleLRUCache.java:106) > 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.invokeOgnlMethod(BeanExpression.java:435) > at > org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:218) > at > org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:232) > at > org.apache.camel.language.simple.SimpleExpressionBuilder$KeyedOgnlExpressionAdapter.evaluate(SimpleExpressionBuilder.java:1253) > at > org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45) > at > org.apache.camel.model.language.ExpressionDefinition.evaluate(ExpressionDefinition.java:252) > at > org.apache.camel.support.builder.ValueBuilder.evaluate(ValueBuilder.java:55) > at > org.apache.camel.support.builder.BinaryPredicateSupport.matchesReturningFailureMessage(BinaryPredicateSupport.java:67) > at > org.apache.camel.support.builder.BinaryPredicateSupport.matches(BinaryPredicateSupport.java:56) > at > org.apache.camel.processor.FilterProcessor.matches(FilterProcessor.java:89) > at > org.apache.camel.processor.FilterProcessor.process(FilterProcessor.java:72) > 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.spring.spi.TransactionErrorHandler.processByErrorHandler(TransactionErrorHandler.java:244) > at > org.apache.camel.spring.spi.TransactionE
[jira] [Updated] (CAMEL-21504) MicrometerTagsAutoConfiguration class puts http method in uri tag
[
https://issues.apache.org/jira/browse/CAMEL-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikola Dangubic updated CAMEL-21504:
Summary: MicrometerTagsAutoConfiguration class puts http method in uri tag
(was: MicrometerTagsAutoConfiguration class puts method instead of uri in
metrics)
> MicrometerTagsAutoConfiguration class puts http method in uri tag
> -
>
> Key: CAMEL-21504
> URL: https://issues.apache.org/jira/browse/CAMEL-21504
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
>Affects Versions: 4.4.4, 4.8.1
>Reporter: Nikola Dangubic
>Priority: Minor
>
> [MicrometerTagsAutoConfiguration|https://github.com/apache/camel-spring-boot/blob/cf415a2c4dc1e6f7b14412d641e4fefd42786081/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java]
> probably has copy/paste error where instead of uri it puts http method in
> map for metrics
> {code:java}
> return KeyValue.of("uri", context.getCarrier().getMethod()); {code}
> and output looks like
> {code:java}
> # TYPE http_server_requests_active_seconds summary
> http_server_requests_active_seconds_count{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0
> http_server_requests_active_seconds_sum{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0.0 {code}
> One would expect uri value for uri tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21504) MicrometerTagsAutoConfiguration class puts http method in uri tag
[
https://issues.apache.org/jira/browse/CAMEL-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902583#comment-17902583
]
Claus Ibsen commented on CAMEL-21504:
-
You cannot have full uris as they can be dynamic and cause too many unique
values for the observability tools. So it has to be limited - but could
possible be the uri base path.
> MicrometerTagsAutoConfiguration class puts http method in uri tag
> -
>
> Key: CAMEL-21504
> URL: https://issues.apache.org/jira/browse/CAMEL-21504
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
>Affects Versions: 4.4.4, 4.8.1
>Reporter: Nikola Dangubic
>Priority: Minor
>
> [MicrometerTagsAutoConfiguration|https://github.com/apache/camel-spring-boot/blob/cf415a2c4dc1e6f7b14412d641e4fefd42786081/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java]
> probably has copy/paste error where instead of uri it puts http method in
> map for metrics
> {code:java}
> return KeyValue.of("uri", context.getCarrier().getMethod()); {code}
> and output looks like
> {code:java}
> # TYPE http_server_requests_active_seconds summary
> http_server_requests_active_seconds_count{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0
> http_server_requests_active_seconds_sum{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0.0 {code}
> One would expect uri value for uri tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21504) camel-spring-boot - MicrometerTagsAutoConfiguration class puts http method in uri tag
[
https://issues.apache.org/jira/browse/CAMEL-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21504:
Summary: camel-spring-boot - MicrometerTagsAutoConfiguration class puts
http method in uri tag (was: MicrometerTagsAutoConfiguration class puts http
method in uri tag)
> camel-spring-boot - MicrometerTagsAutoConfiguration class puts http method in
> uri tag
> -
>
> Key: CAMEL-21504
> URL: https://issues.apache.org/jira/browse/CAMEL-21504
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
>Affects Versions: 4.4.4, 4.8.1
>Reporter: Nikola Dangubic
>Priority: Minor
>
> [MicrometerTagsAutoConfiguration|https://github.com/apache/camel-spring-boot/blob/cf415a2c4dc1e6f7b14412d641e4fefd42786081/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java]
> probably has copy/paste error where instead of uri it puts http method in
> map for metrics
> {code:java}
> return KeyValue.of("uri", context.getCarrier().getMethod()); {code}
> and output looks like
> {code:java}
> # TYPE http_server_requests_active_seconds summary
> http_server_requests_active_seconds_count{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0
> http_server_requests_active_seconds_sum{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
> 0.0 {code}
> One would expect uri value for uri tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21504) MicrometerTagsAutoConfiguration class puts method instead of uri in metrics
Nikola Dangubic created CAMEL-21504:
---
Summary: MicrometerTagsAutoConfiguration class puts method instead
of uri in metrics
Key: CAMEL-21504
URL: https://issues.apache.org/jira/browse/CAMEL-21504
Project: Camel
Issue Type: Bug
Components: camel-spring-boot
Affects Versions: 4.8.1, 4.4.4
Reporter: Nikola Dangubic
[MicrometerTagsAutoConfiguration|https://github.com/apache/camel-spring-boot/blob/cf415a2c4dc1e6f7b14412d641e4fefd42786081/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java]
probably has copy/paste error where instead of uri it puts http method in map
for metrics
{code:java}
return KeyValue.of("uri", context.getCarrier().getMethod()); {code}
and output looks like
{code:java}
# TYPE http_server_requests_active_seconds summary
http_server_requests_active_seconds_count{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
0
http_server_requests_active_seconds_sum{application="test_metrics",exception="none",method="GET",outcome="SUCCESS",status="200",uri="GET"}
0.0 {code}
One would expect uri value for uri tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21500) camel-observability-services - Is missing in camel-catalog
[ https://issues.apache.org/jira/browse/CAMEL-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-21500: --- Assignee: Claus Ibsen > camel-observability-services - Is missing in camel-catalog > -- > > Key: CAMEL-21500 > URL: https://issues.apache.org/jira/browse/CAMEL-21500 > Project: Camel > Issue Type: Task > Components: camel-catalog >Affects Versions: 4.9.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.10.0 > > > Should be generated as an other kind and included in the catalog -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21508) Add a component for KServe
Tadayoshi Sato created CAMEL-21508: -- Summary: Add a component for KServe Key: CAMEL-21508 URL: https://issues.apache.org/jira/browse/CAMEL-21508 Project: Camel Issue Type: New Feature Components: camel-ai Affects Versions: 4.8.1 Reporter: Tadayoshi Sato Assignee: Tadayoshi Sato Fix For: 4.10.0 [KServe|https://kserve.github.io/website/] is a standard for serving AI models on Kubernetes. Popular model servers such as OpenVINO and Triton already support KServe, so once Camel provides a component for KServe it can immediately support multiple model servers for invoking inference with different formats of AI models on Kubernetes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21472) Opentelemetry is using the same traceId when exchange is fired from file or timer component
[
https://issues.apache.org/jira/browse/CAMEL-21472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902775#comment-17902775
]
Thomas Gantenbein commented on CAMEL-21472:
---
If you remove MDC support, doesn't that defeat one of the main purposes of
tracing, i.e. the ability to trace a particular request over several services?
If I don't have the traceId somewhere in the logs, it's hard to find a
particular trace. Moreover, unless the option `traceProcessors` is true, the
context is not passed to other threads, so even if logs were sent via a
[Opentelemetry logs
bridge|https://opentelemetry.io/docs/specs/otel/logs/#new-first-party-application-logs]
instead of using MDC, I doubt that this would work, since that bridge would
have no knowledge about the current context either if a route was using a new
thread in the middle of its execution (for example after a delay EIP).
Maybe if tracing is enabled, every processor should _always_ be intercepted so
that context can be passed?
[https://github.com/apache/camel/blob/main/components/camel-opentelemetry/src/main/java/org/apache/camel/opentelemetry/OpenTelemetryTracingStrategy.java#L45]
almost has what may be needed, but maybe this should be invoked per default so
that every processor would be wrapped at least in a
[PropagateContext|https://github.com/apache/camel/blob/main/components/camel-opentelemetry/src/main/java/org/apache/camel/opentelemetry/OpenTelemetryTracingStrategy.java#L52]?
> Opentelemetry is using the same traceId when exchange is fired from file or
> timer component
> ---
>
> Key: CAMEL-21472
> URL: https://issues.apache.org/jira/browse/CAMEL-21472
> Project: Camel
> Issue Type: Bug
> Components: camel-opentelemetry
>Affects Versions: 4.8.1
>Reporter: Thomas Gantenbein
>Assignee: Pasquale Congiusti
>Priority: Major
> Fix For: 4.8.3, 4.10.0
>
> Attachments: image-2024-11-26-09-59-35-555.png,
> image-2024-11-29-17-04-16-581.png, image-2024-11-29-17-06-26-116.png,
> image-2024-11-29-17-06-42-860.png, image-2024-11-29-17-12-49-768.png,
> image-2024-11-29-17-12-58-036.png
>
>
> *Problem*
> When using a consumer like {{timer}} or {{{}file{}}}, the traceId remains the
> same for all messages. When using a consumer like netty (or, I assume, any
> other http/tcp-based consumer), every call gets its own traceId as expected.
> See also
> https://camel.zulipchat.com/#narrow/channel/257298-camel/topic/Same.20OTEL.20trace.20for.20all.20messages.20into.20IBM.20MQ
> *Reproducer*
> [https://github.com/thomas-gantenbein-tga/camel-opentelemetry/tree/main]
> [~pcongiusti], thanks for your answer on Zulip Chat. Let me know if I should
> further explain or minimize that reproducer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
