[jira] [Commented] (CAMEL-19985) camel-smooks - Add component for Smooks for EDI data mapping
[ https://issues.apache.org/jira/browse/CAMEL-19985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847671#comment-17847671 ] Claus Ibsen commented on CAMEL-19985: - https://github.com/smooks/smooks-camel-cartridge/issues/211 > camel-smooks - Add component for Smooks for EDI data mapping > > > Key: CAMEL-19985 > URL: https://issues.apache.org/jira/browse/CAMEL-19985 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 4.x > > > This project is now ASF2 licensed > https://github.com/smooks/smooks > We used to have a camel-smooks component (camel-extra) in v1 many years ago. > We should add this component again, so users can use smooks for EDI data > mapping -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18597) Make Circuit Breakers and friends observable
[ https://issues.apache.org/jira/browse/CAMEL-18597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18597: Fix Version/s: Future > Make Circuit Breakers and friends observable > > > Key: CAMEL-18597 > URL: https://issues.apache.org/jira/browse/CAMEL-18597 > Project: Camel > Issue Type: New Feature > Components: camel-micrometer >Reporter: Marco Bungart >Priority: Minor > Fix For: Future > > > I would like to be able to monitor the state of my Circuit Breakers, as well > as related elements, e.g. ThrottlingExceptionRoutePolicy. > Thus, the state of such components should be exported in a standardized > manner (e.g. through micrometer), so I can automate monitoring and altering. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18383) camel-platform-http-vertx: Add option to run route processing on IO threads
[ https://issues.apache.org/jira/browse/CAMEL-18383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847655#comment-17847655 ] Claus Ibsen commented on CAMEL-18383: - Hmm I wonder if you want to do this per route, as setting this globally only would be to coarse grained from platform-http:foo?blocking=false from platform-http:bar > camel-platform-http-vertx: Add option to run route processing on IO threads > --- > > Key: CAMEL-18383 > URL: https://issues.apache.org/jira/browse/CAMEL-18383 > Project: Camel > Issue Type: Improvement > Components: camel-platform-http-vertx >Reporter: James Netherton >Assignee: James Netherton >Priority: Major > Fix For: 4.x > > > Some more information in this issue: > https://github.com/apache/camel-quarkus/issues/3888 > There may be cases where you are not going to block the Vert.x event loop in > the Camel routing. Therefore, it may be desirable to not do this 'execute > blocking' logic: > https://github.com/apache/camel/blob/main/components/camel-platform-http-vertx/src/main/java/org/apache/camel/component/platform/http/vertx/VertxPlatformHttpConsumer.java#L168-L221 > And instead run the AsyncProcessor as per normal on an IO thread. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18280) Reuse AWS localstack docker image
[ https://issues.apache.org/jira/browse/CAMEL-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847654#comment-17847654 ] Claus Ibsen commented on CAMEL-18280: - Is this still the situation or does it run faster now ? > Reuse AWS localstack docker image > - > > Key: CAMEL-18280 > URL: https://issues.apache.org/jira/browse/CAMEL-18280 > Project: Camel > Issue Type: Improvement > Components: tests >Reporter: Federico Mariani >Priority: Minor > Labels: easy, help-wanted > Fix For: 4.x > > > AWS IT tests execution is slow mostly due to localstack docker image > restarts, can the docker image be reused via testcontainer? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17753) FailOverLoadBalancer does not Load Balance when sticky flag is set to true.
[ https://issues.apache.org/jira/browse/CAMEL-17753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17753. - Resolution: Won't Fix sticky will keep using the same last known good > FailOverLoadBalancer does not Load Balance when sticky flag is set to true. > --- > > Key: CAMEL-17753 > URL: https://issues.apache.org/jira/browse/CAMEL-17753 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 3.14.1 >Reporter: Vincenzo Galluccio >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17635) camel-yaml-dsl - Configuring bean properties should use key/value style
[ https://issues.apache.org/jira/browse/CAMEL-17635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17635. - Resolution: Won't Fix > camel-yaml-dsl - Configuring bean properties should use key/value style > --- > > Key: CAMEL-17635 > URL: https://issues.apache.org/jira/browse/CAMEL-17635 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Reporter: Claus Ibsen >Assignee: Radovan Netuka >Priority: Major > Fix For: Future > > > Yaml DSL has special beans configuration > https://camel.apache.org/components/next/others/yaml-dsl.html#_defining_beans > But the Camel DSL uses key/value style to be consistent across the DSLs (XML, > Java etc) in the route template locale bean and other places > Using array with key/value also makes this much easier for tooling as the XML > XSD and JSon Schema contract can know about this - otherwise its just > "object" which can be anything. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-15538) Provide a "Qiskit IBM Quantum Provider" Connector
[ https://issues.apache.org/jira/browse/CAMEL-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-15538. - Resolution: Won't Fix > Provide a "Qiskit IBM Quantum Provider" Connector > - > > Key: CAMEL-15538 > URL: https://issues.apache.org/jira/browse/CAMEL-15538 > Project: Camel > Issue Type: New Feature >Reporter: Aurélien Pupier >Priority: Minor > > it will allow to use computing power of a Quantum computer. > - to launch job on a Quantum Computer > - to listen to result from the job on a Quantum computer > https://qiskit.org/documentation/apidoc/ibmq-provider.html > available library is written in Python so migth be quite some work > https://github.com/Qiskit/qiskit-ibmq-provider > or maybe it can be rewritten using directly the REST API for IBM Quantum > https://api.quantum-computing.ibm.com/v2/documentation.html?_ga=2.200951015.870923672.1604673144-1500770967.1598614684 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-14381) create a camel-mutiny component
[
https://issues.apache.org/jira/browse/CAMEL-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-14381.
-
Resolution: Information Provided
> create a camel-mutiny component
> ---
>
> Key: CAMEL-14381
> URL: https://issues.apache.org/jira/browse/CAMEL-14381
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: Future
>
>
> We should create a mutiny component, similar to camel-reactive-streams
> https://github.com/smallrye/smallrye-mutiny
> {code:java}
> CamelMutiny.on(context)
> .toMulti(servicenow().table("incident").max(100))
> .then(m -> doSomething(m))
> .await().indefinitely();
> {code}
> In Quarkus, we can nicely integrate camel into reactive messaging, like:
> {code:java}
> @Inject
> CamelMutiny mutiny;
> @Outgoing
> Multi fromEndpoint() {
> return mutiny.toMulti(servicenow().table("incident").max(100));
> }
> @Outgoing
> Multi fromEndpointURI() {
> return mutiny.toMulti("servicenow?table=incident");
> }
> @Incoming
> void toEndpoint(Multi items) {
> return mutiny.subscribeTo(items)
> .with(servicenow().table("incident").max(100).async());
> }
> @Incoming
> void toEndpointURI(Multi items) {
> return mutiny.subscribeTo(items)
> .with(s"servicenow?table=incident");
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-14381) create a camel-mutiny component
[
https://issues.apache.org/jira/browse/CAMEL-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847640#comment-17847640
]
Claus Ibsen commented on CAMEL-14381:
-
There is
https://smallrye.io/smallrye-reactive-messaging/smallrye-reactive-messaging/3.4/camel/camel.html
> create a camel-mutiny component
> ---
>
> Key: CAMEL-14381
> URL: https://issues.apache.org/jira/browse/CAMEL-14381
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: Future
>
>
> We should create a mutiny component, similar to camel-reactive-streams
> https://github.com/smallrye/smallrye-mutiny
> {code:java}
> CamelMutiny.on(context)
> .toMulti(servicenow().table("incident").max(100))
> .then(m -> doSomething(m))
> .await().indefinitely();
> {code}
> In Quarkus, we can nicely integrate camel into reactive messaging, like:
> {code:java}
> @Inject
> CamelMutiny mutiny;
> @Outgoing
> Multi fromEndpoint() {
> return mutiny.toMulti(servicenow().table("incident").max(100));
> }
> @Outgoing
> Multi fromEndpointURI() {
> return mutiny.toMulti("servicenow?table=incident");
> }
> @Incoming
> void toEndpoint(Multi items) {
> return mutiny.subscribeTo(items)
> .with(servicenow().table("incident").max(100).async());
> }
> @Incoming
> void toEndpointURI(Multi items) {
> return mutiny.subscribeTo(items)
> .with(s"servicenow?table=incident");
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20775) camel-hashicorp-vault - configure multiple engines
[
https://issues.apache.org/jira/browse/CAMEL-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20775:
Fix Version/s: 4.x
> camel-hashicorp-vault - configure multiple engines
> --
>
> Key: CAMEL-20775
> URL: https://issues.apache.org/jira/browse/CAMEL-20775
> Project: Camel
> Issue Type: Improvement
>Reporter: Federico Mariani
>Priority: Major
> Fix For: 4.x
>
>
> Currently, only one engine can be (easily) configured in the
> camel-hashicorp-vault component.
> It would be nice to configure the engine ala
> \{{hashicorp:engine:path/to/secret}} so that multiple engines can be used in
> the same application. for example, key/value store engine and pki store
> engine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20775) camel-hashicorp-vault - configure multiple engines
[
https://issues.apache.org/jira/browse/CAMEL-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20775:
Component/s: camel-hashicorp-vault
> camel-hashicorp-vault - configure multiple engines
> --
>
> Key: CAMEL-20775
> URL: https://issues.apache.org/jira/browse/CAMEL-20775
> Project: Camel
> Issue Type: Improvement
> Components: camel-hashicorp-vault
>Reporter: Federico Mariani
>Priority: Major
> Fix For: 4.x
>
>
> Currently, only one engine can be (easily) configured in the
> camel-hashicorp-vault component.
> It would be nice to configure the engine ala
> \{{hashicorp:engine:path/to/secret}} so that multiple engines can be used in
> the same application. for example, key/value store engine and pki store
> engine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20786) Resolve Camel Property Placeholders in properties file/system
[
https://issues.apache.org/jira/browse/CAMEL-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847639#comment-17847639
]
Claus Ibsen commented on CAMEL-20786:
-
I put together an example using base64 properties function (instead of azure)
and it works in jbang and also in CSB (see attached zip file)
> Resolve Camel Property Placeholders in properties file/system
> -
>
> Key: CAMEL-20786
> URL: https://issues.apache.org/jira/browse/CAMEL-20786
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Priority: Major
> Attachments: sb-props.zip
>
>
> It would be nice to resolve Camel Property placeholders, for example, Azure
> Vault, in application.properties files, system properties, and so on. I think
> that plain Camel, Camel Spring Boot and Camel Quarkus may benefit from it,
> for example, I'd be able to do the following, given the
> application.properties file:
> {code:java}
> mypassword={{azure:pass}}
> {code}
> at runtime, the actual password is used and resolved using the
> camel-azure-key-vault component
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20786) Resolve Camel Property Placeholders in properties file/system
[
https://issues.apache.org/jira/browse/CAMEL-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20786:
Attachment: sb-props.zip
> Resolve Camel Property Placeholders in properties file/system
> -
>
> Key: CAMEL-20786
> URL: https://issues.apache.org/jira/browse/CAMEL-20786
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Priority: Major
> Attachments: sb-props.zip
>
>
> It would be nice to resolve Camel Property placeholders, for example, Azure
> Vault, in application.properties files, system properties, and so on. I think
> that plain Camel, Camel Spring Boot and Camel Quarkus may benefit from it,
> for example, I'd be able to do the following, given the
> application.properties file:
> {code:java}
> mypassword={{azure:pass}}
> {code}
> at runtime, the actual password is used and resolved using the
> camel-azure-key-vault component
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20788) Use another protobuf-maven-plugin
Claus Ibsen created CAMEL-20788: --- Summary: Use another protobuf-maven-plugin Key: CAMEL-20788 URL: https://issues.apache.org/jira/browse/CAMEL-20788 Project: Camel Issue Type: Dependency upgrade Components: camel-salesforce Reporter: Claus Ibsen Fix For: 4.x The [https://www.xolstice.org/protobuf-maven-plugin] is not maintained anymore and last release is from 2018. We can use this instead [https://github.com/ascopes/protobuf-maven-plugin] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18740) Automatic encapsulation of outgoing invocations
[ https://issues.apache.org/jira/browse/CAMEL-18740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847561#comment-17847561 ] Claus Ibsen commented on CAMEL-18740: - We have variables now - lets use that and see how that goes before doing more bigger changes > Automatic encapsulation of outgoing invocations > --- > > Key: CAMEL-18740 > URL: https://issues.apache.org/jira/browse/CAMEL-18740 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Bruno Meseguer >Priority: Minor > Fix For: Future > > > In pursuit of better useability of Camel and future UI tooling, it would be > ideal for implementing in Camel an automatic encapsulation of in/out data > when invoking endpoints. > The following scenario is a typical processing flow in the enterprise: > 1) receive client request > 2) call system A > 3) call system B > 4) call system C > 5) compose response (A'+ B'+ C') > 6) reply to client > Camel is today 100% capable of letting the developer implement such workflow. > If the developer wants to compose a response (step 5), then the sequence of > calls above (A/B/C) require to manually keep responses in exchange > properties. It requires from the developer to be well familiar with Camel to > code the right actions. New users would find it very challenging at first to > find the right approach. > Additionally, the current Camel mechanics of handling properties/headers/body > do not provide a good enough level of support for UI tooling. A GUI user > would still require a good understanding of Camel to accomplish such workflow. > This ticket proposes to provide Camel the ability to automatically handle > external calls in such a way that response data is inmediately available for > developers to easility compose the response data. > An example Exchange structure that Camel could self-populate is the following: > (config/inputs could be defined at design time, in code or GUI) > (outputs would be resolved at runtime) > Exchange > - Consumer (1) > - configuration > - message (received) or (output) > - headers > - body > - Producer (2) > - configuration > - message (sent) or (input) > - headers > - body > - message (response) or (output) > - headers > - body > - Producer (3) > - configuration > - message (sent) or (input) > - headers > - body > - message (response) or (output) > - headers > - body > - Producer (4) > - configuration > - message (sent) or (input) > - headers > - body > - message (response) or (output) > - headers > - body > - Mapping (5) > - configuration > - message (input) > - headers > - body > - message (output) > - headers > - body > - Response to client (automatic) > In the structure above, Camel has automatically created multiple objects > inside the Exchange, where each endpoint interaction has been encapsulated. > At design time, the Camel route could provide all the metadata > (config/inputs) necessary to allow a GUI to easy present to the user > information that can be used to configure other inputs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18740) Automatic encapsulation of outgoing invocations
[ https://issues.apache.org/jira/browse/CAMEL-18740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18740. - Resolution: Information Provided > Automatic encapsulation of outgoing invocations > --- > > Key: CAMEL-18740 > URL: https://issues.apache.org/jira/browse/CAMEL-18740 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Bruno Meseguer >Priority: Minor > Fix For: Future > > > In pursuit of better useability of Camel and future UI tooling, it would be > ideal for implementing in Camel an automatic encapsulation of in/out data > when invoking endpoints. > The following scenario is a typical processing flow in the enterprise: > 1) receive client request > 2) call system A > 3) call system B > 4) call system C > 5) compose response (A'+ B'+ C') > 6) reply to client > Camel is today 100% capable of letting the developer implement such workflow. > If the developer wants to compose a response (step 5), then the sequence of > calls above (A/B/C) require to manually keep responses in exchange > properties. It requires from the developer to be well familiar with Camel to > code the right actions. New users would find it very challenging at first to > find the right approach. > Additionally, the current Camel mechanics of handling properties/headers/body > do not provide a good enough level of support for UI tooling. A GUI user > would still require a good understanding of Camel to accomplish such workflow. > This ticket proposes to provide Camel the ability to automatically handle > external calls in such a way that response data is inmediately available for > developers to easility compose the response data. > An example Exchange structure that Camel could self-populate is the following: > (config/inputs could be defined at design time, in code or GUI) > (outputs would be resolved at runtime) > Exchange > - Consumer (1) > - configuration > - message (received) or (output) > - headers > - body > - Producer (2) > - configuration > - message (sent) or (input) > - headers > - body > - message (response) or (output) > - headers > - body > - Producer (3) > - configuration > - message (sent) or (input) > - headers > - body > - message (response) or (output) > - headers > - body > - Producer (4) > - configuration > - message (sent) or (input) > - headers > - body > - message (response) or (output) > - headers > - body > - Mapping (5) > - configuration > - message (input) > - headers > - body > - message (output) > - headers > - body > - Response to client (automatic) > In the structure above, Camel has automatically created multiple objects > inside the Exchange, where each endpoint interaction has been encapsulated. > At design time, the Camel route could provide all the metadata > (config/inputs) necessary to allow a GUI to easy present to the user > information that can be used to configure other inputs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18962) camel-as2 - AS2Consumer always accepts unencrpted/unsigned data
[ https://issues.apache.org/jira/browse/CAMEL-18962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847560#comment-17847560 ] Claus Ibsen commented on CAMEL-18962: - [~jono] I wonder if top of your head can provide some feedback on this as you helped a lot with camel-as2 of late > camel-as2 - AS2Consumer always accepts unencrpted/unsigned data > --- > > Key: CAMEL-18962 > URL: https://issues.apache.org/jira/browse/CAMEL-18962 > Project: Camel > Issue Type: Improvement > Components: camel-as2 >Reporter: dennis lucero >Priority: Minor > > When setting up an AS2Cosumer (server) security is important. Thus in mind > AS2 should use encryption and signing to verify the incoming data before > processing it (or supplying the message for further processing). That assures > that the originator of the data is a trusted party. > Camel AS2 consumer accepts encrypted and signed data and at least decryption > is working. > *Problem* > The problem is that the consumer also accepts unencrypted data. So even if I > only want to receive encrpyted data from a trusted party, some third party > disguised as the trused party, could send a malicious unencrypted payload > and the server would just accept and process it. > For example sending plain data with the content type "application/edifact" is > always accepted. > *Possible solution* > The consumer should be configurable what content type is allowed. Also the > already existing producer-parameter "as2MessageStructure" may be used for > that purpose. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19253) camel-jbang - Make it easier to use JDBC datasource
[ https://issues.apache.org/jira/browse/CAMEL-19253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19253. - Fix Version/s: 4.6.0 (was: 4.x) Resolution: Fixed > camel-jbang - Make it easier to use JDBC datasource > --- > > Key: CAMEL-19253 > URL: https://issues.apache.org/jira/browse/CAMEL-19253 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > For example to configure a datasource in a .properties file in either quarkus > or spring-boot style. > https://github.com/apache/camel-k-examples/blob/main/generic-examples/databases/datasource.properties > And in plain camel-main style as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19578) Presigned upload urls in camel object storage components
[ https://issues.apache.org/jira/browse/CAMEL-19578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19578: Priority: Minor (was: Major) > Presigned upload urls in camel object storage components > > > Key: CAMEL-19578 > URL: https://issues.apache.org/jira/browse/CAMEL-19578 > Project: Camel > Issue Type: New Feature > Components: camel-aws2, camel-azure, camel-google-storage >Reporter: Hitesh C >Priority: Minor > Labels: S3, azureblob, google-cloud-storage, objectstore > Fix For: Future > > > Camel Minio has the following two operations in relation to presigned urls > * createDownloadLink > * createUploadLink > Other mentioned object storage have functionality of > * createDownloadLink > > The proposal is to add the functionality of createDownloadLink(if missing) > and createUploadLink in all the object storage components where they are > supported by the underlying libraries and rename them into a single operation > called > * createPresignedUrl > The operation configuration upload(PUT) or download(GET) can be supplied > through headers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19639) camel-etc3 - Etcd3RoutePolicyIT is failing
[ https://issues.apache.org/jira/browse/CAMEL-19639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19639. - Fix Version/s: 4.7.0 Resolution: Fixed We have upgraded to 0.8.0 and it works > camel-etc3 - Etcd3RoutePolicyIT is failing > -- > > Key: CAMEL-19639 > URL: https://issues.apache.org/jira/browse/CAMEL-19639 > Project: Camel > Issue Type: Test > Environment: [ERROR] Errors: > [ERROR] Etcd3RoutePolicyIT.testAsLeader:58 » ConditionTimeout Assertion > condition defined as a > org.apache.camel.component.etcd3.policy.Etcd3RoutePolicyIT expected: > but was: within 10 seconds. >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > [ERROR] Errors: > [ERROR] Etcd3RoutePolicyIT.testAsLeader:58 » ConditionTimeout Assertion > condition defined as a > org.apache.camel.component.etcd3.policy.Etcd3RoutePolicyIT expected: > but was: within 10 seconds. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20090) camel-zipfile - Stream close while unzipping
[
https://issues.apache.org/jira/browse/CAMEL-20090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847551#comment-17847551
]
Claus Ibsen commented on CAMEL-20090:
-
Try with 4.7 as some changes has been done internally in camel
> camel-zipfile - Stream close while unzipping
>
>
> Key: CAMEL-20090
> URL: https://issues.apache.org/jira/browse/CAMEL-20090
> Project: Camel
> Issue Type: Bug
> Components: camel-zipfile
>Affects Versions: 3.20.8
>Reporter: Raymond
>Priority: Minor
>
> As discussed on the mailing list:
> [https://lists.apache.org/thread/gkzpjsrdxwrc2jsh82vp92dzdlympjtf]
> Sometimes when unzipping a zip file I get an error:
> {code:java}
> org.apache.camel.StreamCacheException: Error during type conversion
> from type: org.apache.camel.dataformat.zipfile.ZipInputStreamWrapper
> to the required type: org.apache.camel.StreamCache with value
> org.apache.camel.dataformat.zipfile.ZipInputStreamWrapper@10538c67
> due to org.apache.camel.TypeConversionException: Error during type
> conversion from type:
> org.apache.camel.dataformat.zipfile.ZipInputStreamWrapper
> to the required type: org.apache.camel.StreamCache with value
> org.apache.camel.dataformat.zipfile.ZipInputStreamWrapper@10538c67 due
> to java.io.IOException: Stream closed {code}
> I don't know how far this is related to other issue with ZipFile:
> https://issues.apache.org/jira/browse/CAMEL-19849
> The strange thing is that is seems to work in some environments and fails in
> others.
> I tested it with Camel 3.20.8 / JDK
> For example:
> 1. Local (build from source / Windows 11) --> Works
> 2. Local (Docker image / Docker Desktop) --> Works
> 3. Local (build from source / MacOS) --> Works
> 4. AWS (Docker image running on Ubuntu) --> Fails
> I tried to copy the source of ZipFile to my own program to get some more
> information, but it seems that the error is more related to the Camel Support
> module. Nevertheless I got some more logging out of it.
> My route:
> {code:java}
>
>
>
>
>
>
> ${body}
>
>
> {code}
> The log:
> {code:java}
> 2023-11-07 17:41:41.400 ERROR 1 --- [p1242793343-101]
> o.a.d.b.e.ID_6537e1053fad4b0013000109 : Failed delivery for (MessageId:
> A531BE75947BFB1-037D on ExchangeId:
> A531BE75947BFB1-037D). Exhausted after delivery attempt: 1
> caught: org.apache.camel.StreamCacheException: Error during type conversion
> from type: org.assimbly.archive.ZipInputStreamWrapper to the required type:
> org.apache.camel.StreamCache with value
> org.assimbly.archive.ZipInputStreamWrapper@3e6184af due to
> org.apache.camel.TypeConversionException: Error during type conversion from
> type: org.assimbly.archive.ZipInputStreamWrapper to the required type:
> org.apache.camel.StreamCache withvalue
> org.assimbly.archive.ZipInputStreamWrapper@3e6184af due to
> java.io.IOException: Stream closed. Processed by failure processor:
> FatalFallbackErrorHandler[Channel[setExchangePattern76]]Message History
> ---
> Source ID
> Processor Elapsed (ms)
> xml:2 ID_6537e1053fad4b0013000109-6d
> from[direct-vm://ID_654a65bc741e4f00070007da_test_ 40341190
> xml:8 ID_6537e1053fad4b0013000109-6d
> direct-vm:ID_654a65bc741e4f00070007da_test_6df7e1e 0
> xml:5 onException138/setExchangePatt
> setExchangePattern[InOnly] 0Exchange
> ---
> Exchange[
> Id A531BE75947BFB1-037D
> Headers {Accept=*/*,
> breadcrumbId=A531BE75947BFB1-037B, CamelFileName=enrich3.txt,
> CamelRedelivered=false, CamelRedeliveryCounter=0,
> CamelServletContextPath=/regressiontests/ArchiveUnpack, Connection=close,
> Content-Length=1070, Content-Type=application/zip, Host=assimbly-test:9001,
> User-Agent=curl/7.84.0, zipFileName=enrich3.txt}
> BodyType org.assimbly.archive.ZipInputStreamWrapper
> Body [Body is instance of java.io.InputStream]
> ]Stacktrace
> ---org.apache.camel.StreamCacheException:
> Error during type conversion from type:
> org.assimbly.archive.ZipInputStreamWrapper to the required type:
>
[jira] [Resolved] (CAMEL-20095) Create a component for OpenAI
[ https://issues.apache.org/jira/browse/CAMEL-20095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20095. - Fix Version/s: 4.6.0 Resolution: Fixed Okay we have langchain component now > Create a component for OpenAI > - > > Key: CAMEL-20095 > URL: https://issues.apache.org/jira/browse/CAMEL-20095 > Project: Camel > Issue Type: New Feature >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Major > Fix For: 4.6.0 > > Attachments: telegram-openAPI.mp4 > > > Investigate on the Java library langchain4j, to create a component that can > integrate to OpenAI, HugginFace and more via langchain > > This is the link to the project : [https://github.com/langchain4j/langchain4j] > > the attached video is a first POC playing with Camel telegram and OpenAI > > [^telegram-openAPI.mp4] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20167) Provide specific title and description for the 4 CoAP components
[ https://issues.apache.org/jira/browse/CAMEL-20167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20167. - Resolution: Won't Fix > Provide specific title and description for the 4 CoAP components > - > > Key: CAMEL-20167 > URL: https://issues.apache.org/jira/browse/CAMEL-20167 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Affects Versions: 4.2.0 >Reporter: Aurélien Pupier >Priority: Minor > > currently the 4 CoAp component have the same description. And 3 of them have > the same title. it is making it not easy to differentiate at first sight in > tools providing a list of the components. > Technical: there is a single class and annotation for the 4 components (and a > single syntax, how can it be working?) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20171) camel-jetty 12, restore remove header
[ https://issues.apache.org/jira/browse/CAMEL-20171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20171: Priority: Minor (was: Major) > camel-jetty 12, restore remove header > - > > Key: CAMEL-20171 > URL: https://issues.apache.org/jira/browse/CAMEL-20171 > Project: Camel > Issue Type: Task > Components: camel-jetty >Reporter: Federico Mariani >Priority: Minor > > During the upgrade to jetty 12, the following code > https://github.com/apache/camel/pull/12208/files#diff-729ca1c0fa2bbb1790fbbbc3076620428756a4bf74f07e59d737981d9614f501R92 > was commented since out, since seems like that is not possible to remove > headers from the request anymore. > We should investigate if that piece of code is really needed, and somehow > restore or remove it -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20304) Upgrade dizitart nitrite to 4+
[ https://issues.apache.org/jira/browse/CAMEL-20304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20304. - Fix Version/s: 4.7.0 Resolution: Won't Fix > Upgrade dizitart nitrite to 4+ > --- > > Key: CAMEL-20304 > URL: https://issues.apache.org/jira/browse/CAMEL-20304 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 4.3.0 >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 4.7.0 > > > There are API break and compilation is failing when upgrading. Specific work > is needed. > see https://github.com/apache/camel/pull/1712 > Note: camel-nitrite component is missing in JIRa project -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20304) Upgrade dizitart nitrite to 4+
[ https://issues.apache.org/jira/browse/CAMEL-20304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847548#comment-17847548 ] Claus Ibsen commented on CAMEL-20304: - Okay its not worth the trouble, we are deprecating this component > Upgrade dizitart nitrite to 4+ > --- > > Key: CAMEL-20304 > URL: https://issues.apache.org/jira/browse/CAMEL-20304 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 4.3.0 >Reporter: Aurélien Pupier >Priority: Minor > > There are API break and compilation is failing when upgrading. Specific work > is needed. > see https://github.com/apache/camel/pull/1712 > Note: camel-nitrite component is missing in JIRa project -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20304) Upgrade dizitart nitrite to 4+
[ https://issues.apache.org/jira/browse/CAMEL-20304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847546#comment-17847546 ] Claus Ibsen commented on CAMEL-20304: - They do not really offer a guide to upgrade (it just says follow guide and there is no guide) https://nitrite.dizitart.com/java-sdk/getting-started/index.html#upgrade-from-3x > Upgrade dizitart nitrite to 4+ > --- > > Key: CAMEL-20304 > URL: https://issues.apache.org/jira/browse/CAMEL-20304 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 4.3.0 >Reporter: Aurélien Pupier >Priority: Minor > > There are API break and compilation is failing when upgrading. Specific work > is needed. > see https://github.com/apache/camel/pull/1712 > Note: camel-nitrite component is missing in JIRa project -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20496) kotlin-api: can't be used in DI (Spring Boot, Quarkus) based projects
[ https://issues.apache.org/jira/browse/CAMEL-20496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20496. - Resolution: Abandoned The user did not report back > kotlin-api: can't be used in DI (Spring Boot, Quarkus) based projects > - > > Key: CAMEL-20496 > URL: https://issues.apache.org/jira/browse/CAMEL-20496 > Project: Camel > Issue Type: Improvement > Components: dsl >Reporter: Vladimir Konkov >Priority: Minor > > Please provide route DSL that returns RouteBuilder that later be registered > in Camel Context. > [https://camel.apache.org/camel-quarkus/3.8.x/user-guide/defining-camel-routes.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20608) camel-jbang - Improve the docker image
[ https://issues.apache.org/jira/browse/CAMEL-20608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20608: --- Assignee: Andrea Cosentino > camel-jbang - Improve the docker image > -- > > Key: CAMEL-20608 > URL: https://issues.apache.org/jira/browse/CAMEL-20608 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > We need a 4.4.1 released image also > And lets improve what we do > https://hub.docker.com/layers/apache/camel-jbang/4.4.0/images/sha256-a5915cd14b617a42aab5504e0f644b38b0eb83458e62312efde652a45a79bddf?context=explore > 1. Upgrade to JDK 17 or 21 > 2. Upgrade to jbang 0.115.0 > 3. And to camel 4.4.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20608) camel-jbang - Improve the docker image
[ https://issues.apache.org/jira/browse/CAMEL-20608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847544#comment-17847544 ] Claus Ibsen commented on CAMEL-20608: - Andrea, I wonder if you may want to take a look at this - its okay if it goes into 4.7 onwards > camel-jbang - Improve the docker image > -- > > Key: CAMEL-20608 > URL: https://issues.apache.org/jira/browse/CAMEL-20608 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > We need a 4.4.1 released image also > And lets improve what we do > https://hub.docker.com/layers/apache/camel-jbang/4.4.0/images/sha256-a5915cd14b617a42aab5504e0f644b38b0eb83458e62312efde652a45a79bddf?context=explore > 1. Upgrade to JDK 17 or 21 > 2. Upgrade to jbang 0.115.0 > 3. And to camel 4.4.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20600) camel-activemq - Upgrade to ActiveMQ classic 6.x or create camel-activemq6
[ https://issues.apache.org/jira/browse/CAMEL-20600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847523#comment-17847523 ] Claus Ibsen commented on CAMEL-20600: - Yeah I found some time to do it - so there is a activemq6 component now in camel 4.7 onwards. > camel-activemq - Upgrade to ActiveMQ classic 6.x or create camel-activemq6 > -- > > Key: CAMEL-20600 > URL: https://issues.apache.org/jira/browse/CAMEL-20600 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-activemq >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > We test with 5.18.x which is widely in use. > The newer 6.x is JDK17 and jakarta ee compatible. > We may consider having camel-activemq6 as a component for the newer > client/broker. So we can keep the older around for the many 5.x users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20600) camel-activemq - Upgrade to ActiveMQ classic 6.x or create camel-activemq6
[ https://issues.apache.org/jira/browse/CAMEL-20600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20600. - Resolution: Fixed > camel-activemq - Upgrade to ActiveMQ classic 6.x or create camel-activemq6 > -- > > Key: CAMEL-20600 > URL: https://issues.apache.org/jira/browse/CAMEL-20600 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-activemq >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > We test with 5.18.x which is widely in use. > The newer 6.x is JDK17 and jakarta ee compatible. > We may consider having camel-activemq6 as a component for the newer > client/broker. So we can keep the older around for the many 5.x users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20600) camel-activemq - Upgrade to ActiveMQ classic 6.x or create camel-activemq6
[ https://issues.apache.org/jira/browse/CAMEL-20600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20600: Fix Version/s: 4.7.0 (was: 4.x) > camel-activemq - Upgrade to ActiveMQ classic 6.x or create camel-activemq6 > -- > > Key: CAMEL-20600 > URL: https://issues.apache.org/jira/browse/CAMEL-20600 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-activemq >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > We test with 5.18.x which is widely in use. > The newer 6.x is JDK17 and jakarta ee compatible. > We may consider having camel-activemq6 as a component for the newer > client/broker. So we can keep the older around for the many 5.x users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20600) camel-activemq - Upgrade to ActiveMQ classic 6.x or create camel-activemq6
[ https://issues.apache.org/jira/browse/CAMEL-20600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20600: --- Assignee: Claus Ibsen > camel-activemq - Upgrade to ActiveMQ classic 6.x or create camel-activemq6 > -- > > Key: CAMEL-20600 > URL: https://issues.apache.org/jira/browse/CAMEL-20600 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-activemq >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.x > > > We test with 5.18.x which is widely in use. > The newer 6.x is JDK17 and jakarta ee compatible. > We may consider having camel-activemq6 as a component for the newer > client/broker. So we can keep the older around for the many 5.x users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20744) camel-core - Error handler redelivery to support option to break out if stopping
[ https://issues.apache.org/jira/browse/CAMEL-20744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20744. - Resolution: Implemented Already implemented by the option allowRedeliveryWhileStopping > camel-core - Error handler redelivery to support option to break out if > stopping > > > Key: CAMEL-20744 > URL: https://issues.apache.org/jira/browse/CAMEL-20744 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > We can maybe add an option to error handler / onException > retryWhileStopping = true|false > This means that Camel will stop doing retries/redeliveries when CamelContext > is stopping / or that the current route is being stopped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20787) Camel-kinesis: Kinesis consumer set body type InputStream, which is not a common record type
[ https://issues.apache.org/jira/browse/CAMEL-20787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20787. - Resolution: Fixed Thanks for the PR > Camel-kinesis: Kinesis consumer set body type InputStream, which is not a > common record type > > > Key: CAMEL-20787 > URL: https://issues.apache.org/jira/browse/CAMEL-20787 > Project: Camel > Issue Type: Improvement > Components: camel-aws2-kinesis >Reporter: Fan Yang >Priority: Minor > Fix For: 4.7.0 > > > Kinesis consumer set InputStream on the body. The InputStream is not a common > record type and may not be natively supported by many data or messaging > systems. > For better compatibility, it's better to change body type to ByteArray. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20221) Provide documentation on option to create kamelet in CLI help
[ https://issues.apache.org/jira/browse/CAMEL-20221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20221. - Fix Version/s: 4.7.0 Resolution: Fixed > Provide documentation on option to create kamelet in CLI help > - > > Key: CAMEL-20221 > URL: https://issues.apache.org/jira/browse/CAMEL-20221 > Project: Camel > Issue Type: Sub-task > Components: camel-jbang >Affects Versions: 4.3.0 >Reporter: Aurélien Pupier >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20222) Provide documentation on option to create kamelet on Camel website
[ https://issues.apache.org/jira/browse/CAMEL-20222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20222. - Fix Version/s: 4.7.0 Resolution: Fixed > Provide documentation on option to create kamelet on Camel website > -- > > Key: CAMEL-20222 > URL: https://issues.apache.org/jira/browse/CAMEL-20222 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 4.3.0 >Reporter: Aurélien Pupier >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20216) Provide documentation on option to create a kamelet file through Camel Jbang init
[
https://issues.apache.org/jira/browse/CAMEL-20216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20216.
-
Fix Version/s: 4.7.0
Resolution: Fixed
> Provide documentation on option to create a kamelet file through Camel Jbang
> init
> -
>
> Key: CAMEL-20216
> URL: https://issues.apache.org/jira/browse/CAMEL-20216
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang
>Reporter: Aurélien Pupier
>Priority: Major
> Fix For: 4.7.0
>
>
> it would be convenient to provide an option of Camel Jbang init to create a
> kamelet file.
> There is currently an option --integration to create a Camel K Integration.
> So maybe providing a --kamelet which is exclusive with --integration can be
> nice.
> What would be the content for this file?
> Starting from https://github.com/apache/camel-kamelets#general-format
> example, maybe something like:
> {noformat}
> apiVersion: camel.apache.org/v1
> kind: Kamelet
> metadata:
> name: timer-source
> annotations:
> camel.apache.org/kamelet.icon: data:image/svg+xml;base64,PD94...
> camel.apache.org/provider: "My organization"
> labels:
> camel.apache.org/kamelet.type: source
> spec:
> definition:
> title: Timer Source
> description: Produces periodic events with a custom payload
> required:
> - message
> properties:
> period:
> title: Period
> description: The interval between two events in milliseconds
> type: integer
> default: 1000
> message:
> title: Message
> description: The message to generate
> type: string
> example: hello world
> types:
> out:
> mediaType: text/plain
> template:
> from:
> uri: timer:tick
> parameters:
> period: "{{period}}"
> steps:
> - set-body:
> constant: "{{message}}"
> - to: kamelet:sink
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20774) camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters
[ https://issues.apache.org/jira/browse/CAMEL-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847496#comment-17847496 ] Claus Ibsen commented on CAMEL-20774: - Yeah configuring SSL is a bit complex - and configuring via camel.ssl. properties is possible - and also if we make a bean builder as well. We may consider some kind of bean-dsl for known beans from the catalog, to generate a special fluent DSL you can use in XML/YAML as well that offer easy configuration. > camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the > object KeyStoreParameters > -- > > Key: CAMEL-20774 > URL: https://issues.apache.org/jira/browse/CAMEL-20774 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.6.0 >Reporter: Federico Mariani >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > The property keyStore (java.security.KeyStore) is present in the class > KeyStoreParameters but is missing from the XML type > tns:keyStoreParametersFactoryBean. > The java.security.KeyStore XML configuration may be needed for some use cases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20774) camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters
[ https://issues.apache.org/jira/browse/CAMEL-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20774: --- Assignee: Claus Ibsen > camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the > object KeyStoreParameters > -- > > Key: CAMEL-20774 > URL: https://issues.apache.org/jira/browse/CAMEL-20774 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.6.0 >Reporter: Federico Mariani >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > The property keyStore (java.security.KeyStore) is present in the class > KeyStoreParameters but is missing from the XML type > tns:keyStoreParametersFactoryBean. > The java.security.KeyStore XML configuration may be needed for some use cases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20787) Camel-kinesis: Kinesis consumer set body type InputStream, which is not a common record type
[ https://issues.apache.org/jira/browse/CAMEL-20787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20787: Fix Version/s: 4.7.0 > Camel-kinesis: Kinesis consumer set body type InputStream, which is not a > common record type > > > Key: CAMEL-20787 > URL: https://issues.apache.org/jira/browse/CAMEL-20787 > Project: Camel > Issue Type: Improvement > Components: camel-aws2-kinesis >Reporter: Fan Yang >Priority: Minor > Fix For: 4.7.0 > > > Kinesis consumer set InputStream on the body. The InputStream is not a common > record type and may not be natively supported by many data or messaging > systems. > For better compatibility, it's better to change body type to ByteArray. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20774) camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters
[
https://issues.apache.org/jira/browse/CAMEL-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847495#comment-17847495
]
Claus Ibsen commented on CAMEL-20774:
-
{code:xml}
cipherSuite
cipherSuitesFilterInclude
cipherSuitesFilterExclude
cipherSuite
secureSocketProtocolsFilterInclude
secureSocketProtocolsFilterExclude
cipherSuite
cipherSuitesFilterInclude
cipherSuitesFilterExclude
cipherSuite
secureSocketProtocolsFilterInclude
secureSocketProtocolsFilterExclude
cipherSuite
cipherSuitesFilterInclude
cipherSuitesFilterExclude
cipherSuite
secureSocketProtocolsFilterInclude
secureSocketProtocolsFilterExclude
{code}
> camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the
> object KeyStoreParameters
> --
>
> Key: CAMEL-20774
> URL: https://issues.apache.org/jira/browse/CAMEL-20774
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 4.6.0
>Reporter: Federico Mariani
>Priority: Minor
> Fix For: 4.x
>
>
> The property keyStore (java.security.KeyStore) is present in the class
> KeyStoreParameters but is missing from the XML type
> tns:keyStoreParametersFactoryBean.
> The java.security.KeyStore XML configuration may be needed for some use cases
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20786) Resolve Camel Property Placeholders in properties file/system
[
https://issues.apache.org/jira/browse/CAMEL-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847489#comment-17847489
]
Claus Ibsen commented on CAMEL-20786:
-
try in camel-jbang
as spring boot does its own properties loading - the same would quarkus do.
> Resolve Camel Property Placeholders in properties file/system
> -
>
> Key: CAMEL-20786
> URL: https://issues.apache.org/jira/browse/CAMEL-20786
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Priority: Major
>
> It would be nice to resolve Camel Property placeholders, for example, Azure
> Vault, in application.properties files, system properties, and so on. I think
> that plain Camel, Camel Spring Boot and Camel Quarkus may benefit from it,
> for example, I'd be able to do the following, given the
> application.properties file:
> {code:java}
> mypassword={{azure:pass}}
> {code}
> at runtime, the actual password is used and resolved using the
> camel-azure-key-vault component
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20778) Intercept created using AdviceWithRouteBuilder causes issues with error handling (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20778:
Fix Version/s: 4.4.3
> Intercept created using AdviceWithRouteBuilder causes issues with error
> handling (regression)
> -
>
> Key: CAMEL-20778
> URL: https://issues.apache.org/jira/browse/CAMEL-20778
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Denis Istomin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.3, 4.7.0
>
>
> Starting from Camel 4.0.0. It works with 3.22.x and below.
> Reproducer: [https://github.com/DenisIstomin/camel-intercept-bug]
> If route is configured like this:
> {code:java}
> public void configure() {
> onException(Exception.class)
> .log(LoggingLevel.ERROR, "handler", "called");
> from("direct:start").routeId("main-route-id")
> .doTry()
> .throwException(new Exception())
> .doCatch(Exception.class)
> .setBody(constant("expected"))
> .end();
> }
> {code}
> And then this route is adviced:
> {code:java}
> AdviceWith.adviceWith(context, "main-route-id", routeBuilder -> {
> routeBuilder.intercept().log("intercepted");
> });
> {code}
>
> Error handler will not catch an exception. Body will not be equal to
> "expected".
> XML:
> {code:xml}
> http://camel.apache.org/schema/spring; id="main-route-id">
>
>
> java.lang.Exception
>
>
>
>
>
>
>
>
> java.lang.Exception
>
> expected
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20778) Intercept created using AdviceWithRouteBuilder causes issues with error handling (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847360#comment-17847360
]
Claus Ibsen commented on CAMEL-20778:
-
Yes you are welcome to send a PR for 4.4.x branch with the commit
> Intercept created using AdviceWithRouteBuilder causes issues with error
> handling (regression)
> -
>
> Key: CAMEL-20778
> URL: https://issues.apache.org/jira/browse/CAMEL-20778
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Denis Istomin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> Starting from Camel 4.0.0. It works with 3.22.x and below.
> Reproducer: [https://github.com/DenisIstomin/camel-intercept-bug]
> If route is configured like this:
> {code:java}
> public void configure() {
> onException(Exception.class)
> .log(LoggingLevel.ERROR, "handler", "called");
> from("direct:start").routeId("main-route-id")
> .doTry()
> .throwException(new Exception())
> .doCatch(Exception.class)
> .setBody(constant("expected"))
> .end();
> }
> {code}
> And then this route is adviced:
> {code:java}
> AdviceWith.adviceWith(context, "main-route-id", routeBuilder -> {
> routeBuilder.intercept().log("intercepted");
> });
> {code}
>
> Error handler will not catch an exception. Body will not be equal to
> "expected".
> XML:
> {code:xml}
> http://camel.apache.org/schema/spring; id="main-route-id">
>
>
> java.lang.Exception
>
>
>
>
>
>
>
>
> java.lang.Exception
>
> expected
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20783) camel export --runtime=quarkus does not work with custom camel.jbang.quarkusVersion
[
https://issues.apache.org/jira/browse/CAMEL-20783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20783:
Component/s: camel-jbang
> camel export --runtime=quarkus does not work with custom
> camel.jbang.quarkusVersion
> ---
>
> Key: CAMEL-20783
> URL: https://issues.apache.org/jira/browse/CAMEL-20783
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Peter Palaga
>Priority: Major
> Fix For: 4.7.0
>
>
> Steps to reproduce
> {code}
> $ camel -V
> 4.6.0
> $ camel init demo.java
> $ echo 'camel.jbang.quarkusVersion = 3.8.2' >> application.properties
> $ camel export --runtime=quarkus --directory=../camel-quarkus-demo demo.java
> ...
> Exception in thread "main" java.lang.AbstractMethodError: Receiver class
> org.apache.camel.catalog.quarkus.QuarkusRuntimeProvider does not define or
> inherit an implementation of the resolved method 'abstract java.util.List
> findTransformerNames()' of interface org.apache.camel.catalog.RuntimeProvider.
> at
> org.apache.camel.catalog.impl.AbstractCachingCamelCatalog.cache(AbstractCachingCamelCatalog.java:84)
> at
> org.apache.camel.catalog.DefaultCamelCatalog.findTransformerNames(DefaultCamelCatalog.java:256)
> at
> org.apache.camel.catalog.DefaultCamelCatalog.modelFromMavenGAV(DefaultCamelCatalog.java:562)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.createMavenPom(ExportQuarkus.java:382)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:121)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:138)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:57)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:239)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.doCall(Export.java:28)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
> at picocli.CommandLine.execute(CommandLine.java:2170)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:165)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20783) camel export --runtime=quarkus does not work with custom camel.jbang.quarkusVersion
[
https://issues.apache.org/jira/browse/CAMEL-20783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20783.
-
Fix Version/s: 4.7.0
Resolution: Duplicate
Thanks for testing. We discovered this with CAMEL-20586 as well so it will be
fixed for next release.
> camel export --runtime=quarkus does not work with custom
> camel.jbang.quarkusVersion
> ---
>
> Key: CAMEL-20783
> URL: https://issues.apache.org/jira/browse/CAMEL-20783
> Project: Camel
> Issue Type: Bug
>Reporter: Peter Palaga
>Priority: Major
> Fix For: 4.7.0
>
>
> Steps to reproduce
> {code}
> $ camel -V
> 4.6.0
> $ camel init demo.java
> $ echo 'camel.jbang.quarkusVersion = 3.8.2' >> application.properties
> $ camel export --runtime=quarkus --directory=../camel-quarkus-demo demo.java
> ...
> Exception in thread "main" java.lang.AbstractMethodError: Receiver class
> org.apache.camel.catalog.quarkus.QuarkusRuntimeProvider does not define or
> inherit an implementation of the resolved method 'abstract java.util.List
> findTransformerNames()' of interface org.apache.camel.catalog.RuntimeProvider.
> at
> org.apache.camel.catalog.impl.AbstractCachingCamelCatalog.cache(AbstractCachingCamelCatalog.java:84)
> at
> org.apache.camel.catalog.DefaultCamelCatalog.findTransformerNames(DefaultCamelCatalog.java:256)
> at
> org.apache.camel.catalog.DefaultCamelCatalog.modelFromMavenGAV(DefaultCamelCatalog.java:562)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.createMavenPom(ExportQuarkus.java:382)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:121)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:138)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:57)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:239)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.doCall(Export.java:28)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
> at picocli.CommandLine.execute(CommandLine.java:2170)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:165)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20786) Resolve Camel Property Placeholders in properties file/system
[
https://issues.apache.org/jira/browse/CAMEL-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847330#comment-17847330
]
Claus Ibsen commented on CAMEL-20786:
-
Does this not already work?
> Resolve Camel Property Placeholders in properties file/system
> -
>
> Key: CAMEL-20786
> URL: https://issues.apache.org/jira/browse/CAMEL-20786
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Priority: Major
>
> It would be nice to resolve Camel Property placeholders, for example, Azure
> Vault, in application.properties files, system properties, and so on. I think
> that plain Camel, Camel Spring Boot and Camel Quarkus may benefit from it,
> for example, I'd be able to do the following, given the
> application.properties file:
> {code:java}
> mypassword={{azure:pass}}
> {code}
> at runtime, the actual password is used and resolved using the
> camel-azure-key-vault component
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20754) Support MQTT5 Publish Properties in Paho-MQTT5 component
[ https://issues.apache.org/jira/browse/CAMEL-20754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847227#comment-17847227 ] Claus Ibsen commented on CAMEL-20754: - Thanks for the PR > Support MQTT5 Publish Properties in Paho-MQTT5 component > > > Key: CAMEL-20754 > URL: https://issues.apache.org/jira/browse/CAMEL-20754 > Project: Camel > Issue Type: New Feature > Components: camel-paho-mqtt5 >Reporter: Henning Sudbrock >Priority: Major > Fix For: 4.7.0 > > > Currently, for publishing MQTT5 messages, the camel-paho-mqtt5 supports > setting the desired topic, QoS, and retained flag. It does not support adding > the additional publish properties that were introduced with MQTT5. Those > additional publish properties include, i.a., content type, response topic, > message expiry interval, and a list of user properties (cf. section 3.3.2.3 > in the [MQTT5 > spec|https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html]). > These MQTT5-specific properties should be made available as message headers > in camel-paho-mqtt5 (both for extracting them from incoming MQTT5 messages, > and for setting them in outgoing MQTT5 messages). > Technically, the underlying library, Eclipse Paho, supports setting these > properties (cf. > [MqttMessage#setProperties|https://github.com/eclipse/paho.mqtt.java/blob/master/org.eclipse.paho.mqttv5.client/src/main/java/org/eclipse/paho/mqttv5/common/MqttMessage.java#L278]), > but they should be exposed as Camel message headers and, in case of outgoing > messages, be added to the message passed to Eclipse Paho > [here|https://github.com/apache/camel/blob/ba4bf712e66e17fd8c47536e9c45564b6637bb99/components/camel-paho-mqtt5/src/main/java/org/apache/camel/component/paho/mqtt5/PahoMqtt5Producer.java#L50-L52]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20754) Support MQTT5 Publish Properties in Paho-MQTT5 component
[ https://issues.apache.org/jira/browse/CAMEL-20754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20754. - Resolution: Fixed > Support MQTT5 Publish Properties in Paho-MQTT5 component > > > Key: CAMEL-20754 > URL: https://issues.apache.org/jira/browse/CAMEL-20754 > Project: Camel > Issue Type: New Feature > Components: camel-paho-mqtt5 >Reporter: Henning Sudbrock >Priority: Major > Fix For: 4.7.0 > > > Currently, for publishing MQTT5 messages, the camel-paho-mqtt5 supports > setting the desired topic, QoS, and retained flag. It does not support adding > the additional publish properties that were introduced with MQTT5. Those > additional publish properties include, i.a., content type, response topic, > message expiry interval, and a list of user properties (cf. section 3.3.2.3 > in the [MQTT5 > spec|https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html]). > These MQTT5-specific properties should be made available as message headers > in camel-paho-mqtt5 (both for extracting them from incoming MQTT5 messages, > and for setting them in outgoing MQTT5 messages). > Technically, the underlying library, Eclipse Paho, supports setting these > properties (cf. > [MqttMessage#setProperties|https://github.com/eclipse/paho.mqtt.java/blob/master/org.eclipse.paho.mqttv5.client/src/main/java/org/eclipse/paho/mqttv5/common/MqttMessage.java#L278]), > but they should be exposed as Camel message headers and, in case of outgoing > messages, be added to the message passed to Eclipse Paho > [here|https://github.com/apache/camel/blob/ba4bf712e66e17fd8c47536e9c45564b6637bb99/components/camel-paho-mqtt5/src/main/java/org/apache/camel/component/paho/mqtt5/PahoMqtt5Producer.java#L50-L52]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20778) Intercept created using AdviceWithRouteBuilder causes issues with error handling (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20778.
-
Fix Version/s: 4.7.0
Resolution: Fixed
> Intercept created using AdviceWithRouteBuilder causes issues with error
> handling (regression)
> -
>
> Key: CAMEL-20778
> URL: https://issues.apache.org/jira/browse/CAMEL-20778
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Denis Istomin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> Starting from Camel 4.0.0. It works with 3.22.x and below.
> Reproducer: [https://github.com/DenisIstomin/camel-intercept-bug]
> If route is configured like this:
> {code:java}
> public void configure() {
> onException(Exception.class)
> .log(LoggingLevel.ERROR, "handler", "called");
> from("direct:start").routeId("main-route-id")
> .doTry()
> .throwException(new Exception())
> .doCatch(Exception.class)
> .setBody(constant("expected"))
> .end();
> }
> {code}
> And then this route is adviced:
> {code:java}
> AdviceWith.adviceWith(context, "main-route-id", routeBuilder -> {
> routeBuilder.intercept().log("intercepted");
> });
> {code}
>
> Error handler will not catch an exception. Body will not be equal to
> "expected".
> XML:
> {code:xml}
> http://camel.apache.org/schema/spring; id="main-route-id">
>
>
> java.lang.Exception
>
>
>
>
>
>
>
>
> java.lang.Exception
>
> expected
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20778) Intercept created using AdviceWithRouteBuilder causes issues with error handling (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20778:
Component/s: camel-core
> Intercept created using AdviceWithRouteBuilder causes issues with error
> handling (regression)
> -
>
> Key: CAMEL-20778
> URL: https://issues.apache.org/jira/browse/CAMEL-20778
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Denis Istomin
>Assignee: Claus Ibsen
>Priority: Minor
>
> Starting from Camel 4.0.0. It works with 3.22.x and below.
> Reproducer: [https://github.com/DenisIstomin/camel-intercept-bug]
> If route is configured like this:
> {code:java}
> public void configure() {
> onException(Exception.class)
> .log(LoggingLevel.ERROR, "handler", "called");
> from("direct:start").routeId("main-route-id")
> .doTry()
> .throwException(new Exception())
> .doCatch(Exception.class)
> .setBody(constant("expected"))
> .end();
> }
> {code}
> And then this route is adviced:
> {code:java}
> AdviceWith.adviceWith(context, "main-route-id", routeBuilder -> {
> routeBuilder.intercept().log("intercepted");
> });
> {code}
>
> Error handler will not catch an exception. Body will not be equal to
> "expected".
> XML:
> {code:xml}
> http://camel.apache.org/schema/spring; id="main-route-id">
>
>
> java.lang.Exception
>
>
>
>
>
>
>
>
> java.lang.Exception
>
> expected
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20778) Intercept created using AdviceWithRouteBuilder causes issues with error handling (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20778:
---
Assignee: Claus Ibsen
> Intercept created using AdviceWithRouteBuilder causes issues with error
> handling (regression)
> -
>
> Key: CAMEL-20778
> URL: https://issues.apache.org/jira/browse/CAMEL-20778
> Project: Camel
> Issue Type: Bug
>Reporter: Denis Istomin
>Assignee: Claus Ibsen
>Priority: Minor
>
> Starting from Camel 4.0.0. It works with 3.22.x and below.
> Reproducer: [https://github.com/DenisIstomin/camel-intercept-bug]
> If route is configured like this:
> {code:java}
> public void configure() {
> onException(Exception.class)
> .log(LoggingLevel.ERROR, "handler", "called");
> from("direct:start").routeId("main-route-id")
> .doTry()
> .throwException(new Exception())
> .doCatch(Exception.class)
> .setBody(constant("expected"))
> .end();
> }
> {code}
> And then this route is adviced:
> {code:java}
> AdviceWith.adviceWith(context, "main-route-id", routeBuilder -> {
> routeBuilder.intercept().log("intercepted");
> });
> {code}
>
> Error handler will not catch an exception. Body will not be equal to
> "expected".
> XML:
> {code:xml}
> http://camel.apache.org/schema/spring; id="main-route-id">
>
>
> java.lang.Exception
>
>
>
>
>
>
>
>
> java.lang.Exception
>
> expected
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20780) camel-spring-boot - Upgrade to SB 3.2.6
Claus Ibsen created CAMEL-20780: --- Summary: camel-spring-boot - Upgrade to SB 3.2.6 Key: CAMEL-20780 URL: https://issues.apache.org/jira/browse/CAMEL-20780 Project: Camel Issue Type: Dependency upgrade Components: camel-spring-boot Reporter: Claus Ibsen Fix For: 4.4.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20781) camel-spring-boot - Upgrade to SB 3.1.12
Claus Ibsen created CAMEL-20781: --- Summary: camel-spring-boot - Upgrade to SB 3.1.12 Key: CAMEL-20781 URL: https://issues.apache.org/jira/browse/CAMEL-20781 Project: Camel Issue Type: Dependency upgrade Components: camel-spring-boot Reporter: Claus Ibsen Fix For: 4.0.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20779) camel-spring-boot - Upgrade to SB 3.3.0
Claus Ibsen created CAMEL-20779: --- Summary: camel-spring-boot - Upgrade to SB 3.3.0 Key: CAMEL-20779 URL: https://issues.apache.org/jira/browse/CAMEL-20779 Project: Camel Issue Type: Dependency upgrade Components: camel-spring-boot Reporter: Claus Ibsen Fix For: 4.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20774) camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters
[ https://issues.apache.org/jira/browse/CAMEL-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847011#comment-17847011 ] Claus Ibsen commented on CAMEL-20774: - Yeah all that legacy SSL factory beans is for spring XML exclusively. We can make a generic factory bean and markup it with the new bean marker then its included in catalog, and tooling will be able to offer assistance. then you can define as many you want via the regular and -beans in YAML DSL. And we can add fluent builder methods then you can do it via java code with @Bean in spring boot etc. Adding special DSL is just a feature creep. Its not Camel stuff but general Java/JSSE stuff > camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the > object KeyStoreParameters > -- > > Key: CAMEL-20774 > URL: https://issues.apache.org/jira/browse/CAMEL-20774 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.6.0 >Reporter: Federico Mariani >Priority: Minor > Fix For: 4.x > > > The property keyStore (java.security.KeyStore) is present in the class > KeyStoreParameters but is missing from the XML type > tns:keyStoreParametersFactoryBean. > The java.security.KeyStore XML configuration may be needed for some use cases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20776) Camel-kinesis: Getting shard iterator before every record request will reduce performance
[ https://issues.apache.org/jira/browse/CAMEL-20776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847009#comment-17847009 ] Claus Ibsen commented on CAMEL-20776: - You are welcome to work on a suggested code fix and send as PR > Camel-kinesis: Getting shard iterator before every record request will reduce > performance > - > > Key: CAMEL-20776 > URL: https://issues.apache.org/jira/browse/CAMEL-20776 > Project: Camel > Issue Type: Improvement > Components: camel-aws2-kinesis >Reporter: Fan Yang >Priority: Minor > > Each time when camel kinesis connector requests records, it gets shard > iterator first. This will cause performance loss. > Possible solution is to store next shard iterator returned by response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20776) Camel-kinesis: Getting shard iterator before every record request will reduce performance
[ https://issues.apache.org/jira/browse/CAMEL-20776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20776: Fix Version/s: 4.x > Camel-kinesis: Getting shard iterator before every record request will reduce > performance > - > > Key: CAMEL-20776 > URL: https://issues.apache.org/jira/browse/CAMEL-20776 > Project: Camel > Issue Type: Improvement > Components: camel-aws2-kinesis >Reporter: Fan Yang >Priority: Minor > Fix For: 4.x > > > Each time when camel kinesis connector requests records, it gets shard > iterator first. This will cause performance loss. > Possible solution is to store next shard iterator returned by response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20777) Intercept Java DSL is not supported on the route scope
[
https://issues.apache.org/jira/browse/CAMEL-20777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20777.
-
Fix Version/s: 4.7.0
Assignee: Claus Ibsen
Resolution: Fixed
Yeah the doc is outdated for v4
> Intercept Java DSL is not supported on the route scope
> --
>
> Key: CAMEL-20777
> URL: https://issues.apache.org/jira/browse/CAMEL-20777
> Project: Camel
> Issue Type: Task
>Reporter: Denis Istomin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> According to the documentation:
> [https://camel.apache.org/components/4.4.x/eips/intercept.html]
> `.intercept()` could be set on the route scope:
> {code:java}
> from("jms:queue:order")
>.intercept().to("log:hello").end() // intercepts only in this route
> .to("bean:validateOrder")
> .to("bean:processOrder");
> {code}
> But it causes a compile-time error:
> {code:java}
> cannot find symbol
> [ERROR] symbol: method intercept()
> [ERROR] location: class org.apache.camel.model.RouteDefinition
> {code}
> It is a bug in a documentation or in a Camel itself.
> If it is a bug in a documentation, then it should be explicitly said that
> `intercept()` on the route scope is not supported.
> Note: intercept can be used in AdviceWith with AdviceWithRouteBuilder:
> {code:java}
> AdviceWith.adviceWith(context, "route_id", routeBuilder -> {
> routeBuilder.intercept().to(...);
> });
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20777) Intercept Java DSL is not supported on the route scope
[
https://issues.apache.org/jira/browse/CAMEL-20777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20777:
Issue Type: Task (was: Bug)
> Intercept Java DSL is not supported on the route scope
> --
>
> Key: CAMEL-20777
> URL: https://issues.apache.org/jira/browse/CAMEL-20777
> Project: Camel
> Issue Type: Task
>Reporter: Denis Istomin
>Priority: Minor
>
> According to the documentation:
> [https://camel.apache.org/components/4.4.x/eips/intercept.html]
> `.intercept()` could be set on the route scope:
> {code:java}
> from("jms:queue:order")
>.intercept().to("log:hello").end() // intercepts only in this route
> .to("bean:validateOrder")
> .to("bean:processOrder");
> {code}
> But it causes a compile-time error:
> {code:java}
> cannot find symbol
> [ERROR] symbol: method intercept()
> [ERROR] location: class org.apache.camel.model.RouteDefinition
> {code}
> It is a bug in a documentation or in a Camel itself.
> If it is a bug in a documentation, then it should be explicitly said that
> `intercept()` on the route scope is not supported.
> Note: intercept can be used in AdviceWith with AdviceWithRouteBuilder:
> {code:java}
> AdviceWith.adviceWith(context, "route_id", routeBuilder -> {
> routeBuilder.intercept().to(...);
> });
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20774) camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters
[ https://issues.apache.org/jira/browse/CAMEL-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846992#comment-17846992 ] Claus Ibsen commented on CAMEL-20774: - For camel main / camel spring boot https://camel.apache.org/components/4.4.x/others/main.html#_camel_ssl_configurations for SB (see camel.ssl.xx options in this page) https://camel.apache.org/camel-spring-boot/4.4.x/spring-boot.html > camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the > object KeyStoreParameters > -- > > Key: CAMEL-20774 > URL: https://issues.apache.org/jira/browse/CAMEL-20774 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.6.0 >Reporter: Federico Mariani >Priority: Minor > Fix For: 4.x > > > The property keyStore (java.security.KeyStore) is present in the class > KeyStoreParameters but is missing from the XML type > tns:keyStoreParametersFactoryBean. > The java.security.KeyStore XML configuration may be needed for some use cases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20774) camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters
[ https://issues.apache.org/jira/browse/CAMEL-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20774: Issue Type: Improvement (was: Bug) > camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the > object KeyStoreParameters > -- > > Key: CAMEL-20774 > URL: https://issues.apache.org/jira/browse/CAMEL-20774 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.6.0 >Reporter: Federico Mariani >Priority: Minor > Fix For: 4.x > > > The property keyStore (java.security.KeyStore) is present in the class > KeyStoreParameters but is missing from the XML type > tns:keyStoreParametersFactoryBean. > The java.security.KeyStore XML configuration may be needed for some use cases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20774) camel-core-model - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters
[ https://issues.apache.org/jira/browse/CAMEL-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846976#comment-17846976 ] Claus Ibsen commented on CAMEL-20774: - This is for spring/blueprint XML DSL which is a bit legacy > camel-core-model - Align the type tns:keyStoreParametersFactoryBean to the > object KeyStoreParameters > > > Key: CAMEL-20774 > URL: https://issues.apache.org/jira/browse/CAMEL-20774 > Project: Camel > Issue Type: Bug >Affects Versions: 4.6.0 >Reporter: Federico Mariani >Priority: Minor > Fix For: 4.x > > > The property keyStore (java.security.KeyStore) is present in the class > KeyStoreParameters but is missing from the XML type > tns:keyStoreParametersFactoryBean. > The java.security.KeyStore XML configuration may be needed for some use cases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20774) camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters
[ https://issues.apache.org/jira/browse/CAMEL-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20774: Summary: camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters (was: camel-core-model - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters) > camel-core-xml - Align the type tns:keyStoreParametersFactoryBean to the > object KeyStoreParameters > -- > > Key: CAMEL-20774 > URL: https://issues.apache.org/jira/browse/CAMEL-20774 > Project: Camel > Issue Type: Bug >Affects Versions: 4.6.0 >Reporter: Federico Mariani >Priority: Minor > Fix For: 4.x > > > The property keyStore (java.security.KeyStore) is present in the class > KeyStoreParameters but is missing from the XML type > tns:keyStoreParametersFactoryBean. > The java.security.KeyStore XML configuration may be needed for some use cases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20774) camel-core-model - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters
[ https://issues.apache.org/jira/browse/CAMEL-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20774: Summary: camel-core-model - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters (was: Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters) > camel-core-model - Align the type tns:keyStoreParametersFactoryBean to the > object KeyStoreParameters > > > Key: CAMEL-20774 > URL: https://issues.apache.org/jira/browse/CAMEL-20774 > Project: Camel > Issue Type: Bug >Affects Versions: 4.6.0 >Reporter: Federico Mariani >Priority: Minor > > The property keyStore (java.security.KeyStore) is present in the class > KeyStoreParameters but is missing from the XML type > tns:keyStoreParametersFactoryBean. > The java.security.KeyStore XML configuration may be needed for some use cases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20774) camel-core-model - Align the type tns:keyStoreParametersFactoryBean to the object KeyStoreParameters
[ https://issues.apache.org/jira/browse/CAMEL-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20774: Fix Version/s: 4.x > camel-core-model - Align the type tns:keyStoreParametersFactoryBean to the > object KeyStoreParameters > > > Key: CAMEL-20774 > URL: https://issues.apache.org/jira/browse/CAMEL-20774 > Project: Camel > Issue Type: Bug >Affects Versions: 4.6.0 >Reporter: Federico Mariani >Priority: Minor > Fix For: 4.x > > > The property keyStore (java.security.KeyStore) is present in the class > KeyStoreParameters but is missing from the XML type > tns:keyStoreParametersFactoryBean. > The java.security.KeyStore XML configuration may be needed for some use cases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20439) camel-cloudevents - Move API to camel-api
[ https://issues.apache.org/jira/browse/CAMEL-20439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20439. - Resolution: Fixed > camel-cloudevents - Move API to camel-api > - > > Key: CAMEL-20439 > URL: https://issues.apache.org/jira/browse/CAMEL-20439 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Jono Morris >Priority: Major > Fix For: 4.7.0 > > > Instead of having a tiny API that are optional for components that add > transformers for CE and we need to have optional dependency set. And that > camel-cloudevents does not have any 3rd party dependency. Its just a set of > header names. Then we can move that into camel-api under a > org.apache.camel.cloudevents or something -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20773) camel-health - Consumer health checks should be skipped for non autoStartup routes
[ https://issues.apache.org/jira/browse/CAMEL-20773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20773. - Resolution: Fixed > camel-health - Consumer health checks should be skipped for non autoStartup > routes > -- > > Key: CAMEL-20773 > URL: https://issues.apache.org/jira/browse/CAMEL-20773 > Project: Camel > Issue Type: Improvement > Components: camel-health >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > If a route is not auto startup, then its manually managed, and so health > checks should be skipped for these routes and their consumers. > The route and consumer checks are linked together. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20768) camel-spring-redis - SpringRedisIdempotentRepository flushes DB on start
[
https://issues.apache.org/jira/browse/CAMEL-20768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20768.
-
Resolution: Fixed
> camel-spring-redis - SpringRedisIdempotentRepository flushes DB on start
>
>
> Key: CAMEL-20768
> URL: https://issues.apache.org/jira/browse/CAMEL-20768
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-redis
>Affects Versions: 4.5.0, 4.6.0
>Reporter: Dylan Piergies
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> The {{SpringRedisIdempotentRepository}} class executes the statement
> {{this.redisTemplate.getConnectionFactory().getConnection().flushDb();}}
> within its {{doStart}} method.
> This behaviour does not seem safe or desirable, since the DB may be in use by
> other applications, or by replicas of a single application.
> It seems that a restart of the application or a scale-up event would cause
> the idempotency DB to be lost, which somewhat defeats the point of using a
> centralised cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20768) camel-spring-redis - SpringRedisIdempotentRepository flushes DB on start
[
https://issues.apache.org/jira/browse/CAMEL-20768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20768:
---
Assignee: Claus Ibsen
> camel-spring-redis - SpringRedisIdempotentRepository flushes DB on start
>
>
> Key: CAMEL-20768
> URL: https://issues.apache.org/jira/browse/CAMEL-20768
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-redis
>Affects Versions: 4.5.0, 4.6.0
>Reporter: Dylan Piergies
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> The {{SpringRedisIdempotentRepository}} class executes the statement
> {{this.redisTemplate.getConnectionFactory().getConnection().flushDb();}}
> within its {{doStart}} method.
> This behaviour does not seem safe or desirable, since the DB may be in use by
> other applications, or by replicas of a single application.
> It seems that a restart of the application or a scale-up event would cause
> the idempotency DB to be lost, which somewhat defeats the point of using a
> centralised cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20773) camel-health - Consumer health checks should be skipped for non autoStartup routes
Claus Ibsen created CAMEL-20773: --- Summary: camel-health - Consumer health checks should be skipped for non autoStartup routes Key: CAMEL-20773 URL: https://issues.apache.org/jira/browse/CAMEL-20773 Project: Camel Issue Type: Improvement Components: camel-health Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.7.0 If a route is not auto startup, then its manually managed, and so health checks should be skipped for these routes and their consumers. The route and consumer checks are linked together. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20769) camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
[
https://issues.apache.org/jira/browse/CAMEL-20769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20769.
-
Resolution: Fixed
> camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
> --
>
> Key: CAMEL-20769
> URL: https://issues.apache.org/jira/browse/CAMEL-20769
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
>Affects Versions: 4.6.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> Looking at the logs for a test that has been hang up on my CI for several
> hours I noticed that the logs are full of messages like:
>
> {code:java}
> 2024-05-14 13:08:46,501 [sComponentTest]] WARN TemporaryQueueReplyManager
> - Exception inside the DMLC for Temporary ReplyTo Queue for destination
> JmsComponentTest, refreshing ReplyTo destination (stacktrace in DEBUG logging
> level).
> 2024-05-14 13:08:46,501 [sComponentTest]] ERROR
> ultJmsMessageListenerContainer - Could not refresh JMS Connection for
> destination 'temporary' - retrying using FixedBackOff{interval=9000,
> currentAttempts=1908, maxAttempts=unlimited}. Cause: Failed to create session
> factory; nested exception is
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007:
> Cannot connect to server(s). Tried with all available servers.]{code}
>
> The code is in an endless loop on my CI for 6 hours:
> {code:java}
> cat target/camel-jms-test.log | grep "Exception inside the DMLC for
> Temporary" | wc -l
> 1912{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20439) camel-cloudevents - Move API to camel-api
[ https://issues.apache.org/jira/browse/CAMEL-20439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20439: Fix Version/s: 4.7.0 (was: 4.x) > camel-cloudevents - Move API to camel-api > - > > Key: CAMEL-20439 > URL: https://issues.apache.org/jira/browse/CAMEL-20439 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Jono Morris >Priority: Major > Fix For: 4.7.0 > > > Instead of having a tiny API that are optional for components that add > transformers for CE and we need to have optional dependency set. And that > camel-cloudevents does not have any 3rd party dependency. Its just a set of > header names. Then we can move that into camel-api under a > org.apache.camel.cloudevents or something -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20493) camel-core: concurrency issue copying headers
[
https://issues.apache.org/jira/browse/CAMEL-20493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846641#comment-17846641
]
Claus Ibsen commented on CAMEL-20493:
-
Today on main branch
{code}
[ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.191 s
<<< FAILURE! -- in
org.apache.camel.component.jms.JmsProducerConcurrentWithReplyTest
[ERROR]
org.apache.camel.component.jms.JmsProducerConcurrentWithReplyTest.testConcurrentProducers
-- Time elapsed: 0.139 s <<< ERROR!
java.util.concurrent.ExecutionException:
org.apache.camel.CamelExecutionException: Exception occurred during execution
on the exchange: Exchange[CF23C35CE9BBF3D-025A]
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:205)
at
org.apache.camel.component.jms.JmsProducerConcurrentWithReplyTest.doSendMessages(JmsProducerConcurrentWithReplyTest.java:86)
at
org.apache.camel.component.jms.JmsProducerConcurrentWithReplyTest.testConcurrentProducers(JmsProducerConcurrentWithReplyTest.java:68)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at
java.base/java.util.concurrent.RecursiveAction.exec(RecursiveAction.java:194)
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Caused by: org.apache.camel.CamelExecutionException: Exception occurred during
execution on the exchange: Exchange[CF23C35CE9BBF3D-025A]
at
org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)
at
org.apache.camel.support.ExchangeHelper.extractResultBody(ExchangeHelper.java:677)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:591)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:587)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:414)
at
org.apache.camel.component.jms.JmsProducerConcurrentWithReplyTest.lambda$doSendMessages$0(JmsProducerConcurrentWithReplyTest.java:79)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.util.ConcurrentModificationException
at
java.base/java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1486)
at java.base/java.util.TreeMap$EntryIterator.next(TreeMap.java:1522)
at java.base/java.util.TreeMap$EntryIterator.next(TreeMap.java:1517)
at java.base/java.util.TreeMap.buildFromSorted(TreeMap.java:2879)
at java.base/java.util.TreeMap.buildFromSorted(TreeMap.java:2871)
at java.base/java.util.TreeMap.buildFromSorted(TreeMap.java:2903)
at java.base/java.util.TreeMap.buildFromSorted(TreeMap.java:2871)
at java.base/java.util.TreeMap.buildFromSorted(TreeMap.java:2828)
at java.base/java.util.TreeMap.putAll(TreeMap.java:319)
at
org.apache.camel.support.MessageSupport.copyFromWithNewBody(MessageSupport.java:226)
at
org.apache.camel.support.processor.ConvertBodyProcessor.process(ConvertBodyProcessor.java:129)
at
org.apache.camel.impl.engine.SharedCamelInternalProcessor$InternalCallback.done(SharedCamelInternalProcessor.java:216)
at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.doRun(DefaultReactiveExecutor.java:199)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeReactiveWork(DefaultReactiveExecutor.java:189)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.tryExecuteReactiveWork(DefaultReactiveExecutor.java:166)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:148)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor.schedule(DefaultReactiveExecutor.java:54)
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$SimpleTask.run(RedeliveryErrorHandler.java:421)
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$SimpleTask.done(RedeliveryErrorHandler.java:392)
at
[jira] [Commented] (CAMEL-20769) camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
[
https://issues.apache.org/jira/browse/CAMEL-20769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846630#comment-17846630
]
Claus Ibsen commented on CAMEL-20769:
-
Okay changing the thread locking code to be similar to wait for provisional
message id to be updated, which is more thread safe.
This could very likely fix this problem.
> camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
> --
>
> Key: CAMEL-20769
> URL: https://issues.apache.org/jira/browse/CAMEL-20769
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
>Affects Versions: 4.6.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> Looking at the logs for a test that has been hang up on my CI for several
> hours I noticed that the logs are full of messages like:
>
> {code:java}
> 2024-05-14 13:08:46,501 [sComponentTest]] WARN TemporaryQueueReplyManager
> - Exception inside the DMLC for Temporary ReplyTo Queue for destination
> JmsComponentTest, refreshing ReplyTo destination (stacktrace in DEBUG logging
> level).
> 2024-05-14 13:08:46,501 [sComponentTest]] ERROR
> ultJmsMessageListenerContainer - Could not refresh JMS Connection for
> destination 'temporary' - retrying using FixedBackOff{interval=9000,
> currentAttempts=1908, maxAttempts=unlimited}. Cause: Failed to create session
> factory; nested exception is
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007:
> Cannot connect to server(s). Tried with all available servers.]{code}
>
> The code is in an endless loop on my CI for 6 hours:
> {code:java}
> cat target/camel-jms-test.log | grep "Exception inside the DMLC for
> Temporary" | wc -l
> 1912{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20769) camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
[
https://issues.apache.org/jira/browse/CAMEL-20769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20769:
---
Assignee: Claus Ibsen
> camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
> --
>
> Key: CAMEL-20769
> URL: https://issues.apache.org/jira/browse/CAMEL-20769
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
>Affects Versions: 4.6.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Claus Ibsen
>Priority: Major
>
> Looking at the logs for a test that has been hang up on my CI for several
> hours I noticed that the logs are full of messages like:
>
> {code:java}
> 2024-05-14 13:08:46,501 [sComponentTest]] WARN TemporaryQueueReplyManager
> - Exception inside the DMLC for Temporary ReplyTo Queue for destination
> JmsComponentTest, refreshing ReplyTo destination (stacktrace in DEBUG logging
> level).
> 2024-05-14 13:08:46,501 [sComponentTest]] ERROR
> ultJmsMessageListenerContainer - Could not refresh JMS Connection for
> destination 'temporary' - retrying using FixedBackOff{interval=9000,
> currentAttempts=1908, maxAttempts=unlimited}. Cause: Failed to create session
> factory; nested exception is
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007:
> Cannot connect to server(s). Tried with all available servers.]{code}
>
> The code is in an endless loop on my CI for 6 hours:
> {code:java}
> cat target/camel-jms-test.log | grep "Exception inside the DMLC for
> Temporary" | wc -l
> 1912{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20769) camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
[
https://issues.apache.org/jira/browse/CAMEL-20769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20769:
Fix Version/s: 4.7.0
> camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
> --
>
> Key: CAMEL-20769
> URL: https://issues.apache.org/jira/browse/CAMEL-20769
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
>Affects Versions: 4.6.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> Looking at the logs for a test that has been hang up on my CI for several
> hours I noticed that the logs are full of messages like:
>
> {code:java}
> 2024-05-14 13:08:46,501 [sComponentTest]] WARN TemporaryQueueReplyManager
> - Exception inside the DMLC for Temporary ReplyTo Queue for destination
> JmsComponentTest, refreshing ReplyTo destination (stacktrace in DEBUG logging
> level).
> 2024-05-14 13:08:46,501 [sComponentTest]] ERROR
> ultJmsMessageListenerContainer - Could not refresh JMS Connection for
> destination 'temporary' - retrying using FixedBackOff{interval=9000,
> currentAttempts=1908, maxAttempts=unlimited}. Cause: Failed to create session
> factory; nested exception is
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007:
> Cannot connect to server(s). Tried with all available servers.]{code}
>
> The code is in an endless loop on my CI for 6 hours:
> {code:java}
> cat target/camel-jms-test.log | grep "Exception inside the DMLC for
> Temporary" | wc -l
> 1912{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20769) camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
[
https://issues.apache.org/jira/browse/CAMEL-20769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846612#comment-17846612
]
Claus Ibsen commented on CAMEL-20769:
-
Okay if I do some dirty thread hacking I can maybe simulate that camel-jms
cannot create a temporary queue due to JMS broker failure, and it keeps
looping. And then at the same timer the JMS producer is waiting for that reply
to queue to be ready. However it uses some old thread await that never gets
signalled due to that endless exception. And then in fact we have code
afterwards that has a 10 sec timeout waiting for reply to be ready.
> camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
> --
>
> Key: CAMEL-20769
> URL: https://issues.apache.org/jira/browse/CAMEL-20769
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
>Affects Versions: 4.6.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
>
> Looking at the logs for a test that has been hang up on my CI for several
> hours I noticed that the logs are full of messages like:
>
> {code:java}
> 2024-05-14 13:08:46,501 [sComponentTest]] WARN TemporaryQueueReplyManager
> - Exception inside the DMLC for Temporary ReplyTo Queue for destination
> JmsComponentTest, refreshing ReplyTo destination (stacktrace in DEBUG logging
> level).
> 2024-05-14 13:08:46,501 [sComponentTest]] ERROR
> ultJmsMessageListenerContainer - Could not refresh JMS Connection for
> destination 'temporary' - retrying using FixedBackOff{interval=9000,
> currentAttempts=1908, maxAttempts=unlimited}. Cause: Failed to create session
> factory; nested exception is
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007:
> Cannot connect to server(s). Tried with all available servers.]{code}
>
> The code is in an endless loop on my CI for 6 hours:
> {code:java}
> cat target/camel-jms-test.log | grep "Exception inside the DMLC for
> Temporary" | wc -l
> 1912{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20769) camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
[
https://issues.apache.org/jira/browse/CAMEL-20769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846611#comment-17846611
]
Claus Ibsen commented on CAMEL-20769:
-
Or maybe you have camel-jms-test.log you can attach
> camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
> --
>
> Key: CAMEL-20769
> URL: https://issues.apache.org/jira/browse/CAMEL-20769
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
>Affects Versions: 4.6.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
>
> Looking at the logs for a test that has been hang up on my CI for several
> hours I noticed that the logs are full of messages like:
>
> {code:java}
> 2024-05-14 13:08:46,501 [sComponentTest]] WARN TemporaryQueueReplyManager
> - Exception inside the DMLC for Temporary ReplyTo Queue for destination
> JmsComponentTest, refreshing ReplyTo destination (stacktrace in DEBUG logging
> level).
> 2024-05-14 13:08:46,501 [sComponentTest]] ERROR
> ultJmsMessageListenerContainer - Could not refresh JMS Connection for
> destination 'temporary' - retrying using FixedBackOff{interval=9000,
> currentAttempts=1908, maxAttempts=unlimited}. Cause: Failed to create session
> factory; nested exception is
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007:
> Cannot connect to server(s). Tried with all available servers.]{code}
>
> The code is in an endless loop on my CI for 6 hours:
> {code:java}
> cat target/camel-jms-test.log | grep "Exception inside the DMLC for
> Temporary" | wc -l
> 1912{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20769) camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
[
https://issues.apache.org/jira/browse/CAMEL-20769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846610#comment-17846610
]
Claus Ibsen commented on CAMEL-20769:
-
Are you able to see if its a specific test that hangs and keep looping there?
> camel-jms: TemporaryReplyQueueExceptionListener may be causing an endless lock
> --
>
> Key: CAMEL-20769
> URL: https://issues.apache.org/jira/browse/CAMEL-20769
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
>Affects Versions: 4.6.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
>
> Looking at the logs for a test that has been hang up on my CI for several
> hours I noticed that the logs are full of messages like:
>
> {code:java}
> 2024-05-14 13:08:46,501 [sComponentTest]] WARN TemporaryQueueReplyManager
> - Exception inside the DMLC for Temporary ReplyTo Queue for destination
> JmsComponentTest, refreshing ReplyTo destination (stacktrace in DEBUG logging
> level).
> 2024-05-14 13:08:46,501 [sComponentTest]] ERROR
> ultJmsMessageListenerContainer - Could not refresh JMS Connection for
> destination 'temporary' - retrying using FixedBackOff{interval=9000,
> currentAttempts=1908, maxAttempts=unlimited}. Cause: Failed to create session
> factory; nested exception is
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007:
> Cannot connect to server(s). Tried with all available servers.]{code}
>
> The code is in an endless loop on my CI for 6 hours:
> {code:java}
> cat target/camel-jms-test.log | grep "Exception inside the DMLC for
> Temporary" | wc -l
> 1912{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20770) onException(Throwable.class) does not catch java.lang.AssertionError
[
https://issues.apache.org/jira/browse/CAMEL-20770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20770.
-
Resolution: Information Provided
> onException(Throwable.class) does not catch java.lang.AssertionError
>
>
> Key: CAMEL-20770
> URL: https://issues.apache.org/jira/browse/CAMEL-20770
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.4.0
>Reporter: John Yin
>Priority: Major
>
> The onException(Throwable.class) does not catch java.lang.AssertionError in
> 4.4.0. It worked fine in 3.18.x.
> Here is a sample:
> {code:java}
> from("timer://test?repeatCount=1")
> .onException(Throwable.class).handled(true).log("in onException").end()
> .process({
> assert false : "test onException for assert"
> }) {code}
> The onException would not catch the assert failure and not print "in
> onException" in log. The onException can catch other exceptions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20770) onException(Throwable.class) does not catch java.lang.AssertionError
[
https://issues.apache.org/jira/browse/CAMEL-20770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846606#comment-17846606
]
Claus Ibsen commented on CAMEL-20770:
-
Camel only catches Exception to let serious errors like OOME and others be
handed by the JVM as they should be.
There is a JIRA somewhere about this
> onException(Throwable.class) does not catch java.lang.AssertionError
>
>
> Key: CAMEL-20770
> URL: https://issues.apache.org/jira/browse/CAMEL-20770
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.4.0
>Reporter: John Yin
>Priority: Major
>
> The onException(Throwable.class) does not catch java.lang.AssertionError in
> 4.4.0. It worked fine in 3.18.x.
> Here is a sample:
> {code:java}
> from("timer://test?repeatCount=1")
> .onException(Throwable.class).handled(true).log("in onException").end()
> .process({
> assert false : "test onException for assert"
> }) {code}
> The onException would not catch the assert failure and not print "in
> onException" in log. The onException can catch other exceptions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20763) Rest template with underscore fails after Camel 4.2.0
[
https://issues.apache.org/jira/browse/CAMEL-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20763:
Fix Version/s: 4.4.3
> Rest template with underscore fails after Camel 4.2.0
> -
>
> Key: CAMEL-20763
> URL: https://issues.apache.org/jira/browse/CAMEL-20763
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.2.0
> Environment: Camel 4.2.0 or later
>Reporter: Dave Riseley
>Priority: Minor
> Fix For: 4.4.3, 4.7.0
>
>
> We have a camel route, which in it's simplified form looks like this:
> {code:java}
> @Component
> public class CamelRouteBuilder extends RouteBuilder{
> @Override
> public void configure() throws Exception {
> restConfiguration().component("servlet");
> rest("/hello")
> .get("/{first_name}")
> .to("direct:helloworld");
> from("direct:helloworld")
> .transform()
> .simple("Hi ${header.first_name}");
> }
> }
> {code}
> This works fine on Spring Boot 3.1.11 / Camel 4.0.5 . When we upgrade to
> Camel 4.2.0 or later, it fails on startup with the following exception:
>
> {code:java}
> Caused by: java.util.regex.PatternSyntaxException: named capturing group is
> missing trailing '>' near index 17
> \/hello\/(?[^\/]+)
> ^
> at java.base/java.util.regex.Pattern.error(Pattern.java:2028) ~[na:na]
> at java.base/java.util.regex.Pattern.groupname(Pattern.java:2945)
> ~[na:na]
> at java.base/java.util.regex.Pattern.group0(Pattern.java:2990)
> ~[na:na]
> at java.base/java.util.regex.Pattern.sequence(Pattern.java:2124)
> ~[na:na]
> at java.base/java.util.regex.Pattern.expr(Pattern.java:2069) ~[na:na]
> at java.base/java.util.regex.Pattern.compile(Pattern.java:1783)
> ~[na:na]
> at java.base/java.util.regex.Pattern.(Pattern.java:1430)
> ~[na:na]
> at java.base/java.util.regex.Pattern.compile(Pattern.java:1069)
> ~[na:na]
> at
> org.apache.camel.support.RestConsumerContextPathMatcher.register(RestConsumerContextPathMatcher.java:255)
> ~[camel-support-4.2.0.jar:4.2.0]
> at
> org.apache.camel.http.common.CamelServlet.connect(CamelServlet.java:424)
> ~[camel-http-common-4.2.0.jar:4.2.0]
> at
> org.apache.camel.component.servlet.CamelHttpTransportServlet.connect(CamelHttpTransportServlet.java:100)
> ~[camel-servlet-4.2.0.jar:4.2.0]
>
> {code}
> I believe this is due to a change introduced by
> https://issues.apache.org/jira/browse/CAMEL-8306 in which the following
> method:
> {code:java}
> /**
> * Pre-compiled consumer path for wildcard match
> *
> * @param consumerPath a consumer path
> */
> public static void register(String consumerPath) {
> // Convert URI template to a regex pattern
> String regex = consumerPath
> .replace("/", "\\/")
> .replace("{", "(?<")
> .replace("}", ">[^\\/]+)");
> // Add support for wildcard * as path suffix
> regex = regex.replace("*", ".*");
> // Match the provided path against the regex pattern
> Pattern pattern = Pattern.compile(regex);
> PATH_PATTERN.put(consumerPath, pattern);
> }
> {code}
>
> does not allow for underscore (and other regex special characters) in the
> parameter name. I could not find any documentation that describes limits on
> the characters that can be used in rest templates.
> Our production code has many, many rest routes with many parameters with
> underscores in them.
> I will prepare a PR with a proposed fix
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20763) Rest template with underscore fails after Camel 4.2.0
[
https://issues.apache.org/jira/browse/CAMEL-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20763.
-
Resolution: Fixed
> Rest template with underscore fails after Camel 4.2.0
> -
>
> Key: CAMEL-20763
> URL: https://issues.apache.org/jira/browse/CAMEL-20763
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.2.0
> Environment: Camel 4.2.0 or later
>Reporter: Dave Riseley
>Priority: Minor
> Fix For: 4.4.3, 4.7.0
>
>
> We have a camel route, which in it's simplified form looks like this:
> {code:java}
> @Component
> public class CamelRouteBuilder extends RouteBuilder{
> @Override
> public void configure() throws Exception {
> restConfiguration().component("servlet");
> rest("/hello")
> .get("/{first_name}")
> .to("direct:helloworld");
> from("direct:helloworld")
> .transform()
> .simple("Hi ${header.first_name}");
> }
> }
> {code}
> This works fine on Spring Boot 3.1.11 / Camel 4.0.5 . When we upgrade to
> Camel 4.2.0 or later, it fails on startup with the following exception:
>
> {code:java}
> Caused by: java.util.regex.PatternSyntaxException: named capturing group is
> missing trailing '>' near index 17
> \/hello\/(?[^\/]+)
> ^
> at java.base/java.util.regex.Pattern.error(Pattern.java:2028) ~[na:na]
> at java.base/java.util.regex.Pattern.groupname(Pattern.java:2945)
> ~[na:na]
> at java.base/java.util.regex.Pattern.group0(Pattern.java:2990)
> ~[na:na]
> at java.base/java.util.regex.Pattern.sequence(Pattern.java:2124)
> ~[na:na]
> at java.base/java.util.regex.Pattern.expr(Pattern.java:2069) ~[na:na]
> at java.base/java.util.regex.Pattern.compile(Pattern.java:1783)
> ~[na:na]
> at java.base/java.util.regex.Pattern.(Pattern.java:1430)
> ~[na:na]
> at java.base/java.util.regex.Pattern.compile(Pattern.java:1069)
> ~[na:na]
> at
> org.apache.camel.support.RestConsumerContextPathMatcher.register(RestConsumerContextPathMatcher.java:255)
> ~[camel-support-4.2.0.jar:4.2.0]
> at
> org.apache.camel.http.common.CamelServlet.connect(CamelServlet.java:424)
> ~[camel-http-common-4.2.0.jar:4.2.0]
> at
> org.apache.camel.component.servlet.CamelHttpTransportServlet.connect(CamelHttpTransportServlet.java:100)
> ~[camel-servlet-4.2.0.jar:4.2.0]
>
> {code}
> I believe this is due to a change introduced by
> https://issues.apache.org/jira/browse/CAMEL-8306 in which the following
> method:
> {code:java}
> /**
> * Pre-compiled consumer path for wildcard match
> *
> * @param consumerPath a consumer path
> */
> public static void register(String consumerPath) {
> // Convert URI template to a regex pattern
> String regex = consumerPath
> .replace("/", "\\/")
> .replace("{", "(?<")
> .replace("}", ">[^\\/]+)");
> // Add support for wildcard * as path suffix
> regex = regex.replace("*", ".*");
> // Match the provided path against the regex pattern
> Pattern pattern = Pattern.compile(regex);
> PATH_PATTERN.put(consumerPath, pattern);
> }
> {code}
>
> does not allow for underscore (and other regex special characters) in the
> parameter name. I could not find any documentation that describes limits on
> the characters that can be used in rest templates.
> Our production code has many, many rest routes with many parameters with
> underscores in them.
> I will prepare a PR with a proposed fix
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20771) camel-jbang - Does not hot-reload java source changes
[ https://issues.apache.org/jira/browse/CAMEL-20771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20771. - Resolution: Fixed > camel-jbang - Does not hot-reload java source changes > - > > Key: CAMEL-20771 > URL: https://issues.apache.org/jira/browse/CAMEL-20771 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.1.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.3, 4.7.0 > > > If you run in --dev mode then .java camel routes does not update on save > changes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20771) camel-jbang - Does not hot-reload java source changes
Claus Ibsen created CAMEL-20771: --- Summary: camel-jbang - Does not hot-reload java source changes Key: CAMEL-20771 URL: https://issues.apache.org/jira/browse/CAMEL-20771 Project: Camel Issue Type: Bug Components: camel-jbang Affects Versions: 4.1.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.4.3, 4.7.0 If you run in --dev mode then .java camel routes does not update on save changes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20653) kotlin-dsl: flaky build due to Kotlin DSL
[
https://issues.apache.org/jira/browse/CAMEL-20653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846303#comment-17846303
]
Claus Ibsen commented on CAMEL-20653:
-
Why is it looking for idea ? that is a editor.
> kotlin-dsl: flaky build due to Kotlin DSL
> -
>
> Key: CAMEL-20653
> URL: https://issues.apache.org/jira/browse/CAMEL-20653
> Project: Camel
> Issue Type: Task
> Components: build system, dsl
>Affects Versions: 4.6.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.x
>
>
> Builds with Maven Daemon seem to fail quite often due to Kotlin issues such
> as:
>
> {code:java}
> [ERROR] Failed to execute goal
> org.jetbrains.kotlin:kotlin-maven-plugin:1.9.23:compile (compile) on project
> camel-kotlin-api: Compilation failure
> [ERROR] java.lang.RuntimeException: Could not find installation home path.
> Please make sure bin/idea.properties is present in the installation directory.
> {code}
>
> Trying to build it with maven seems to work OK.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20763) Rest template with underscore fails after Camel 4.2.0
[
https://issues.apache.org/jira/browse/CAMEL-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20763:
Fix Version/s: 4.7.0
> Rest template with underscore fails after Camel 4.2.0
> -
>
> Key: CAMEL-20763
> URL: https://issues.apache.org/jira/browse/CAMEL-20763
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.2.0
> Environment: Camel 4.2.0 or later
>Reporter: Dave Riseley
>Priority: Minor
> Fix For: 4.7.0
>
>
> We have a camel route, which in it's simplified form looks like this:
> {code:java}
> @Component
> public class CamelRouteBuilder extends RouteBuilder{
> @Override
> public void configure() throws Exception {
> restConfiguration().component("servlet");
> rest("/hello")
> .get("/{first_name}")
> .to("direct:helloworld");
> from("direct:helloworld")
> .transform()
> .simple("Hi ${header.first_name}");
> }
> }
> {code}
> This works fine on Spring Boot 3.1.11 / Camel 4.0.5 . When we upgrade to
> Camel 4.2.0 or later, it fails on startup with the following exception:
>
> {code:java}
> Caused by: java.util.regex.PatternSyntaxException: named capturing group is
> missing trailing '>' near index 17
> \/hello\/(?[^\/]+)
> ^
> at java.base/java.util.regex.Pattern.error(Pattern.java:2028) ~[na:na]
> at java.base/java.util.regex.Pattern.groupname(Pattern.java:2945)
> ~[na:na]
> at java.base/java.util.regex.Pattern.group0(Pattern.java:2990)
> ~[na:na]
> at java.base/java.util.regex.Pattern.sequence(Pattern.java:2124)
> ~[na:na]
> at java.base/java.util.regex.Pattern.expr(Pattern.java:2069) ~[na:na]
> at java.base/java.util.regex.Pattern.compile(Pattern.java:1783)
> ~[na:na]
> at java.base/java.util.regex.Pattern.(Pattern.java:1430)
> ~[na:na]
> at java.base/java.util.regex.Pattern.compile(Pattern.java:1069)
> ~[na:na]
> at
> org.apache.camel.support.RestConsumerContextPathMatcher.register(RestConsumerContextPathMatcher.java:255)
> ~[camel-support-4.2.0.jar:4.2.0]
> at
> org.apache.camel.http.common.CamelServlet.connect(CamelServlet.java:424)
> ~[camel-http-common-4.2.0.jar:4.2.0]
> at
> org.apache.camel.component.servlet.CamelHttpTransportServlet.connect(CamelHttpTransportServlet.java:100)
> ~[camel-servlet-4.2.0.jar:4.2.0]
>
> {code}
> I believe this is due to a change introduced by
> https://issues.apache.org/jira/browse/CAMEL-8306 in which the following
> method:
> {code:java}
> /**
> * Pre-compiled consumer path for wildcard match
> *
> * @param consumerPath a consumer path
> */
> public static void register(String consumerPath) {
> // Convert URI template to a regex pattern
> String regex = consumerPath
> .replace("/", "\\/")
> .replace("{", "(?<")
> .replace("}", ">[^\\/]+)");
> // Add support for wildcard * as path suffix
> regex = regex.replace("*", ".*");
> // Match the provided path against the regex pattern
> Pattern pattern = Pattern.compile(regex);
> PATH_PATTERN.put(consumerPath, pattern);
> }
> {code}
>
> does not allow for underscore (and other regex special characters) in the
> parameter name. I could not find any documentation that describes limits on
> the characters that can be used in rest templates.
> Our production code has many, many rest routes with many parameters with
> underscores in them.
> I will prepare a PR with a proposed fix
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20768) camel-spring-redis - SpringRedisIdempotentRepository flushes DB on start
[
https://issues.apache.org/jira/browse/CAMEL-20768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20768:
Fix Version/s: 4.7.0
> camel-spring-redis - SpringRedisIdempotentRepository flushes DB on start
>
>
> Key: CAMEL-20768
> URL: https://issues.apache.org/jira/browse/CAMEL-20768
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-redis
>Affects Versions: 4.5.0, 4.6.0
>Reporter: Dylan Piergies
>Priority: Major
> Fix For: 4.7.0
>
>
> The {{SpringRedisIdempotentRepository}} class executes the statement
> {{this.redisTemplate.getConnectionFactory().getConnection().flushDb();}}
> within its {{doStart}} method.
> This behaviour does not seem safe or desirable, since the DB may be in use by
> other applications, or by replicas of a single application.
> It seems that a restart of the application or a scale-up event would cause
> the idempotency DB to be lost, which somewhat defeats the point of using a
> centralised cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20768) camel-spring-redis - SpringRedisIdempotentRepository flushes DB on start
[
https://issues.apache.org/jira/browse/CAMEL-20768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846299#comment-17846299
]
Claus Ibsen commented on CAMEL-20768:
-
Yeah you are welcome to work on a PR for main branch.
We could add an option to turn this on|off, and then leave it off by default
(safer).
> camel-spring-redis - SpringRedisIdempotentRepository flushes DB on start
>
>
> Key: CAMEL-20768
> URL: https://issues.apache.org/jira/browse/CAMEL-20768
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-redis
>Affects Versions: 4.5.0, 4.6.0
>Reporter: Dylan Piergies
>Priority: Major
> Fix For: 4.7.0
>
>
> The {{SpringRedisIdempotentRepository}} class executes the statement
> {{this.redisTemplate.getConnectionFactory().getConnection().flushDb();}}
> within its {{doStart}} method.
> This behaviour does not seem safe or desirable, since the DB may be in use by
> other applications, or by replicas of a single application.
> It seems that a restart of the application or a scale-up event would cause
> the idempotency DB to be lost, which somewhat defeats the point of using a
> centralised cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20767) camel-spring-redis - Creating SpringRedisIdempotentRepository via SB should be possible
[ https://issues.apache.org/jira/browse/CAMEL-20767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846282#comment-17846282 ] Claus Ibsen commented on CAMEL-20767: - Can you create a new JIRA ticket > camel-spring-redis - Creating SpringRedisIdempotentRepository via SB should > be possible > --- > > Key: CAMEL-20767 > URL: https://issues.apache.org/jira/browse/CAMEL-20767 > Project: Camel > Issue Type: Bug > Components: camel-spring-redis >Affects Versions: 4.5.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > https://github.com/apache/camel/pull/13491#pullrequestreview-2054565755 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20767) camel-spring-redis - Creating SpringRedisIdempotentRepository via SB should be possible
[ https://issues.apache.org/jira/browse/CAMEL-20767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20767: Component/s: camel-spring-redis > camel-spring-redis - Creating SpringRedisIdempotentRepository via SB should > be possible > --- > > Key: CAMEL-20767 > URL: https://issues.apache.org/jira/browse/CAMEL-20767 > Project: Camel > Issue Type: Bug > Components: camel-spring-redis >Affects Versions: 4.5.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > https://github.com/apache/camel/pull/13491#pullrequestreview-2054565755 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20767) camel-spring-redis - Creating SpringRedisIdempotentRepository via SB should be possible
[ https://issues.apache.org/jira/browse/CAMEL-20767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20767. - Resolution: Fixed > camel-spring-redis - Creating SpringRedisIdempotentRepository via SB should > be possible > --- > > Key: CAMEL-20767 > URL: https://issues.apache.org/jira/browse/CAMEL-20767 > Project: Camel > Issue Type: Bug >Affects Versions: 4.5.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > https://github.com/apache/camel/pull/13491#pullrequestreview-2054565755 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20767) camel-spring-redis - Creating SpringRedisIdempotentRepository via SB should be possible
Claus Ibsen created CAMEL-20767: --- Summary: camel-spring-redis - Creating SpringRedisIdempotentRepository via SB should be possible Key: CAMEL-20767 URL: https://issues.apache.org/jira/browse/CAMEL-20767 Project: Camel Issue Type: Bug Affects Versions: 4.5.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.7.0 https://github.com/apache/camel/pull/13491#pullrequestreview-2054565755 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20766) camel-core - Running in dev mode should turn on JMX updateRouteEnabled
[ https://issues.apache.org/jira/browse/CAMEL-20766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846243#comment-17846243 ] Claus Ibsen commented on CAMEL-20766: - CEQ needs to fix this https://github.com/apache/camel-quarkus/issues/6083 > camel-core - Running in dev mode should turn on JMX updateRouteEnabled > -- > > Key: CAMEL-20766 > URL: https://issues.apache.org/jira/browse/CAMEL-20766 > Project: Camel > Issue Type: Improvement > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > https://camel.apache.org/manual/jmx.html > This makes it easier and possible to update routes via jmx such as hawtio > when running in dev mode -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20766) camel-core - Running in dev mode should turn on JMX updateRouteEnabled
[ https://issues.apache.org/jira/browse/CAMEL-20766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20766. - Resolution: Fixed This was already done, but made configuring dev mode easier for CEQ and CSB > camel-core - Running in dev mode should turn on JMX updateRouteEnabled > -- > > Key: CAMEL-20766 > URL: https://issues.apache.org/jira/browse/CAMEL-20766 > Project: Camel > Issue Type: Improvement > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > https://camel.apache.org/manual/jmx.html > This makes it easier and possible to update routes via jmx such as hawtio > when running in dev mode -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20766) camel-core - Running in dev mode should turn on JMX updateRouteEnabled
[ https://issues.apache.org/jira/browse/CAMEL-20766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20766: --- Assignee: Claus Ibsen > camel-core - Running in dev mode should turn on JMX updateRouteEnabled > -- > > Key: CAMEL-20766 > URL: https://issues.apache.org/jira/browse/CAMEL-20766 > Project: Camel > Issue Type: Improvement > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > https://camel.apache.org/manual/jmx.html > This makes it easier and possible to update routes via jmx such as hawtio > when running in dev mode -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20760) camel-core - Allow to turn on|off RMI connector for tooling based debuggers
[ https://issues.apache.org/jira/browse/CAMEL-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20760. - Resolution: Fixed > camel-core - Allow to turn on|off RMI connector for tooling based debuggers > --- > > Key: CAMEL-20760 > URL: https://issues.apache.org/jira/browse/CAMEL-20760 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > When using camel-debug then RMI connector is in use for remote tooling such > as IDEA / VSCode etc. We should make this configurable and also the RMI port > number -- This message was sent by Atlassian Jira (v8.20.10#820010)
