[jira] [Comment Edited] (CAMEL-21483) Camel-upgrade-recipes: cover upgrading camel 4.8 to 4.9
[ https://issues.apache.org/jira/browse/CAMEL-21483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902285#comment-17902285 ] Jiri Ondrusek edited comment on CAMEL-21483 at 12/2/24 1:57 PM: PR with migration from 4.8 to 4.9 is prepared - [https://github.com/apache/camel-upgrade-recipes/pull/17] Once the changes are merged, we can probably release upgrade recipes 4.9.0 [~acosentino] [~davsclaus] WDYT? was (Author: jondruse): PR with migration from 4.8 to 4.9 is prepared - [https://github.com/apache/camel-upgrade-recipes/pull/17] Once the changes are merged, we can probably release upgrade recipes 4.9.0 [~acosentino] [~davsclaus] WSYT? > Camel-upgrade-recipes: cover upgrading camel 4.8 to 4.9 > --- > > Key: CAMEL-21483 > URL: https://issues.apache.org/jira/browse/CAMEL-21483 > Project: Camel > Issue Type: Task > Components: upgrade-recipes >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > Cover migrations described by [migration > guide|https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_9.adoc] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21483) Camel-upgrade-recipes: cover upgrading camel 4.8 to 4.9
[ https://issues.apache.org/jira/browse/CAMEL-21483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902285#comment-17902285 ] Jiri Ondrusek commented on CAMEL-21483: --- PR with migration from 4.8 to 4.9 is prepared - [https://github.com/apache/camel-upgrade-recipes/pull/17] Once the changes are merged, we can probably release upgrade recipes 4.9.0 [~acosentino] [~davsclaus] WSYT? > Camel-upgrade-recipes: cover upgrading camel 4.8 to 4.9 > --- > > Key: CAMEL-21483 > URL: https://issues.apache.org/jira/browse/CAMEL-21483 > Project: Camel > Issue Type: Task > Components: upgrade-recipes >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > Cover migrations described by [migration > guide|https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_9.adoc] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21497) Camel-Kubernetes: Add Configmap Dev Console
[ https://issues.apache.org/jira/browse/CAMEL-21497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21497. -- Resolution: Fixed > Camel-Kubernetes: Add Configmap Dev Console > --- > > Key: CAMEL-21497 > URL: https://issues.apache.org/jira/browse/CAMEL-21497 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21499) Error while loading Spring XML context when using MOXy as the JAXB implementation
Adriano Machado created CAMEL-21499:
---
Summary: 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
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-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:all-tabpanel
]
Claus Ibsen updated CAMEL-21495:
Priority: Minor (was: Major)
> 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] [Created] (CAMEL-21496) Camel-Azure-Key-Vault: Add Update Secret operation to Producer
Andrea Cosentino created CAMEL-21496: Summary: Camel-Azure-Key-Vault: Add Update Secret operation to Producer Key: CAMEL-21496 URL: https://issues.apache.org/jira/browse/CAMEL-21496 Project: Camel Issue Type: New Feature Components: camel-azure Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21495) camel-quarkus: REST route inlining works incorrectly when testing
Sami Peltola created CAMEL-21495:
Summary: 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
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] [Created] (CAMEL-21497) Camel-Kubernetes: Add Configmap Dev Console
Andrea Cosentino created CAMEL-21497: Summary: Camel-Kubernetes: Add Configmap Dev Console Key: CAMEL-21497 URL: https://issues.apache.org/jira/browse/CAMEL-21497 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21463) Camel-jbang while running the process in background unable to access log if the process start fails with errors
[ https://issues.apache.org/jira/browse/CAMEL-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21463. - Resolution: Fixed > Camel-jbang while running the process in background unable to access log if > the process start fails with errors > --- > > Key: CAMEL-21463 > URL: https://issues.apache.org/jira/browse/CAMEL-21463 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.0, 4.8.1 >Reporter: Vidhya Sagar Jeevendran >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.10.0 > > > When I run camel integrations with jbang in background and later fetch log > using "camel log" I am able to access the log only when the process has > started successfully. But when it fails with some error, the log is empty and > I am unable to find the failure reason. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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 updated CAMEL-21418:
Fix Version/s: 4.8.3
4.10.0
> 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] [Created] (CAMEL-21498) RemoteFileConfiguration
John Yeary created CAMEL-21498: -- Summary: RemoteFileConfiguration Key: CAMEL-21498 URL: https://issues.apache.org/jira/browse/CAMEL-21498 Project: Camel Issue Type: Bug Components: camel-ftp, camel-sftp Affects Versions: 4.8.1, 4.7.0 Reporter: John Yeary The `RemoteFileConfiguration` contains a parameter for `soTimeout` with a default value of 300,000 milliseconds. This translates to 5,000 minutes. I believe that the default value should be 30,000 milliseconds or 5 minutes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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 updated CAMEL-21418:
Affects Version/s: 4.9.0
> 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, 4.9.0
>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] [Assigned] (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 reassigned CAMEL-21418:
---
Assignee: Claus Ibsen
> 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
>
> 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-21498) RemoteFileConfiguration
[ https://issues.apache.org/jira/browse/CAMEL-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yeary updated CAMEL-21498: --- Description: The RemoteFileConfiguration contains a parameter for soTimeout with a default value of 300,000 milliseconds. This translates to 5,000 minutes. I believe that the default value should be 30,000 milliseconds or 5 minutes. (was: The `RemoteFileConfiguration` contains a parameter for `soTimeout` with a default value of 300,000 milliseconds. This translates to 5,000 minutes. I believe that the default value should be 30,000 milliseconds or 5 minutes.) > RemoteFileConfiguration > --- > > Key: CAMEL-21498 > URL: https://issues.apache.org/jira/browse/CAMEL-21498 > Project: Camel > Issue Type: Bug > Components: camel-ftp, camel-sftp >Affects Versions: 4.7.0, 4.8.1 >Reporter: John Yeary >Priority: Trivial > > The RemoteFileConfiguration contains a parameter for soTimeout with a default > value of 300,000 milliseconds. This translates to 5,000 minutes. I believe > that the default value should be 30,000 milliseconds or 5 minutes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21483) Camel-upgrade-recipes: cover upgrading camel 4.8 to 4.9
[ https://issues.apache.org/jira/browse/CAMEL-21483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902291#comment-17902291 ] Andrea Cosentino commented on CAMEL-21483: -- It's good from my pov. > Camel-upgrade-recipes: cover upgrading camel 4.8 to 4.9 > --- > > Key: CAMEL-21483 > URL: https://issues.apache.org/jira/browse/CAMEL-21483 > Project: Camel > Issue Type: Task > Components: upgrade-recipes >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > Cover migrations described by [migration > guide|https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_9.adoc] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-21498) RemoteFileConfiguration
[ https://issues.apache.org/jira/browse/CAMEL-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yeary closed CAMEL-21498. -- Resolution: Fixed Wrong conversion from milliseconds. > RemoteFileConfiguration > --- > > Key: CAMEL-21498 > URL: https://issues.apache.org/jira/browse/CAMEL-21498 > Project: Camel > Issue Type: Bug > Components: camel-ftp, camel-sftp >Affects Versions: 4.7.0, 4.8.1 >Reporter: John Yeary >Priority: Trivial > > The RemoteFileConfiguration contains a parameter for soTimeout with a default > value of 300,000 milliseconds. This translates to 5,000 minutes. I believe > that the default value should be 30,000 milliseconds or 5 minutes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-17881) TLS for MLLP Component
[ https://issues.apache.org/jira/browse/CAMEL-17881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17881: Fix Version/s: 4.x (was: Future) > TLS for MLLP Component > -- > > Key: CAMEL-17881 > URL: https://issues.apache.org/jira/browse/CAMEL-17881 > Project: Camel > Issue Type: New Feature > Components: camel-mllp >Reporter: Peter Palaga >Priority: Minor > Fix For: 4.x > > > There is no single occurrence of TLS or SSL on the MLLP component page > https://camel.apache.org/components/3.16.x/mllp-component.html > So I assume it is currently not possible to activate TLS for MLLP > communication. > Would it please be possibly to add this functionality? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-17881) TLS for MLLP Component
[ https://issues.apache.org/jira/browse/CAMEL-17881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902335#comment-17902335 ] Claus Ibsen commented on CAMEL-17881: - Thanks Anders > TLS for MLLP Component > -- > > Key: CAMEL-17881 > URL: https://issues.apache.org/jira/browse/CAMEL-17881 > Project: Camel > Issue Type: New Feature > Components: camel-mllp >Reporter: Peter Palaga >Priority: Minor > Fix For: Future > > > There is no single occurrence of TLS or SSL on the MLLP component page > https://camel.apache.org/components/3.16.x/mllp-component.html > So I assume it is currently not possible to activate TLS for MLLP > communication. > Would it please be possibly to add this functionality? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17902312#comment-17902312
]
Claus Ibsen commented on CAMEL-21418:
-
Thanks I found a way to reproduce this and have a fix on the way
> 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-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:all-tabpanel
]
Claus Ibsen updated CAMEL-21499:
Priority: Minor (was: Major)
> 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] [Created] (CAMEL-21500) camel-observability-services - Is missing in camel-catalog
Claus Ibsen created CAMEL-21500: --- Summary: 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 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] [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=17902524#comment-17902524
]
Claus Ibsen commented on CAMEL-21499:
-
What is MOXy
> 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: Major
>
> 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)
