[jira] [Assigned] (CAMEL-20590) Delay to execute timeout to Camel RabbitMQ (InOut)
[
https://issues.apache.org/jira/browse/CAMEL-20590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhuan Rocha reassigned CAMEL-20590:
---
Assignee: Rhuan Rocha
> Delay to execute timeout to Camel RabbitMQ (InOut)
> --
>
> Key: CAMEL-20590
> URL: https://issues.apache.org/jira/browse/CAMEL-20590
> Project: Camel
> Issue Type: Improvement
> Components: camel-rabbitmq
>Affects Versions: 3.20.0, 3.21.0
>Reporter: Rhuan Rocha
>Assignee: Rhuan Rocha
>Priority: Major
>
> I'm utilizing the camel-rabbitmq component to send messages to RabbitMQ with
> a specified timeout. However, I've observed that the timeout response is
> delayed. Upon debugging the Camel code
> ([https://github.com/apache/camel/blob/camel-3.21.x/components/camel-rabbitmq/src/main/java/org/apache/camel/component/rabbitmq/reply/ReplyManagerSupport.java#L217]),
> I discovered that this delay is caused by a specific line of code that
> performs a {{get}} operation on a map. This map internally uses a
> {{{}ReentrantLock{}}}, which is contributing to the delay. I think it is not
> a bug, but I think it can be improved. I propose developing a 'contains'
> method that operates without the need for locking. I'm trying to reproduce it
> outside my application and inside a simple POC.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20590) Delay to execute timeout to Camel RabbitMQ (InOut)
Rhuan Rocha created CAMEL-20590:
---
Summary: Delay to execute timeout to Camel RabbitMQ (InOut)
Key: CAMEL-20590
URL: https://issues.apache.org/jira/browse/CAMEL-20590
Project: Camel
Issue Type: Improvement
Components: camel-rabbitmq
Affects Versions: 3.21.0, 3.20.0
Reporter: Rhuan Rocha
I'm utilizing the camel-rabbitmq component to send messages to RabbitMQ with a
specified timeout. However, I've observed that the timeout response is delayed.
Upon debugging the Camel code
([https://github.com/apache/camel/blob/camel-3.21.x/components/camel-rabbitmq/src/main/java/org/apache/camel/component/rabbitmq/reply/ReplyManagerSupport.java#L217]),
I discovered that this delay is caused by a specific line of code that
performs a {{get}} operation on a map. This map internally uses a
{{{}ReentrantLock{}}}, which is contributing to the delay. I think it is not a
bug, but I think it can be improved. I propose developing a 'contains' method
that operates without the need for locking. I'm trying to reproduce it outside
my application and inside a simple POC.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20589) camel-jbang - Make it easy to run activemq with vm transport
Claus Ibsen created CAMEL-20589:
---
Summary: camel-jbang - Make it easy to run activemq with vm
transport
Key: CAMEL-20589
URL: https://issues.apache.org/jira/browse/CAMEL-20589
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Fix For: 4.x
camel-activemq uses tcp:localhost:61616 by default, but we should make it
possible to run via vm embedded instead
camel run
https://github.com/apache/camel/blob/camel-1.0.0/examples/camel-example-spring/src/main/java/org/apache/camel/example/spring/MyRouteBuilder.java
--prop=camel.component.activemq.brokerUrl=vm://localhost
However I get an error
2024-03-20 22:20:33.743 ERROR 11245 --- [r[test.MyQueue]]
.DefaultJmsMessageListenerContainer : Could not refresh JMS Connection for
destination 'test.MyQueue' - retrying using FixedBackOff{interval=5000,
currentAttempts=1, maxAttempts=unlimited}. Cause: Could not create Transport.
Reason: java.io.IOException: Transport scheme NOT recognized: [vm]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20588) camel-salesforce: java.lang.IllegalArgumentException: Request header too large Exception
[
https://issues.apache.org/jira/browse/CAMEL-20588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20588.
-
Resolution: Fixed
> camel-salesforce: java.lang.IllegalArgumentException: Request header too
> large Exception
>
>
> Key: CAMEL-20588
> URL: https://issues.apache.org/jira/browse/CAMEL-20588
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 4.4.0
>Reporter: David Lappert
>Priority: Minor
> Fix For: 4.4.2, 4.5.0
>
>
> *Summary*
> The Set-Cookie "Expires" cookie attribute is being incorrectly parsed by the
> version *8.0.0.beta1* *cometd-java-client-http-jetty* library. This results
> in the header growing indefinitely, eventually leading to a
> "java.lang.IllegalArgumentException: Request header too large Exception"
> being thrown by Salesforce. This issue seems to have been resolved in
> *8.0.0.beta2* by this PR: [https://github.com/cometd/cometd/pull/1631]
>
> *Root Cause*
> The issue stems from the use of the *HttpField.getValueList* method, and its
> use of the *QuotedCSV* class that extends {*}QuotedCSVParser{*}, see
> {*}JettyHttpClientTransport.java:238{*}.
>
> *Artifacts*
> * [https://github.com/cometd/cometd/issues/1600]
> * [https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.1]
>
> *Resolution*
> Explicitly pinning to the following version of
> *cometd-java-client-http-jetty* fixes the issue related to the "Expires"
> attribute being incorrectly parsed.
>
> {code:java}
>
> org.cometd.java
> cometd-java-client-http-jetty
> 8.0.0.beta2
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20588) camel-salesforce: java.lang.IllegalArgumentException: Request header too large Exception
[
https://issues.apache.org/jira/browse/CAMEL-20588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829261#comment-17829261
]
David Lappert commented on CAMEL-20588:
---
[~davsclaus] I've opened a PR against the camel-4.4.x branch, see:
[https://github.com/apache/camel/pull/13555]
> camel-salesforce: java.lang.IllegalArgumentException: Request header too
> large Exception
>
>
> Key: CAMEL-20588
> URL: https://issues.apache.org/jira/browse/CAMEL-20588
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 4.4.0
>Reporter: David Lappert
>Priority: Minor
> Fix For: 4.4.2, 4.5.0
>
>
> *Summary*
> The Set-Cookie "Expires" cookie attribute is being incorrectly parsed by the
> version *8.0.0.beta1* *cometd-java-client-http-jetty* library. This results
> in the header growing indefinitely, eventually leading to a
> "java.lang.IllegalArgumentException: Request header too large Exception"
> being thrown by Salesforce. This issue seems to have been resolved in
> *8.0.0.beta2* by this PR: [https://github.com/cometd/cometd/pull/1631]
>
> *Root Cause*
> The issue stems from the use of the *HttpField.getValueList* method, and its
> use of the *QuotedCSV* class that extends {*}QuotedCSVParser{*}, see
> {*}JettyHttpClientTransport.java:238{*}.
>
> *Artifacts*
> * [https://github.com/cometd/cometd/issues/1600]
> * [https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.1]
>
> *Resolution*
> Explicitly pinning to the following version of
> *cometd-java-client-http-jetty* fixes the issue related to the "Expires"
> attribute being incorrectly parsed.
>
> {code:java}
>
> org.cometd.java
> cometd-java-client-http-jetty
> 8.0.0.beta2
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20588) camel-salesforce: java.lang.IllegalArgumentException: Request header too large Exception
[
https://issues.apache.org/jira/browse/CAMEL-20588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20588:
Fix Version/s: 4.4.2
> camel-salesforce: java.lang.IllegalArgumentException: Request header too
> large Exception
>
>
> Key: CAMEL-20588
> URL: https://issues.apache.org/jira/browse/CAMEL-20588
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 4.4.0
>Reporter: David Lappert
>Priority: Minor
> Fix For: 4.4.2, 4.5.0
>
>
> *Summary*
> The Set-Cookie "Expires" cookie attribute is being incorrectly parsed by the
> version *8.0.0.beta1* *cometd-java-client-http-jetty* library. This results
> in the header growing indefinitely, eventually leading to a
> "java.lang.IllegalArgumentException: Request header too large Exception"
> being thrown by Salesforce. This issue seems to have been resolved in
> *8.0.0.beta2* by this PR: [https://github.com/cometd/cometd/pull/1631]
>
> *Root Cause*
> The issue stems from the use of the *HttpField.getValueList* method, and its
> use of the *QuotedCSV* class that extends {*}QuotedCSVParser{*}, see
> {*}JettyHttpClientTransport.java:238{*}.
>
> *Artifacts*
> * [https://github.com/cometd/cometd/issues/1600]
> * [https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.1]
>
> *Resolution*
> Explicitly pinning to the following version of
> *cometd-java-client-http-jetty* fixes the issue related to the "Expires"
> attribute being incorrectly parsed.
>
> {code:java}
>
> org.cometd.java
> cometd-java-client-http-jetty
> 8.0.0.beta2
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20588) camel-salesforce: java.lang.IllegalArgumentException: Request header too large Exception
[
https://issues.apache.org/jira/browse/CAMEL-20588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829229#comment-17829229
]
Claus Ibsen commented on CAMEL-20588:
-
Ah okay we have upgraded to beta2 for 4.5.0. For 4.4.x you can send a PR to
upgrade it, see parent/pom.xml file.
> camel-salesforce: java.lang.IllegalArgumentException: Request header too
> large Exception
>
>
> Key: CAMEL-20588
> URL: https://issues.apache.org/jira/browse/CAMEL-20588
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 4.4.0
>Reporter: David Lappert
>Priority: Minor
> Fix For: 4.5.0
>
>
> *Summary*
> The Set-Cookie "Expires" cookie attribute is being incorrectly parsed by the
> version *8.0.0.beta1* *cometd-java-client-http-jetty* library. This results
> in the header growing indefinitely, eventually leading to a
> "java.lang.IllegalArgumentException: Request header too large Exception"
> being thrown by Salesforce. This issue seems to have been resolved in
> *8.0.0.beta2* by this PR: [https://github.com/cometd/cometd/pull/1631]
>
> *Root Cause*
> The issue stems from the use of the *HttpField.getValueList* method, and its
> use of the *QuotedCSV* class that extends {*}QuotedCSVParser{*}, see
> {*}JettyHttpClientTransport.java:238{*}.
>
> *Artifacts*
> * [https://github.com/cometd/cometd/issues/1600]
> * [https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.1]
>
> *Resolution*
> Explicitly pinning to the following version of
> *cometd-java-client-http-jetty* fixes the issue related to the "Expires"
> attribute being incorrectly parsed.
>
> {code:java}
>
> org.cometd.java
> cometd-java-client-http-jetty
> 8.0.0.beta2
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20588) camel-salesforce: java.lang.IllegalArgumentException: Request header too large Exception
[
https://issues.apache.org/jira/browse/CAMEL-20588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20588:
Fix Version/s: 4.5.0
> camel-salesforce: java.lang.IllegalArgumentException: Request header too
> large Exception
>
>
> Key: CAMEL-20588
> URL: https://issues.apache.org/jira/browse/CAMEL-20588
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 4.4.0
>Reporter: David Lappert
>Priority: Minor
> Fix For: 4.5.0
>
>
> *Summary*
> The Set-Cookie "Expires" cookie attribute is being incorrectly parsed by the
> version *8.0.0.beta1* *cometd-java-client-http-jetty* library. This results
> in the header growing indefinitely, eventually leading to a
> "java.lang.IllegalArgumentException: Request header too large Exception"
> being thrown by Salesforce. This issue seems to have been resolved in
> *8.0.0.beta2* by this PR: [https://github.com/cometd/cometd/pull/1631]
>
> *Root Cause*
> The issue stems from the use of the *HttpField.getValueList* method, and its
> use of the *QuotedCSV* class that extends {*}QuotedCSVParser{*}, see
> {*}JettyHttpClientTransport.java:238{*}.
>
> *Artifacts*
> * [https://github.com/cometd/cometd/issues/1600]
> * [https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.1]
>
> *Resolution*
> Explicitly pinning to the following version of
> *cometd-java-client-http-jetty* fixes the issue related to the "Expires"
> attribute being incorrectly parsed.
>
> {code:java}
>
> org.cometd.java
> cometd-java-client-http-jetty
> 8.0.0.beta2
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20588) camel-salesforce: java.lang.IllegalArgumentException: Request header too large Exception
[
https://issues.apache.org/jira/browse/CAMEL-20588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829227#comment-17829227
]
Claus Ibsen commented on CAMEL-20588:
-
What does it use now? And are you able to send a PR to fix this
> camel-salesforce: java.lang.IllegalArgumentException: Request header too
> large Exception
>
>
> Key: CAMEL-20588
> URL: https://issues.apache.org/jira/browse/CAMEL-20588
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 4.4.0
>Reporter: David Lappert
>Priority: Minor
>
> *Summary*
> The Set-Cookie "Expires" cookie attribute is being incorrectly parsed by the
> version *8.0.0.beta1* *cometd-java-client-http-jetty* library. This results
> in the header growing indefinitely, eventually leading to a
> "java.lang.IllegalArgumentException: Request header too large Exception"
> being thrown by Salesforce. This issue seems to have been resolved in
> *8.0.0.beta2* by this PR: [https://github.com/cometd/cometd/pull/1631]
>
> *Root Cause*
> The issue stems from the use of the *HttpField.getValueList* method, and its
> use of the *QuotedCSV* class that extends {*}QuotedCSVParser{*}, see
> {*}JettyHttpClientTransport.java:238{*}.
>
> *Artifacts*
> * [https://github.com/cometd/cometd/issues/1600]
> * [https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.1]
>
> *Resolution*
> Explicitly pinning to the following version of
> *cometd-java-client-http-jetty* fixes the issue related to the "Expires"
> attribute being incorrectly parsed.
>
> {code:java}
>
> org.cometd.java
> cometd-java-client-http-jetty
> 8.0.0.beta2
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20458) Writing custom dev console does not work
[ https://issues.apache.org/jira/browse/CAMEL-20458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20458. - Resolution: Fixed > Writing custom dev console does not work > > > Key: CAMEL-20458 > URL: https://issues.apache.org/jira/browse/CAMEL-20458 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-platform-http >Affects Versions: 4.4.0 >Reporter: Ivan Kulaga >Assignee: Ivan Kulaga >Priority: Minor > Labels: help-wanted > Fix For: 4.5.0 > > > There is documentation saying you can write custom @DevConsole: > [https://camel.apache.org/manual/camel-console.html#_writing_custom_dev_consoles] > Tried to copy the example from this documentation and my console was not > discovered: > [https://github.com/kulagaIA/camel-examples/tree/custom-dev-console-not-working] > I believe this happens because this cycle in > org.apache.camel.maven.packaging.SpiGeneratorMojo.java does not work as > intended: > [https://github.com/apache/camel/blob/1b8d9827dcb82e899cc5b0740f4ba9fff6b65029/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SpiGeneratorMojo.java#L120] > It iterates specifically over @ServiceFactory annotations, while the logic > suggests it should also iterate over any annotation that is itself annotated > with @ServiceFactory . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20578) generated configurer should use lower case first-char name
[ https://issues.apache.org/jira/browse/CAMEL-20578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20578. - Resolution: Fixed > generated configurer should use lower case first-char name > -- > > Key: CAMEL-20578 > URL: https://issues.apache.org/jira/browse/CAMEL-20578 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.5.0 > > > case "CacheSize": target.setCacheSize(property(camelContext, > int.class, value)); return true; > should be > case "cacheSize": target.setCacheSize(property(camelContext, > int.class, value)); return true; -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20588) camel-salesforce: java.lang.IllegalArgumentException: Request header too large Exception
[
https://issues.apache.org/jira/browse/CAMEL-20588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Lappert updated CAMEL-20588:
--
Priority: Minor (was: Major)
> camel-salesforce: java.lang.IllegalArgumentException: Request header too
> large Exception
>
>
> Key: CAMEL-20588
> URL: https://issues.apache.org/jira/browse/CAMEL-20588
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 4.4.0
>Reporter: David Lappert
>Priority: Minor
>
> *Summary*
> The Set-Cookie "Expires" cookie attribute is being incorrectly parsed by the
> version *8.0.0.beta1* *cometd-java-client-http-jetty* library. This results
> in the header growing indefinitely, eventually leading to a
> "java.lang.IllegalArgumentException: Request header too large Exception"
> being thrown by Salesforce. This issue seems to have been resolved in
> *8.0.0.beta2* by this PR: [https://github.com/cometd/cometd/pull/1631]
>
> *Root Cause*
> The issue stems from the use of the *HttpField.getValueList* method, and its
> use of the *QuotedCSV* class that extends {*}QuotedCSVParser{*}, see
> {*}JettyHttpClientTransport.java:238{*}.
>
> *Artifacts*
> * [https://github.com/cometd/cometd/issues/1600]
> * [https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.1]
>
> *Resolution*
> Explicitly pinning to the following version of
> *cometd-java-client-http-jetty* fixes the issue related to the "Expires"
> attribute being incorrectly parsed.
>
> {code:java}
>
> org.cometd.java
> cometd-java-client-http-jetty
> 8.0.0.beta2
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20588) camel-salesforce: java.lang.IllegalArgumentException: Request header too large Exception
David Lappert created CAMEL-20588:
-
Summary: camel-salesforce: java.lang.IllegalArgumentException:
Request header too large Exception
Key: CAMEL-20588
URL: https://issues.apache.org/jira/browse/CAMEL-20588
Project: Camel
Issue Type: Bug
Components: camel-salesforce
Affects Versions: 4.4.0
Reporter: David Lappert
*Summary*
The Set-Cookie "Expires" cookie attribute is being incorrectly parsed by the
version *8.0.0.beta1* *cometd-java-client-http-jetty* library. This results in
the header growing indefinitely, eventually leading to a
"java.lang.IllegalArgumentException: Request header too large Exception" being
thrown by Salesforce. This issue seems to have been resolved in *8.0.0.beta2*
by this PR: [https://github.com/cometd/cometd/pull/1631]
*Root Cause*
The issue stems from the use of the *HttpField.getValueList* method, and its
use of the *QuotedCSV* class that extends {*}QuotedCSVParser{*}, see
{*}JettyHttpClientTransport.java:238{*}.
*Artifacts*
* [https://github.com/cometd/cometd/issues/1600]
* [https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.1]
*Resolution*
Explicitly pinning to the following version of *cometd-java-client-http-jetty*
fixes the issue related to the "Expires" attribute being incorrectly parsed.
{code:java}
org.cometd.java
cometd-java-client-http-jetty
8.0.0.beta2
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20578) generated configurer should use lower case first-char name
[ https://issues.apache.org/jira/browse/CAMEL-20578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829217#comment-17829217 ] Claus Ibsen commented on CAMEL-20578: - Yes I think its some recent code changes that causes this > generated configurer should use lower case first-char name > -- > > Key: CAMEL-20578 > URL: https://issues.apache.org/jira/browse/CAMEL-20578 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.5.0 > > > case "CacheSize": target.setCacheSize(property(camelContext, > int.class, value)); return true; > should be > case "cacheSize": target.setCacheSize(property(camelContext, > int.class, value)); return true; -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20578) generated configurer should use lower case first-char name
[ https://issues.apache.org/jira/browse/CAMEL-20578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20578: --- Assignee: Claus Ibsen > generated configurer should use lower case first-char name > -- > > Key: CAMEL-20578 > URL: https://issues.apache.org/jira/browse/CAMEL-20578 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.5.0 > > > case "CacheSize": target.setCacheSize(property(camelContext, > int.class, value)); return true; > should be > case "cacheSize": target.setCacheSize(property(camelContext, > int.class, value)); return true; -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20577) Spring Beans XML Camel context duplicates rest routes defined in java or xml-io DSL
[ https://issues.apache.org/jira/browse/CAMEL-20577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Mariani resolved CAMEL-20577. -- Resolution: Fixed > Spring Beans XML Camel context duplicates rest routes defined in java or > xml-io DSL > --- > > Key: CAMEL-20577 > URL: https://issues.apache.org/jira/browse/CAMEL-20577 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Affects Versions: 4.4.1 >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Major > Fix For: 4.4.2, 4.5.0 > > > The Spring Beans XML Camel context tries to add already handled routes to the > camel context route lists, this means that, if I have a java dsl route that > define a rest() or an xml-io-dsl that defines routes, they are > initialized twice when Spring Beans XML Camel context is initialized and the > application cannot start due to duplicated rest routes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20557) camel-rest - Add openapi to rest-dsl so you can expose rest services from existing schema
[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20557:
Fix Version/s: 4.6.0
(was: 4.5.0)
> camel-rest - Add openapi to rest-dsl so you can expose rest services from
> existing schema
> -
>
> Key: CAMEL-20557
> URL: https://issues.apache.org/jira/browse/CAMEL-20557
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, rest
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.6.0
>
>
> rest()
>.openapi("my-schema.json")
> When you want to do contract-first with existing schema, then it would be
> good to make that first-class with rest-dsl, so the schema can be used as-is,
> and let it automatic map to direct:operationId routes like the convention is
> typically.
> The openapi should have same binding mode as rest-dsl, so it can automatic
> map to pojo or back if using json/xml via jackson etc.
> And the api-context can then return the schema file as-is (it may need to
> adjust the server part to be the actual server - like normal rest-dsl can do).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-16660) Hazelcast : tests : create camel-test-infra-Hazelcast
[ https://issues.apache.org/jira/browse/CAMEL-16660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16660. - Resolution: Fixed > Hazelcast : tests : create camel-test-infra-Hazelcast > - > > Key: CAMEL-16660 > URL: https://issues.apache.org/jira/browse/CAMEL-16660 > Project: Camel > Issue Type: Test > Components: camel-hazelcast, tests >Reporter: Zineb Bendhiba >Priority: Minor > Labels: help-wanted > Fix For: 4.5.0 > > > Create camel-test-infra-Hazelcast > Delete mock where it is possible. Update the HazelcastTestSupport to use new > service from camel-test-infra-Hazelcast instead of mocks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-16660) Hazelcast : tests : create camel-test-infra-Hazelcast
[ https://issues.apache.org/jira/browse/CAMEL-16660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16660: Fix Version/s: 4.5.0 > Hazelcast : tests : create camel-test-infra-Hazelcast > - > > Key: CAMEL-16660 > URL: https://issues.apache.org/jira/browse/CAMEL-16660 > Project: Camel > Issue Type: Test > Components: camel-hazelcast, tests >Reporter: Zineb Bendhiba >Priority: Minor > Labels: help-wanted > Fix For: 4.5.0 > > > Create camel-test-infra-Hazelcast > Delete mock where it is possible. Update the HazelcastTestSupport to use new > service from camel-test-infra-Hazelcast instead of mocks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20584) camel-mongo: java driver upgrade causes instabilities
[ https://issues.apache.org/jira/browse/CAMEL-20584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20584: Fix Version/s: 4.x > camel-mongo: java driver upgrade causes instabilities > - > > Key: CAMEL-20584 > URL: https://issues.apache.org/jira/browse/CAMEL-20584 > Project: Camel > Issue Type: Bug > Components: camel-mongodb >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > Fix For: 4.x > > > We found out that upgrading the MongoDB driver from 4.11.1 to 5.0.0 causes > the MongoDbTailableCursorConsumerIT to hang up, which seems to indicate a > problem with tailable cursors support or a problem with the new driver. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20584) camel-mongo: java driver upgrade causes instabilities
[ https://issues.apache.org/jira/browse/CAMEL-20584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20584: Issue Type: Dependency upgrade (was: Bug) > camel-mongo: java driver upgrade causes instabilities > - > > Key: CAMEL-20584 > URL: https://issues.apache.org/jira/browse/CAMEL-20584 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-mongodb >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > Fix For: 4.x > > > We found out that upgrading the MongoDB driver from 4.11.1 to 5.0.0 causes > the MongoDbTailableCursorConsumerIT to hang up, which seems to indicate a > problem with tailable cursors support or a problem with the new driver. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20577) Spring Beans XML Camel context duplicates rest routes defined in java or xml-io DSL
[ https://issues.apache.org/jira/browse/CAMEL-20577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829199#comment-17829199 ] Claus Ibsen commented on CAMEL-20577: - Is this fixed now? > Spring Beans XML Camel context duplicates rest routes defined in java or > xml-io DSL > --- > > Key: CAMEL-20577 > URL: https://issues.apache.org/jira/browse/CAMEL-20577 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Affects Versions: 4.4.1 >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Major > Fix For: 4.4.2, 4.5.0 > > > The Spring Beans XML Camel context tries to add already handled routes to the > camel context route lists, this means that, if I have a java dsl route that > define a rest() or an xml-io-dsl that defines routes, they are > initialized twice when Spring Beans XML Camel context is initialized and the > application cannot start due to duplicated rest routes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20583) Java 21 - Reduce the noise from the ThreadType logger
[ https://issues.apache.org/jira/browse/CAMEL-20583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20583. - Resolution: Fixed > Java 21 - Reduce the noise from the ThreadType logger > - > > Key: CAMEL-20583 > URL: https://issues.apache.org/jira/browse/CAMEL-20583 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.5.0 > > > The virtual thread stuff is experimental and we should only log if its > enabled explicit and otherwise log at DEBUG level the default level in > ThreadType -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20587) Camel-Qdrant: Add a datatype for transforming langchain embeddings in qdrant objects
[ https://issues.apache.org/jira/browse/CAMEL-20587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20587. -- Resolution: Fixed > Camel-Qdrant: Add a datatype for transforming langchain embeddings in qdrant > objects > > > Key: CAMEL-20587 > URL: https://issues.apache.org/jira/browse/CAMEL-20587 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20587) Camel-Qdrant: Add a datatype for transforming langchain embeddings in qdrant objects
Andrea Cosentino created CAMEL-20587: Summary: Camel-Qdrant: Add a datatype for transforming langchain embeddings in qdrant objects Key: CAMEL-20587 URL: https://issues.apache.org/jira/browse/CAMEL-20587 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20576) camel-jbang-plugin-k run command kebab-case parsing invalid
[
https://issues.apache.org/jira/browse/CAMEL-20576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20576:
Fix Version/s: 4.5.0
> camel-jbang-plugin-k run command kebab-case parsing invalid
> ---
>
> Key: CAMEL-20576
> URL: https://issues.apache.org/jira/browse/CAMEL-20576
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.4.0, 4.4.1
> Environment: Jbang version : 0.114.0
> Camel version: 4.4.0
> Camel k: 2.3.0-SNAPSHOT
>Reporter: Gaëlle Fournier
>Assignee: Claudio Miranda
>Priority: Minor
> Fix For: 4.4.2, 4.5.0
>
>
> The run command ignore the kebab-case trait properties.
> The jbang camel k command:
> {code:java}
> $ camel k run files/Java.java -t affinity.enabled=true -t
> "affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"{code}
> will result in the following integration CRD configuration:
> {code:java}
> traits:
> affinity:
> enabled: true
> podAffinity: false
> podAntiAffinity: false{code}
>
> In comparaison the kamel command:
> {code:java}
> $ kamel run files/Java.java -t affinity.enabled=true -t
> "affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"
> {code}
> will result in the following integration CRD configuration:
> {code:java}
> traits:
> affinity:
> enabled: true
> nodeAffinityLabels:
> - kubernetes.io/hostname in(minikube){code}
>
> *Note:* using the camel case in the jbang camel k command should be a
> workaround after fix https://issues.apache.org/jira/browse/CAMEL-20559:
> {code:java}
> $ camel k run files/Java.java -t affinity.enabled=true -t
> affinity.nodeAffinityLabels='kubernetes.io/hostname=minikube'{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20576) camel-jbang-plugin-k run command kebab-case parsing invalid
[
https://issues.apache.org/jira/browse/CAMEL-20576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20576:
Fix Version/s: 4.4.2
> camel-jbang-plugin-k run command kebab-case parsing invalid
> ---
>
> Key: CAMEL-20576
> URL: https://issues.apache.org/jira/browse/CAMEL-20576
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.4.0, 4.4.1
> Environment: Jbang version : 0.114.0
> Camel version: 4.4.0
> Camel k: 2.3.0-SNAPSHOT
>Reporter: Gaëlle Fournier
>Assignee: Claudio Miranda
>Priority: Minor
> Fix For: 4.4.2
>
>
> The run command ignore the kebab-case trait properties.
> The jbang camel k command:
> {code:java}
> $ camel k run files/Java.java -t affinity.enabled=true -t
> "affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"{code}
> will result in the following integration CRD configuration:
> {code:java}
> traits:
> affinity:
> enabled: true
> podAffinity: false
> podAntiAffinity: false{code}
>
> In comparaison the kamel command:
> {code:java}
> $ kamel run files/Java.java -t affinity.enabled=true -t
> "affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"
> {code}
> will result in the following integration CRD configuration:
> {code:java}
> traits:
> affinity:
> enabled: true
> nodeAffinityLabels:
> - kubernetes.io/hostname in(minikube){code}
>
> *Note:* using the camel case in the jbang camel k command should be a
> workaround after fix https://issues.apache.org/jira/browse/CAMEL-20559:
> {code:java}
> $ camel k run files/Java.java -t affinity.enabled=true -t
> affinity.nodeAffinityLabels='kubernetes.io/hostname=minikube'{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20585) Camel-package-maven-plugin: generates test configurers in non-tests artifacts
[
https://issues.apache.org/jira/browse/CAMEL-20585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20585:
Component/s: build system
> Camel-package-maven-plugin: generates test configurers in non-tests artifacts
> -
>
> Key: CAMEL-20585
> URL: https://issues.apache.org/jira/browse/CAMEL-20585
> Project: Camel
> Issue Type: Bug
> Components: build system, camel-package-maven-plugin
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Priority: Major
> Fix For: 4.6.0
>
>
> Change
> [https://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4#diff-8c376760c1f21c10dc4f6b051f972405cc04fc1ce9ca636a478cc5cfb8a1f51c]
> causes that for example _camel-main.jar_ contains test configurers like
> {code:java}
> org.apache.camel.main.MySecondBar, org.apache.camel.main.MySecondFoo| {code}
> As you can see
> herehttps://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4
> different method is called.
>
> The original method was:
> {code:java}
> public static boolean updateResource(BuildContext buildContext, Path out,
> String data) {
> try {
> if (FileUtil.updateFile(out, data)) {
> refresh(buildContext, out);
> return true;
> }
> } catch (IOException e) {
> throw new IOError(e);
> }
> return false;
> {code}
> which can not create a test resource.
> Newly called method
> {code:java}
> protected boolean updateResource(Path dir, String fileName, String data) {
> boolean updated;
> updated = updateResource(buildContext, dir.resolve(fileName), data);
> if (!fileName.endsWith(".java")) {
> > Path outputDir =
> > Paths.get(project.getBuild().getOutputDirectory());
> > updated |= updateResource(buildContext,
> > outputDir.resolve(fileName), data);
> }
> return updated;
> {code}
> refreshes also resources in outputDiectorry. Therefore some test configurers
> are created during build of the artifact.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20586) camel-jbang - Export to CSB can use camel.main.xxx properties
Claus Ibsen created CAMEL-20586: --- Summary: camel-jbang - Export to CSB can use camel.main.xxx properties Key: CAMEL-20586 URL: https://issues.apache.org/jira/browse/CAMEL-20586 Project: Camel Issue Type: Improvement Components: camel-jbang Affects Versions: 4.5.0 Reporter: Claus Ibsen Fix For: 4.6.0 In Camel 4.5 we make it possible to use camel.main.xxx for CSB configuration option that are common in camel. So jbang do not need to transform camel.main.xx to camel.springboot.xxx anymore if running on Camel 4.5 or newer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20585) Camel-package-maven-plugin: generates test configurers in non-tests artifacts
[
https://issues.apache.org/jira/browse/CAMEL-20585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828891#comment-17828891
]
Jiri Ondrusek commented on CAMEL-20585:
---
[~gnodet] FYI
> Camel-package-maven-plugin: generates test configurers in non-tests artifacts
> -
>
> Key: CAMEL-20585
> URL: https://issues.apache.org/jira/browse/CAMEL-20585
> Project: Camel
> Issue Type: Bug
> Components: camel-package-maven-plugin
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Priority: Major
>
> Change
> [https://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4#diff-8c376760c1f21c10dc4f6b051f972405cc04fc1ce9ca636a478cc5cfb8a1f51c]
> causes that for example _camel-main.jar_ contains test configurers like
> {code:java}
> org.apache.camel.main.MySecondBar, org.apache.camel.main.MySecondFoo| {code}
> As you can see
> herehttps://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4
> different method is called.
>
> The original method was:
> {code:java}
> public static boolean updateResource(BuildContext buildContext, Path out,
> String data) {
> try {
> if (FileUtil.updateFile(out, data)) {
> refresh(buildContext, out);
> return true;
> }
> } catch (IOException e) {
> throw new IOError(e);
> }
> return false;
> {code}
> which can not create a test resource.
> Newly called method
> {code:java}
> protected boolean updateResource(Path dir, String fileName, String data) {
> boolean updated;
> updated = updateResource(buildContext, dir.resolve(fileName), data);
> if (!fileName.endsWith(".java")) {
> > Path outputDir =
> > Paths.get(project.getBuild().getOutputDirectory());
> > updated |= updateResource(buildContext,
> > outputDir.resolve(fileName), data);
> }
> return updated;
> {code}
> refreshes also resources in outputDiectorry. Therefore some test configurers
> are created during build of the artifact.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20576) camel-jbang-plugin-k run command kebab-case parsing invalid
[
https://issues.apache.org/jira/browse/CAMEL-20576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claudio Miranda resolved CAMEL-20576.
-
Resolution: Fixed
> camel-jbang-plugin-k run command kebab-case parsing invalid
> ---
>
> Key: CAMEL-20576
> URL: https://issues.apache.org/jira/browse/CAMEL-20576
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.4.0, 4.4.1
> Environment: Jbang version : 0.114.0
> Camel version: 4.4.0
> Camel k: 2.3.0-SNAPSHOT
>Reporter: Gaëlle Fournier
>Assignee: Claudio Miranda
>Priority: Minor
>
> The run command ignore the kebab-case trait properties.
> The jbang camel k command:
> {code:java}
> $ camel k run files/Java.java -t affinity.enabled=true -t
> "affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"{code}
> will result in the following integration CRD configuration:
> {code:java}
> traits:
> affinity:
> enabled: true
> podAffinity: false
> podAntiAffinity: false{code}
>
> In comparaison the kamel command:
> {code:java}
> $ kamel run files/Java.java -t affinity.enabled=true -t
> "affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"
> {code}
> will result in the following integration CRD configuration:
> {code:java}
> traits:
> affinity:
> enabled: true
> nodeAffinityLabels:
> - kubernetes.io/hostname in(minikube){code}
>
> *Note:* using the camel case in the jbang camel k command should be a
> workaround after fix https://issues.apache.org/jira/browse/CAMEL-20559:
> {code:java}
> $ camel k run files/Java.java -t affinity.enabled=true -t
> affinity.nodeAffinityLabels='kubernetes.io/hostname=minikube'{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20585) Camel-package-maven-plugin: generates test configurers in non-tests artifacts
Jiri Ondrusek created CAMEL-20585:
-
Summary: Camel-package-maven-plugin: generates test configurers in
non-tests artifacts
Key: CAMEL-20585
URL: https://issues.apache.org/jira/browse/CAMEL-20585
Project: Camel
Issue Type: Bug
Components: camel-package-maven-plugin
Affects Versions: 4.5.0
Reporter: Jiri Ondrusek
Change
[https://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4#diff-8c376760c1f21c10dc4f6b051f972405cc04fc1ce9ca636a478cc5cfb8a1f51c]
causes that for example _camel-main.jar_ contains test configurers like
{code:java}
org.apache.camel.main.MySecondBar, org.apache.camel.main.MySecondFoo| {code}
As you can see
herehttps://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4
different method is called.
The original method was:
{code:java}
public static boolean updateResource(BuildContext buildContext, Path out,
String data) {
try {
if (FileUtil.updateFile(out, data)) {
refresh(buildContext, out);
return true;
}
} catch (IOException e) {
throw new IOError(e);
}
return false;
{code}
which can not create a test resource.
Newly called method
{code:java}
protected boolean updateResource(Path dir, String fileName, String data) {
boolean updated;
updated = updateResource(buildContext, dir.resolve(fileName), data);
if (!fileName.endsWith(".java")) {
> Path outputDir =
> Paths.get(project.getBuild().getOutputDirectory());
> updated |= updateResource(buildContext,
> outputDir.resolve(fileName), data);
}
return updated;
{code}
refreshes also resources in outputDiectorry. Therefore some test configurers
are created during build of the artifact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20384) modernization: modernize map operations
[ https://issues.apache.org/jira/browse/CAMEL-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-20384: - Fix Version/s: 4.4.0 (was: 4.x) > modernization: modernize map operations > --- > > Key: CAMEL-20384 > URL: https://issues.apache.org/jira/browse/CAMEL-20384 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > Fix For: 4.4.0 > > > Use more modern map operations (see below) where this could lead to cleaner > code. Check this list for outdated map usages: > https://sonarcloud.io/project/issues?resolved=false=java%3AS3824=apache_camel > Modern map operations: > * putIfAbsent > * computeIfPresent > * computeIfAbsent > * compute > Note: be careful with changing code in `core` as it could be part of the hot > path, and it needs closer inspection. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17641) camel-catalog - Generate metadata for all known implementations of camel SPI interfaces
[ https://issues.apache.org/jira/browse/CAMEL-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17641. - Resolution: Fixed > camel-catalog - Generate metadata for all known implementations of camel SPI > interfaces > --- > > Key: CAMEL-17641 > URL: https://issues.apache.org/jira/browse/CAMEL-17641 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > For example AggregationStrategy can have a set of OOTB impls, and it would be > good to know what we have in camel. > We can make this metadata generated per component then it can be isolated per > component you use - and maybe also have this in the camel-catalog so we have > a single place to look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20585) Camel-package-maven-plugin: generates test configurers in non-tests artifacts
[
https://issues.apache.org/jira/browse/CAMEL-20585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828918#comment-17828918
]
Jiri Ondrusek commented on CAMEL-20585:
---
I reverted the code causing problem in this PR (as a quick fix):
https://github.com/apache/camel/pull/13549
> Camel-package-maven-plugin: generates test configurers in non-tests artifacts
> -
>
> Key: CAMEL-20585
> URL: https://issues.apache.org/jira/browse/CAMEL-20585
> Project: Camel
> Issue Type: Bug
> Components: camel-package-maven-plugin
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Priority: Major
>
> Change
> [https://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4#diff-8c376760c1f21c10dc4f6b051f972405cc04fc1ce9ca636a478cc5cfb8a1f51c]
> causes that for example _camel-main.jar_ contains test configurers like
> {code:java}
> org.apache.camel.main.MySecondBar, org.apache.camel.main.MySecondFoo| {code}
> As you can see
> herehttps://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4
> different method is called.
>
> The original method was:
> {code:java}
> public static boolean updateResource(BuildContext buildContext, Path out,
> String data) {
> try {
> if (FileUtil.updateFile(out, data)) {
> refresh(buildContext, out);
> return true;
> }
> } catch (IOException e) {
> throw new IOError(e);
> }
> return false;
> {code}
> which can not create a test resource.
> Newly called method
> {code:java}
> protected boolean updateResource(Path dir, String fileName, String data) {
> boolean updated;
> updated = updateResource(buildContext, dir.resolve(fileName), data);
> if (!fileName.endsWith(".java")) {
> > Path outputDir =
> > Paths.get(project.getBuild().getOutputDirectory());
> > updated |= updateResource(buildContext,
> > outputDir.resolve(fileName), data);
> }
> return updated;
> {code}
> refreshes also resources in outputDiectorry. Therefore some test configurers
> are created during build of the artifact.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20585) Camel-package-maven-plugin: generates test configurers in non-tests artifacts
[
https://issues.apache.org/jira/browse/CAMEL-20585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20585:
Fix Version/s: 4.6.0
> Camel-package-maven-plugin: generates test configurers in non-tests artifacts
> -
>
> Key: CAMEL-20585
> URL: https://issues.apache.org/jira/browse/CAMEL-20585
> Project: Camel
> Issue Type: Bug
> Components: camel-package-maven-plugin
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Priority: Major
> Fix For: 4.6.0
>
>
> Change
> [https://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4#diff-8c376760c1f21c10dc4f6b051f972405cc04fc1ce9ca636a478cc5cfb8a1f51c]
> causes that for example _camel-main.jar_ contains test configurers like
> {code:java}
> org.apache.camel.main.MySecondBar, org.apache.camel.main.MySecondFoo| {code}
> As you can see
> herehttps://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4
> different method is called.
>
> The original method was:
> {code:java}
> public static boolean updateResource(BuildContext buildContext, Path out,
> String data) {
> try {
> if (FileUtil.updateFile(out, data)) {
> refresh(buildContext, out);
> return true;
> }
> } catch (IOException e) {
> throw new IOError(e);
> }
> return false;
> {code}
> which can not create a test resource.
> Newly called method
> {code:java}
> protected boolean updateResource(Path dir, String fileName, String data) {
> boolean updated;
> updated = updateResource(buildContext, dir.resolve(fileName), data);
> if (!fileName.endsWith(".java")) {
> > Path outputDir =
> > Paths.get(project.getBuild().getOutputDirectory());
> > updated |= updateResource(buildContext,
> > outputDir.resolve(fileName), data);
> }
> return updated;
> {code}
> refreshes also resources in outputDiectorry. Therefore some test configurers
> are created during build of the artifact.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20384) modernization: modernize map operations
[ https://issues.apache.org/jira/browse/CAMEL-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-20384. -- Assignee: Otavio Rodolfo Piske Resolution: Fixed This was fixed by the linked PR from Brice Frisco. Thanks for your contribution! > modernization: modernize map operations > --- > > Key: CAMEL-20384 > URL: https://issues.apache.org/jira/browse/CAMEL-20384 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > Fix For: 4.4.0 > > > Use more modern map operations (see below) where this could lead to cleaner > code. Check this list for outdated map usages: > https://sonarcloud.io/project/issues?resolved=false=java%3AS3824=apache_camel > Modern map operations: > * putIfAbsent > * computeIfPresent > * computeIfAbsent > * compute > Note: be careful with changing code in `core` as it could be part of the hot > path, and it needs closer inspection. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20582) No encoding is known for map entry value of type for header CamelAzureEventHubsEnqueuedTime
[
https://issues.apache.org/jira/browse/CAMEL-20582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-20582:
Assignee: Andrea Cosentino
> No encoding is known for map entry value of type for header
> CamelAzureEventHubsEnqueuedTime
>
>
> Key: CAMEL-20582
> URL: https://issues.apache.org/jira/browse/CAMEL-20582
> Project: Camel
> Issue Type: Bug
> Components: camel-azure-eventhubs
>Affects Versions: 4.4.0
>Reporter: Vishal Bihani
>Assignee: Andrea Cosentino
>Priority: Minor
> Attachments: e1.png, e2.png, logs.txt
>
>
> Camel azure event hub connector internally sets a header
> '{*}CamelAzureEventHubsEnqueuedTime{*}' which is of type
> '{*}java.time.Instant{*}'. But the underlying library Apache Qpid Proton does
> not support this type which results in error when producing messages to event
> hub.
>
> Current workaround is to remove this header from exchange before producing
> the message to event hub.
> Refer attachments for screenshot and logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20582) No encoding is known for map entry value of type for header CamelAzureEventHubsEnqueuedTime
[
https://issues.apache.org/jira/browse/CAMEL-20582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828890#comment-17828890
]
Andrea Cosentino commented on CAMEL-20582:
--
You're not supposed to send event with that header set. That header is only for
the consuming side, so if you're moving the message from eventhub to eventhub,
you need to clean the header. As documented the enqueueTime header is consumer
only, it's not common.
> No encoding is known for map entry value of type for header
> CamelAzureEventHubsEnqueuedTime
>
>
> Key: CAMEL-20582
> URL: https://issues.apache.org/jira/browse/CAMEL-20582
> Project: Camel
> Issue Type: Bug
> Components: camel-azure-eventhubs
>Affects Versions: 4.4.0
>Reporter: Vishal Bihani
>Priority: Minor
> Attachments: e1.png, e2.png, logs.txt
>
>
> Camel azure event hub connector internally sets a header
> '{*}CamelAzureEventHubsEnqueuedTime{*}' which is of type
> '{*}java.time.Instant{*}'. But the underlying library Apache Qpid Proton does
> not support this type which results in error when producing messages to event
> hub.
>
> Current workaround is to remove this header from exchange before producing
> the message to event hub.
> Refer attachments for screenshot and logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20582) No encoding is known for map entry value of type for header CamelAzureEventHubsEnqueuedTime
[
https://issues.apache.org/jira/browse/CAMEL-20582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-20582.
--
Resolution: Information Provided
> No encoding is known for map entry value of type for header
> CamelAzureEventHubsEnqueuedTime
>
>
> Key: CAMEL-20582
> URL: https://issues.apache.org/jira/browse/CAMEL-20582
> Project: Camel
> Issue Type: Bug
> Components: camel-azure-eventhubs
>Affects Versions: 4.4.0
>Reporter: Vishal Bihani
>Assignee: Andrea Cosentino
>Priority: Minor
> Attachments: e1.png, e2.png, logs.txt
>
>
> Camel azure event hub connector internally sets a header
> '{*}CamelAzureEventHubsEnqueuedTime{*}' which is of type
> '{*}java.time.Instant{*}'. But the underlying library Apache Qpid Proton does
> not support this type which results in error when producing messages to event
> hub.
>
> Current workaround is to remove this header from exchange before producing
> the message to event hub.
> Refer attachments for screenshot and logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20215) camel-mllp - MllpTcpServerConsumerOptionalEndOfDataWithValidationTest.testMessageWithoutEndOfDataByte is failing on JDK21
[
https://issues.apache.org/jira/browse/CAMEL-20215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-20215:
-
Estimated Complexity: Novice (was: Unknown)
> camel-mllp -
> MllpTcpServerConsumerOptionalEndOfDataWithValidationTest.testMessageWithoutEndOfDataByte
> is failing on JDK21
> -
>
> Key: CAMEL-20215
> URL: https://issues.apache.org/jira/browse/CAMEL-20215
> Project: Camel
> Issue Type: Test
> Components: camel-mllp
>Affects Versions: 4.3.0
>Reporter: Aurélien Pupier
>Priority: Minor
> Labels: help-wanted
> Fix For: 4.x
>
>
> {noformat}
> java.lang.AssertionError: mock://complete Received message count. Expected:
> <1> but was: <2>
> at
> org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1860)
> at
> org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1794)
> at
> org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:448)
> at
> org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:426)
> at
> org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:416)
> at
> org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:238)
> at
> org.apache.camel.component.mllp.TcpServerConsumerEndOfDataAndValidationTestSupport.tearDown(TcpServerConsumerEndOfDataAndValidationTestSupport.java:121)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> {noformat}
> it is since build 197 but we don ot have anymore the history and so do not
> know which changes were included
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20215) camel-mllp - MllpTcpServerConsumerOptionalEndOfDataWithValidationTest.testMessageWithoutEndOfDataByte is failing on JDK21
[
https://issues.apache.org/jira/browse/CAMEL-20215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-20215:
-
Labels: help-wanted (was: )
> camel-mllp -
> MllpTcpServerConsumerOptionalEndOfDataWithValidationTest.testMessageWithoutEndOfDataByte
> is failing on JDK21
> -
>
> Key: CAMEL-20215
> URL: https://issues.apache.org/jira/browse/CAMEL-20215
> Project: Camel
> Issue Type: Test
> Components: camel-mllp
>Affects Versions: 4.3.0
>Reporter: Aurélien Pupier
>Priority: Minor
> Labels: help-wanted
> Fix For: 4.x
>
>
> {noformat}
> java.lang.AssertionError: mock://complete Received message count. Expected:
> <1> but was: <2>
> at
> org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1860)
> at
> org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1794)
> at
> org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:448)
> at
> org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:426)
> at
> org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:416)
> at
> org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:238)
> at
> org.apache.camel.component.mllp.TcpServerConsumerEndOfDataAndValidationTestSupport.tearDown(TcpServerConsumerEndOfDataAndValidationTestSupport.java:121)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> {noformat}
> it is since build 197 but we don ot have anymore the history and so do not
> know which changes were included
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20584) camel-mongo: java driver upgrade causes instabilities
[ https://issues.apache.org/jira/browse/CAMEL-20584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828674#comment-17828674 ] Otavio Rodolfo Piske commented on CAMEL-20584: -- Reference discussion: https://github.com/apache/camel/commit/6fe4706f1ff4051bebe109f6bdd28fd35d737f77 > camel-mongo: java driver upgrade causes instabilities > - > > Key: CAMEL-20584 > URL: https://issues.apache.org/jira/browse/CAMEL-20584 > Project: Camel > Issue Type: Bug > Components: camel-mongodb >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > > We found out that upgrading the MongoDB driver from 4.11.1 to 5.0.0 causes > the MongoDbTailableCursorConsumerIT to hang up, which seems to indicate a > problem with tailable cursors support or a problem with the new driver. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20584) camel-mongo: java driver upgrade causes instabilities
Otavio Rodolfo Piske created CAMEL-20584: Summary: camel-mongo: java driver upgrade causes instabilities Key: CAMEL-20584 URL: https://issues.apache.org/jira/browse/CAMEL-20584 Project: Camel Issue Type: Bug Components: camel-mongodb Reporter: Otavio Rodolfo Piske We found out that upgrading the MongoDB driver from 4.11.1 to 5.0.0 causes the MongoDbTailableCursorConsumerIT to hang up, which seems to indicate a problem with tailable cursors support or a problem with the new driver. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20565) Azure Service Bus Component: Support dead-lettering at application level
[ https://issues.apache.org/jira/browse/CAMEL-20565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20565. -- Resolution: Fixed > Azure Service Bus Component: Support dead-lettering at application level > > > Key: CAMEL-20565 > URL: https://issues.apache.org/jira/browse/CAMEL-20565 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > > https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dead-letter-queues#application-level-dead-lettering -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-17641) camel-catalog - Generate metadata for all known implementations of camel SPI interfaces
[ https://issues.apache.org/jira/browse/CAMEL-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828317#comment-17828317 ] Claus Ibsen edited comment on CAMEL-17641 at 3/20/24 6:31 AM: -- TODO: camel-sql aggregation repository *DONE* TODO: fix interfaceType not correct for some of beans *DONE* was (Author: davsclaus): TODO: camel-sql aggregation repository *DONE* TODO: fix interfaceType not correct for some of beans > camel-catalog - Generate metadata for all known implementations of camel SPI > interfaces > --- > > Key: CAMEL-17641 > URL: https://issues.apache.org/jira/browse/CAMEL-17641 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > For example AggregationStrategy can have a set of OOTB impls, and it would be > good to know what we have in camel. > We can make this metadata generated per component then it can be isolated per > component you use - and maybe also have this in the camel-catalog so we have > a single place to look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20583) Java 21 - Reduce the noise from the ThreadType logger
Claus Ibsen created CAMEL-20583: --- Summary: Java 21 - Reduce the noise from the ThreadType logger Key: CAMEL-20583 URL: https://issues.apache.org/jira/browse/CAMEL-20583 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 4.5.0 The virtual thread stuff is experimental and we should only log if its enabled explicit and otherwise log at DEBUG level the default level in ThreadType -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-17641) camel-catalog - Generate metadata for all known implementations of camel SPI interfaces
[ https://issues.apache.org/jira/browse/CAMEL-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827138#comment-17827138 ] Claus Ibsen edited comment on CAMEL-17641 at 3/20/24 6:05 AM: -- TODO: mojo to generate json *DONE* TODO: markup various beans such as aggregation strategy *DONE* TODO: copy jsons into camel-catalog *DONE* TODO: markup more beans from other components (camel-zipfile as example) TODO: camel-jbang can use the catalog to map FQN classname to JAR *DONE* TODO: generate configurer for reflection-free *DONE* TODO: markup all aggregation strategies *DONE* TODO: markup all idempotent repositories *DONE* TODO: markup all aggregation repositories *DONE* was (Author: davsclaus): TODO: mojo to generate json *DONE* TODO: markup various beans such as aggregation strategy *DONE* TODO: copy jsons into camel-catalog *DONE* TODO: markup more beans from other components (camel-zipfile as example) TODO: camel-jbang can use the catalog to map FQN classname to JAR *DONE* TODO: generate configurer for reflection-free *DONE* TODO: markup all aggregation strategies *DONE* TODO: markup all idempotent repositories *DONE* TODO: markup all aggregation repositories > camel-catalog - Generate metadata for all known implementations of camel SPI > interfaces > --- > > Key: CAMEL-17641 > URL: https://issues.apache.org/jira/browse/CAMEL-17641 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > For example AggregationStrategy can have a set of OOTB impls, and it would be > good to know what we have in camel. > We can make this metadata generated per component then it can be isolated per > component you use - and maybe also have this in the camel-catalog so we have > a single place to look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-17641) camel-catalog - Generate metadata for all known implementations of camel SPI interfaces
[ https://issues.apache.org/jira/browse/CAMEL-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828317#comment-17828317 ] Claus Ibsen edited comment on CAMEL-17641 at 3/20/24 6:05 AM: -- TODO: camel-sql aggregation repository *DONE* TODO: fix interfaceType not correct for some of beans was (Author: davsclaus): TODO: camel-sql aggregation repository TODO: fix interfaceType not correct for some of beans > camel-catalog - Generate metadata for all known implementations of camel SPI > interfaces > --- > > Key: CAMEL-17641 > URL: https://issues.apache.org/jira/browse/CAMEL-17641 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > For example AggregationStrategy can have a set of OOTB impls, and it would be > good to know what we have in camel. > We can make this metadata generated per component then it can be isolated per > component you use - and maybe also have this in the camel-catalog so we have > a single place to look -- This message was sent by Atlassian Jira (v8.20.10#820010)
