[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/14/24 8:07 PM: -- 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 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) > 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] [Updated] (CAMEL-20568) Set errorHandler on route level in YAML DSL
[ https://issues.apache.org/jira/browse/CAMEL-20568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20568: Affects Version/s: 4.4.0 (was: 4.x) > Set errorHandler on route level in YAML DSL > --- > > Key: CAMEL-20568 > URL: https://issues.apache.org/jira/browse/CAMEL-20568 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.4.0 >Reporter: Christoph Deppisch >Priority: Major > Fix For: 4.5.0 > > > Camel YAML DSL allows to set errorHandler only as global error handler on > Camel context. We should also allow to set the error handler on a route level. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20568) Set errorHandler on route level in YAML DSL
[ https://issues.apache.org/jira/browse/CAMEL-20568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20568: Fix Version/s: 4.5.0 > Set errorHandler on route level in YAML DSL > --- > > Key: CAMEL-20568 > URL: https://issues.apache.org/jira/browse/CAMEL-20568 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.x >Reporter: Christoph Deppisch >Priority: Major > Fix For: 4.5.0 > > > Camel YAML DSL allows to set errorHandler only as global error handler on > Camel context. We should also allow to set the error handler on a route level. -- 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/14/24 6:55 PM: -- 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) was (Author: davsclaus): TODO: mojo to generate json *DONE* TODO: markup various beans such as aggregation strategy TODO: copy jsons into camel-catalog > 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] [Resolved] (CAMEL-20570) Camel-Langchain-*: Create starters for Spring Boot
[ https://issues.apache.org/jira/browse/CAMEL-20570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20570. -- Resolution: Fixed > Camel-Langchain-*: Create starters for Spring Boot > -- > > Key: CAMEL-20570 > URL: https://issues.apache.org/jira/browse/CAMEL-20570 > 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] [Updated] (CAMEL-20570) Camel-Langchain-*: Create starters for Spring Boot
[ https://issues.apache.org/jira/browse/CAMEL-20570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20570: - Summary: Camel-Langchain-*: Create starters for Spring Boot (was: Camel-Langchain: Create starer for Spring Boot) > Camel-Langchain-*: Create starters for Spring Boot > -- > > Key: CAMEL-20570 > URL: https://issues.apache.org/jira/browse/CAMEL-20570 > 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-20570) Camel-Langchain: Create starer for Spring Boot
Andrea Cosentino created CAMEL-20570: Summary: Camel-Langchain: Create starer for Spring Boot Key: CAMEL-20570 URL: https://issues.apache.org/jira/browse/CAMEL-20570 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-20567) Add support for restConfiguration in XML DSL IO
[ https://issues.apache.org/jira/browse/CAMEL-20567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20567: Fix Version/s: 4.5.0 > Add support for restConfiguration in XML DSL IO > --- > > Key: CAMEL-20567 > URL: https://issues.apache.org/jira/browse/CAMEL-20567 > Project: Camel > Issue Type: Improvement > Components: camel-xml-io >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20567) Add support for restConfiguration in XML DSL IO
[ https://issues.apache.org/jira/browse/CAMEL-20567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827164#comment-17827164 ] Claus Ibsen commented on CAMEL-20567: - Ah okay, you want it to have api for loading as in the PR > Add support for restConfiguration in XML DSL IO > --- > > Key: CAMEL-20567 > URL: https://issues.apache.org/jira/browse/CAMEL-20567 > Project: Camel > Issue Type: Improvement > Components: camel-xml-io >Reporter: John Poth >Assignee: John Poth >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20566) Jaxb version should be present in parent/pom.xml not pom/xml
[
https://issues.apache.org/jira/browse/CAMEL-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20566.
-
Resolution: Fixed
> Jaxb version should be present in parent/pom.xml not pom/xml
>
>
> Key: CAMEL-20566
> URL: https://issues.apache.org/jira/browse/CAMEL-20566
> Project: Camel
> Issue Type: Task
> Components: build system
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
> Fix For: 4.5.0
>
>
> I'd like to reuse a version `jaxb-core-version` in camel-quarkus project. I
> noticed, that the definition of version is placed in pom.xml (not
> parent/pom.xml), therefore can not be reused.
> I dug up a little bit into the history and found a comment from pom.xml
> {code:java}
>
> {code}
> , which was removed during removal of maven-eclipse-plugin ( that is retired
> since 2015)
>
> Based on that comment, the fact that eclipse plugin was removed and
> successful local build with the fix, I think that those version definition
> should be moved to parent/pom.xml (where other version resides).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20569) camel-catalog - Can we markup what functions and operations languages have for tooling assistance
Claus Ibsen created CAMEL-20569: --- Summary: camel-catalog - Can we markup what functions and operations languages have for tooling assistance Key: CAMEL-20569 URL: https://issues.apache.org/jira/browse/CAMEL-20569 Project: Camel Issue Type: Improvement Components: camel-catalog Reporter: Claus Ibsen Fix For: 4.x Tooling would benefit if we can markup which functions you have in - simple - java-joor - xpath - and some others In particular simple and java-joor would benefit -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20568) Set errorHandler on route level in YAML DSL
[
https://issues.apache.org/jira/browse/CAMEL-20568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827145#comment-17827145
]
Claus Ibsen commented on CAMEL-20568:
-
Something ala
{code}
- routeConfiguration:
id: myEH
errorHandler:
deadLetterChannel:
deadLetterUri: myRouteDLQ
- route:
routeConfigurationId: myEH
from:
uri: activemq:cheese
steps:
- log:
message: ${body}
{code}
> Set errorHandler on route level in YAML DSL
> ---
>
> Key: CAMEL-20568
> URL: https://issues.apache.org/jira/browse/CAMEL-20568
> Project: Camel
> Issue Type: Improvement
> Components: camel-yaml-dsl
>Affects Versions: 4.x
>Reporter: Christoph Deppisch
>Priority: Major
>
> Camel YAML DSL allows to set errorHandler only as global error handler on
> Camel context. We should also allow to set the error handler on a route level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20568) Set errorHandler on route level in YAML DSL
[ https://issues.apache.org/jira/browse/CAMEL-20568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827143#comment-17827143 ] Claus Ibsen commented on CAMEL-20568: - You use route configurations for that, and then set the route to the given route configuration. > Set errorHandler on route level in YAML DSL > --- > > Key: CAMEL-20568 > URL: https://issues.apache.org/jira/browse/CAMEL-20568 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.x >Reporter: Christoph Deppisch >Priority: Major > > Camel YAML DSL allows to set errorHandler only as global error handler on > Camel context. We should also allow to set the error handler on a route level. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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 updated CAMEL-17641: Fix Version/s: 4.5.0 (was: 4.x) > 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-20567) Add support for restConfiguration in XML DSL IO
[ https://issues.apache.org/jira/browse/CAMEL-20567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827140#comment-17827140 ] Claus Ibsen commented on CAMEL-20567: - Can you tell more as its already there doParseRestConfigurationDefinition > Add support for restConfiguration in XML DSL IO > --- > > Key: CAMEL-20567 > URL: https://issues.apache.org/jira/browse/CAMEL-20567 > Project: Camel > Issue Type: Improvement > Components: camel-xml-io >Reporter: John Poth >Assignee: John Poth >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20567) Add support for restConfiguration in XML DSL IO
[ https://issues.apache.org/jira/browse/CAMEL-20567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827140#comment-17827140 ] Claus Ibsen edited comment on CAMEL-20567 at 3/14/24 3:35 PM: -- Can you tell more as its already there (doParseRestConfigurationDefinition) what is it that you cannot do was (Author: davsclaus): Can you tell more as its already there doParseRestConfigurationDefinition > Add support for restConfiguration in XML DSL IO > --- > > Key: CAMEL-20567 > URL: https://issues.apache.org/jira/browse/CAMEL-20567 > Project: Camel > Issue Type: Improvement > Components: camel-xml-io >Reporter: John Poth >Assignee: John Poth >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20568) Set errorHandler on route level in YAML DSL
Christoph Deppisch created CAMEL-20568: -- Summary: Set errorHandler on route level in YAML DSL Key: CAMEL-20568 URL: https://issues.apache.org/jira/browse/CAMEL-20568 Project: Camel Issue Type: Improvement Components: camel-yaml-dsl Affects Versions: 4.x Reporter: Christoph Deppisch Camel YAML DSL allows to set errorHandler only as global error handler on Camel context. We should also allow to set the error handler on a route level. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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 commented on CAMEL-17641: - TODO: mojo to generate json *DONE* TODO: markup various beans such as aggregation strategy TODO: copy jsons into camel-catalog > 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.x > > > 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-20567) Add support for restConfiguration in XML DSL IO
John Poth created CAMEL-20567: - Summary: Add support for restConfiguration in XML DSL IO Key: CAMEL-20567 URL: https://issues.apache.org/jira/browse/CAMEL-20567 Project: Camel Issue Type: Improvement Components: camel-xml-io Reporter: John Poth -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20567) Add support for restConfiguration in XML DSL IO
[ https://issues.apache.org/jira/browse/CAMEL-20567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-20567: - Assignee: John Poth > Add support for restConfiguration in XML DSL IO > --- > > Key: CAMEL-20567 > URL: https://issues.apache.org/jira/browse/CAMEL-20567 > Project: Camel > Issue Type: Improvement > Components: camel-xml-io >Reporter: John Poth >Assignee: John Poth >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (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 reassigned CAMEL-17641: --- Assignee: Claus Ibsen > 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.x > > > 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] [Updated] (CAMEL-20563) camel-kafka - breakOnFirstError causes thread and memory leaks
[ https://issues.apache.org/jira/browse/CAMEL-20563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20563: Fix Version/s: 4.x > camel-kafka - breakOnFirstError causes thread and memory leaks > -- > > Key: CAMEL-20563 > URL: https://issues.apache.org/jira/browse/CAMEL-20563 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 3.18.5, 3.22.1 >Reporter: Aniket Jadhav >Priority: Major > Fix For: 4.x > > Attachments: KafkaHeartBeatLeakThread.PNG, > heartbeat-threading-problem.zip > > > This has got fixed in > [CAMEL-16857|https://issues.apache.org/jira/browse/CAMEL-16857]. But Facing > same issue with 3.18.5, is it reintroduced at some point? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20563) camel-kafka - breakOnFirstError causes thread and memory leaks
[ https://issues.apache.org/jira/browse/CAMEL-20563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827102#comment-17827102 ] Claus Ibsen commented on CAMEL-20563: - Thanks for the sample and analysis. Yeah we should see if we can find a way to cancel the old thread. You are welcome to attempt doing a fix and test it, and if fixed then send as PR or attach the code here > camel-kafka - breakOnFirstError causes thread and memory leaks > -- > > Key: CAMEL-20563 > URL: https://issues.apache.org/jira/browse/CAMEL-20563 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 3.18.5, 3.22.1 >Reporter: Aniket Jadhav >Priority: Major > Attachments: KafkaHeartBeatLeakThread.PNG, > heartbeat-threading-problem.zip > > > This has got fixed in > [CAMEL-16857|https://issues.apache.org/jira/browse/CAMEL-16857]. But Facing > same issue with 3.18.5, is it reintroduced at some point? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-16870) camel-karaf - Add camel-atlasmap feature
[ https://issues.apache.org/jira/browse/CAMEL-16870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16870. - Resolution: Abandoned atlasmap is EOL and not maintained anymore > camel-karaf - Add camel-atlasmap feature > > > Key: CAMEL-16870 > URL: https://issues.apache.org/jira/browse/CAMEL-16870 > Project: Camel > Issue Type: New Feature > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-16187) camel-restdsl-openapi-plugin - generate operationId enumeration
[
https://issues.apache.org/jira/browse/CAMEL-16187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827099#comment-17827099
]
Claus Ibsen commented on CAMEL-16187:
-
This would only be for Java DSL, the tool can output for XML and YAML also
> camel-restdsl-openapi-plugin - generate operationId enumeration
> ---
>
> Key: CAMEL-16187
> URL: https://issues.apache.org/jira/browse/CAMEL-16187
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 3.7.2
>Reporter: Vladimír Váša
>Priority: Minor
> Fix For: 4.x
>
>
> Hi,
> I discovered this great tool (camel-restdsl-openapi-plugin) two days ago.
> It's almost perfect. I have only one suggestion for improvement:
>
> Actually the plugin is generating "controller" like class with code similar
> to:
> {code:java}
> rest()
> .get("/somepath")
> .id("operationIdFromOpenAPI")
> .produces("application/json")
> .to("direct:operationIdFromOpenAPI");
> {code}
> And "user" can continue route with:
> {code:java}
> from(direct:operationIdFromOpenAPI)...
> {code}
>
> Problem:
> The problem occurs during the change operationId in next version of OpenAPI
> definition. It have to be manually checked.
>
> Improvement:
> It would be very nice if the plugin generated an enum of operationIds from
> the OpenAPI definition. Something like:
> {code:java}
> public enum ApiOperation {
> OPERATION_ID_1("operationId1"),
> ANOTHER_OPERATION_ID("anotherOperationId");
> private final String value;
> // ... constructor, toString...{code}
>
> And route with:
> {code:java}
> ...to("direct:" + ApiOperation.OPERATION_ID_1);
> {code}
> With best regards
> Vladimir
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20563) camel-kafka - breakOnFirstError causes thread and memory leaks
[
https://issues.apache.org/jira/browse/CAMEL-20563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827098#comment-17827098
]
Sami Peltola commented on CAMEL-20563:
--
Attached an example project, instructions in the README.md.
Seems that using breakOnFirstError option for Kafka component creates a new
heartbeat thread every time KafkaFetchRecords is set to reconnect, which
happens when there an exception is allowed to propagate back from the route.
In KafkaFetchRecords, the task is set to reconnection state every time an
exception bubbles back from the route:
{code:java}
// when breakOnFirstError we want to unsubscribe from Kafka
if (result != null && result.isBreakOnErrorHit() &&
!this.state.equals(State.PAUSED)) {
LOG.debug("We hit an error ... setting flags to force
reconnect");
// force re-connect
setReconnect(true);
setConnected(false);
}
{code}
This will lead to kafka-client
*kafkaConsumer.getEndpoint().getKafkaClientFactory().getConsumer* being called
again in KafkaFetchRecords.createConsumer(), which in turn creates
ConsumerCoordinator again. The problem is that the heartbeat-thread created for
the previous ConsumerCoordinator is never shutdown.
The new ConsumerCoordinator will have class member heartbeatThread set to null
and the next time ensureActiveGroup is called, a new heartbeat-thread is
created:
{code:java}
private synchronized void startHeartbeatThreadIfNeeded() {
if (heartbeatThread == null) {
heartbeatThread = new HeartbeatThread();
heartbeatThread.start();
}
}
{code}
> camel-kafka - breakOnFirstError causes thread and memory leaks
> --
>
> Key: CAMEL-20563
> URL: https://issues.apache.org/jira/browse/CAMEL-20563
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 3.18.5, 3.22.1
>Reporter: Aniket Jadhav
>Priority: Major
> Attachments: KafkaHeartBeatLeakThread.PNG,
> heartbeat-threading-problem.zip
>
>
> This has got fixed in
> [CAMEL-16857|https://issues.apache.org/jira/browse/CAMEL-16857]. But Facing
> same issue with 3.18.5, is it reintroduced at some point?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20545) AdviceWith -> replaceFromWith fails when using several templated routes
[
https://issues.apache.org/jira/browse/CAMEL-20545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20545.
-
Resolution: Fixed
Thanks for reporting and the sample code
> AdviceWith -> replaceFromWith fails when using several templated routes
> ---
>
> Key: CAMEL-20545
> URL: https://issues.apache.org/jira/browse/CAMEL-20545
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 4.4.0
>Reporter: Thomas Gantenbein
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.5.0
>
>
> Given the following route template
> {code:java}
> routeTemplate("myRouteTemplate")
> .templateParameter("message")
> .from("timer:myTimer?period=5000")
> .log("{{message}}");
> {code}
> And given the following two routes based on that template
>
> {code:java}
> templatedRoute("myRouteTemplate")
> .parameter("message", "hello from first template")
> .routeId("firstroute");
> templatedRoute("myRouteTemplate")
> .parameter("message", "hello from second template")
> .routeId("secondroute");
>
> {code}
> a JUnit test annotated with
> {code:java}
> @CamelMainTest(replaceRouteFromWith = {"firstroute=direct:start"}){code}
> will fail with
> ??Failed to start route secondroute because of Multiple consumers for the
> same endpoint is not allowed: direct://start??
> See
> [https://github.com/thomas-gantenbein-tga/camel-advicewithtest/blob/master/src/test/java/com/acme/ReplaceFromWithAnnotationTest.java]
> for such a JUnit test that will fail.
> The same happens with Spring Boot test, see
> [https://github.com/thomas-gantenbein-tga/advicewithtest_springboot/blob/master/src/test/java/com/acme/WithAdviceWithAnnotationTest.java].
> Tests _do_ pass when the context is already started when advising it, see
> https://github.com/thomas-gantenbein-tga/advicewithtest_springboot/blob/master/src/test/java/com/acme/NoAdviceWithAnnotationTest.java#L38.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20563) camel-kafka - breakOnFirstError causes thread and memory leaks
[ https://issues.apache.org/jira/browse/CAMEL-20563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sami Peltola updated CAMEL-20563: - Attachment: heartbeat-threading-problem.zip > camel-kafka - breakOnFirstError causes thread and memory leaks > -- > > Key: CAMEL-20563 > URL: https://issues.apache.org/jira/browse/CAMEL-20563 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 3.18.5, 3.22.1 >Reporter: Aniket Jadhav >Priority: Major > Attachments: KafkaHeartBeatLeakThread.PNG, > heartbeat-threading-problem.zip > > > This has got fixed in > [CAMEL-16857|https://issues.apache.org/jira/browse/CAMEL-16857]. But Facing > same issue with 3.18.5, is it reintroduced at some point? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20566) Jaxb version should be present in parent/pom.xml not pom/xml
[
https://issues.apache.org/jira/browse/CAMEL-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20566:
Fix Version/s: 4.5.0
> Jaxb version should be present in parent/pom.xml not pom/xml
>
>
> Key: CAMEL-20566
> URL: https://issues.apache.org/jira/browse/CAMEL-20566
> Project: Camel
> Issue Type: Task
> Components: build system
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
> Fix For: 4.5.0
>
>
> I'd like to reuse a version `jaxb-core-version` in camel-quarkus project. I
> noticed, that the definition of version is placed in pom.xml (not
> parent/pom.xml), therefore can not be reused.
> I dug up a little bit into the history and found a comment from pom.xml
> {code:java}
>
> {code}
> , which was removed during removal of maven-eclipse-plugin ( that is retired
> since 2015)
>
> Based on that comment, the fact that eclipse plugin was removed and
> successful local build with the fix, I think that those version definition
> should be moved to parent/pom.xml (where other version resides).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20566) Jaxb version should be present in parent/pom.xml not pom/xml
[
https://issues.apache.org/jira/browse/CAMEL-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20566:
Priority: Minor (was: Major)
> Jaxb version should be present in parent/pom.xml not pom/xml
>
>
> Key: CAMEL-20566
> URL: https://issues.apache.org/jira/browse/CAMEL-20566
> Project: Camel
> Issue Type: Task
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
>
> I'd like to reuse a version `jaxb-core-version` in camel-quarkus project. I
> noticed, that the definition of version is placed in pom.xml (not
> parent/pom.xml), therefore can not be reused.
> I dug up a little bit into the history and found a comment from pom.xml
> {code:java}
>
> {code}
> , which was removed during removal of maven-eclipse-plugin ( that is retired
> since 2015)
>
> Based on that comment, the fact that eclipse plugin was removed and
> successful local build with the fix, I think that those version definition
> should be moved to parent/pom.xml (where other version resides).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20566) Jaxb version should be present in parent/pom.xml not pom/xml
[
https://issues.apache.org/jira/browse/CAMEL-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20566:
Component/s: build system
> Jaxb version should be present in parent/pom.xml not pom/xml
>
>
> Key: CAMEL-20566
> URL: https://issues.apache.org/jira/browse/CAMEL-20566
> Project: Camel
> Issue Type: Task
> Components: build system
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
>
> I'd like to reuse a version `jaxb-core-version` in camel-quarkus project. I
> noticed, that the definition of version is placed in pom.xml (not
> parent/pom.xml), therefore can not be reused.
> I dug up a little bit into the history and found a comment from pom.xml
> {code:java}
>
> {code}
> , which was removed during removal of maven-eclipse-plugin ( that is retired
> since 2015)
>
> Based on that comment, the fact that eclipse plugin was removed and
> successful local build with the fix, I think that those version definition
> should be moved to parent/pom.xml (where other version resides).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20566) Jaxb version should be present in parent/pom.xml not pom/xml
[
https://issues.apache.org/jira/browse/CAMEL-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20566:
Issue Type: Task (was: Bug)
> Jaxb version should be present in parent/pom.xml not pom/xml
>
>
> Key: CAMEL-20566
> URL: https://issues.apache.org/jira/browse/CAMEL-20566
> Project: Camel
> Issue Type: Task
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Major
>
> I'd like to reuse a version `jaxb-core-version` in camel-quarkus project. I
> noticed, that the definition of version is placed in pom.xml (not
> parent/pom.xml), therefore can not be reused.
> I dug up a little bit into the history and found a comment from pom.xml
> {code:java}
>
> {code}
> , which was removed during removal of maven-eclipse-plugin ( that is retired
> since 2015)
>
> Based on that comment, the fact that eclipse plugin was removed and
> successful local build with the fix, I think that those version definition
> should be moved to parent/pom.xml (where other version resides).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20566) Jaxb version should be present in parent/pom.xml not pom/xml
Jiri Ondrusek created CAMEL-20566:
-
Summary: Jaxb version should be present in parent/pom.xml not
pom/xml
Key: CAMEL-20566
URL: https://issues.apache.org/jira/browse/CAMEL-20566
Project: Camel
Issue Type: Bug
Affects Versions: 4.5.0
Reporter: Jiri Ondrusek
Assignee: Jiri Ondrusek
I'd like to reuse a version `jaxb-core-version` in camel-quarkus project. I
noticed, that the definition of version is placed in pom.xml (not
parent/pom.xml), therefore can not be reused.
I dug up a little bit into the history and found a comment from pom.xml
{code:java}
{code}
, which was removed during removal of maven-eclipse-plugin ( that is retired
since 2015)
Based on that comment, the fact that eclipse plugin was removed and successful
local build with the fix, I think that those version definition should be moved
to parent/pom.xml (where other version resides).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20545) AdviceWith -> replaceFromWith fails when using several templated routes
[
https://issues.apache.org/jira/browse/CAMEL-20545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20545:
Component/s: camel-test
(was: camel-main)
(was: camel-spring-boot)
> AdviceWith -> replaceFromWith fails when using several templated routes
> ---
>
> Key: CAMEL-20545
> URL: https://issues.apache.org/jira/browse/CAMEL-20545
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 4.4.0
>Reporter: Thomas Gantenbein
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.5.0
>
>
> Given the following route template
> {code:java}
> routeTemplate("myRouteTemplate")
> .templateParameter("message")
> .from("timer:myTimer?period=5000")
> .log("{{message}}");
> {code}
> And given the following two routes based on that template
>
> {code:java}
> templatedRoute("myRouteTemplate")
> .parameter("message", "hello from first template")
> .routeId("firstroute");
> templatedRoute("myRouteTemplate")
> .parameter("message", "hello from second template")
> .routeId("secondroute");
>
> {code}
> a JUnit test annotated with
> {code:java}
> @CamelMainTest(replaceRouteFromWith = {"firstroute=direct:start"}){code}
> will fail with
> ??Failed to start route secondroute because of Multiple consumers for the
> same endpoint is not allowed: direct://start??
> See
> [https://github.com/thomas-gantenbein-tga/camel-advicewithtest/blob/master/src/test/java/com/acme/ReplaceFromWithAnnotationTest.java]
> for such a JUnit test that will fail.
> The same happens with Spring Boot test, see
> [https://github.com/thomas-gantenbein-tga/advicewithtest_springboot/blob/master/src/test/java/com/acme/WithAdviceWithAnnotationTest.java].
> Tests _do_ pass when the context is already started when advising it, see
> https://github.com/thomas-gantenbein-tga/advicewithtest_springboot/blob/master/src/test/java/com/acme/NoAdviceWithAnnotationTest.java#L38.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20545) AdviceWith -> replaceFromWith fails when using several templated routes
[
https://issues.apache.org/jira/browse/CAMEL-20545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20545:
Fix Version/s: 4.5.0
> AdviceWith -> replaceFromWith fails when using several templated routes
> ---
>
> Key: CAMEL-20545
> URL: https://issues.apache.org/jira/browse/CAMEL-20545
> Project: Camel
> Issue Type: Bug
> Components: camel-main, camel-spring-boot
>Affects Versions: 4.4.0
>Reporter: Thomas Gantenbein
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.5.0
>
>
> Given the following route template
> {code:java}
> routeTemplate("myRouteTemplate")
> .templateParameter("message")
> .from("timer:myTimer?period=5000")
> .log("{{message}}");
> {code}
> And given the following two routes based on that template
>
> {code:java}
> templatedRoute("myRouteTemplate")
> .parameter("message", "hello from first template")
> .routeId("firstroute");
> templatedRoute("myRouteTemplate")
> .parameter("message", "hello from second template")
> .routeId("secondroute");
>
> {code}
> a JUnit test annotated with
> {code:java}
> @CamelMainTest(replaceRouteFromWith = {"firstroute=direct:start"}){code}
> will fail with
> ??Failed to start route secondroute because of Multiple consumers for the
> same endpoint is not allowed: direct://start??
> See
> [https://github.com/thomas-gantenbein-tga/camel-advicewithtest/blob/master/src/test/java/com/acme/ReplaceFromWithAnnotationTest.java]
> for such a JUnit test that will fail.
> The same happens with Spring Boot test, see
> [https://github.com/thomas-gantenbein-tga/advicewithtest_springboot/blob/master/src/test/java/com/acme/WithAdviceWithAnnotationTest.java].
> Tests _do_ pass when the context is already started when advising it, see
> https://github.com/thomas-gantenbein-tga/advicewithtest_springboot/blob/master/src/test/java/com/acme/NoAdviceWithAnnotationTest.java#L38.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20545) AdviceWith -> replaceFromWith fails when using several templated routes
[
https://issues.apache.org/jira/browse/CAMEL-20545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20545:
---
Assignee: Claus Ibsen
> AdviceWith -> replaceFromWith fails when using several templated routes
> ---
>
> Key: CAMEL-20545
> URL: https://issues.apache.org/jira/browse/CAMEL-20545
> Project: Camel
> Issue Type: Bug
> Components: camel-main, camel-spring-boot
>Affects Versions: 4.4.0
>Reporter: Thomas Gantenbein
>Assignee: Claus Ibsen
>Priority: Minor
>
> Given the following route template
> {code:java}
> routeTemplate("myRouteTemplate")
> .templateParameter("message")
> .from("timer:myTimer?period=5000")
> .log("{{message}}");
> {code}
> And given the following two routes based on that template
>
> {code:java}
> templatedRoute("myRouteTemplate")
> .parameter("message", "hello from first template")
> .routeId("firstroute");
> templatedRoute("myRouteTemplate")
> .parameter("message", "hello from second template")
> .routeId("secondroute");
>
> {code}
> a JUnit test annotated with
> {code:java}
> @CamelMainTest(replaceRouteFromWith = {"firstroute=direct:start"}){code}
> will fail with
> ??Failed to start route secondroute because of Multiple consumers for the
> same endpoint is not allowed: direct://start??
> See
> [https://github.com/thomas-gantenbein-tga/camel-advicewithtest/blob/master/src/test/java/com/acme/ReplaceFromWithAnnotationTest.java]
> for such a JUnit test that will fail.
> The same happens with Spring Boot test, see
> [https://github.com/thomas-gantenbein-tga/advicewithtest_springboot/blob/master/src/test/java/com/acme/WithAdviceWithAnnotationTest.java].
> Tests _do_ pass when the context is already started when advising it, see
> https://github.com/thomas-gantenbein-tga/advicewithtest_springboot/blob/master/src/test/java/com/acme/NoAdviceWithAnnotationTest.java#L38.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20357) camel-core - throttle EIP doesn't work as expected when it's in a loopDoWhile
[
https://issues.apache.org/jira/browse/CAMEL-20357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20357.
-
Fix Version/s: 4.4.0
Resolution: Fixed
Works fine in 4.4.0
> camel-core - throttle EIP doesn't work as expected when it's in a loopDoWhile
> -
>
> Key: CAMEL-20357
> URL: https://issues.apache.org/jira/browse/CAMEL-20357
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.3.0
>Reporter: Papa John
>Assignee: Rhuan Rocha
>Priority: Minor
> Fix For: 4.4.0
>
>
> I just upgraded my project to Apache Camel 4.3.0, and my code stop to work as
> expected.
> It seems there was some changes to the `throttle EIP` – it's now throttling
> based on the number of concurrent exchanges.
> My route uses a {{`{*}loopDoWhile{*}`}} to loop an exchange over and over, so
> in a sense, the concurrent exchange should always be zero (and the inflight
> exchange is actually zero).
> However, my loop will stop when it reached the max number of concurrent
> exchanges I set for the thottler.
> For example, in the following code, the loop will stop at 10th iteration. It
> seems the new changes didn't put loop DSL into consideration...
> {code:java}
> import org.apache.camel.builder.RouteBuilder;public class Test extends
> RouteBuilder { @Override
> public void configure() throws Exception { // Write your routes
> here, for example:
> from("timer:java?delay=1000=1")
> .loopDoWhile(constant(true)).breakOnShutdown()
> .throttle(10)
> .setBody()
> .simple("Hello Camel from ${routeId}")
> .log("${body}");
> }
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20563) camel-kafka - breakOnFirstError causes thread and memory leaks
[ https://issues.apache.org/jira/browse/CAMEL-20563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20563: Summary: camel-kafka - breakOnFirstError causes thread and memory leaks (was: breakOnFirstError causes thread and memory leaks in camel-kafka) > camel-kafka - breakOnFirstError causes thread and memory leaks > -- > > Key: CAMEL-20563 > URL: https://issues.apache.org/jira/browse/CAMEL-20563 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 3.18.5, 3.22.1 >Reporter: Aniket Jadhav >Priority: Major > Attachments: KafkaHeartBeatLeakThread.PNG > > > This has got fixed in > [CAMEL-16857|https://issues.apache.org/jira/browse/CAMEL-16857]. But Facing > same issue with 3.18.5, is it reintroduced at some point? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20563) breakOnFirstError causes thread and memory leaks in camel-kafka
[ https://issues.apache.org/jira/browse/CAMEL-20563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827081#comment-17827081 ] Claus Ibsen commented on CAMEL-20563: - Also if you can put together a sample project that reproduces this and attach as .zip file > breakOnFirstError causes thread and memory leaks in camel-kafka > --- > > Key: CAMEL-20563 > URL: https://issues.apache.org/jira/browse/CAMEL-20563 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 3.18.5, 3.22.1 >Reporter: Aniket Jadhav >Priority: Major > Attachments: KafkaHeartBeatLeakThread.PNG > > > This has got fixed in > [CAMEL-16857|https://issues.apache.org/jira/browse/CAMEL-16857]. But Facing > same issue with 3.18.5, is it reintroduced at some point? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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 updated CAMEL-20565: - Description: https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dead-letter-queues#application-level-dead-lettering > 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] [Updated] (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 updated CAMEL-20565: - Summary: Azure Service Bus Component: Support dead-lettering at application level (was: Azure Service Bus Component: Support SubQueue as configuration parameter) > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20518) Camel project - doesn't build on Windows anymore
[
https://issues.apache.org/jira/browse/CAMEL-20518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-20518:
-
Fix Version/s: 4.4.2
> Camel project - doesn't build on Windows anymore
>
>
> Key: CAMEL-20518
> URL: https://issues.apache.org/jira/browse/CAMEL-20518
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Minor
> Labels: help-wanted
> Fix For: 4.4.2, 4.5.0
>
>
> Apache Camel is not building on Windows.
> Trying to build it on Windows fails with the following error:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.camel:camel-package-maven-plugin:4.5.0-SNAPSHOT:prepare-catalog
> (default) on project camel-catalog: Error preparing catalog: Error reading
> json file:
> D:\a\camel\camel\catalog\camel-catalog\..\..\components\camel-salesforce\camel-salesforce-component\target\classes\META-INF\org\apache\camel\component\salesforce\salesforce.json:
> Input length = 3 -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20518) Camel project - doesn't build on Windows anymore
[
https://issues.apache.org/jira/browse/CAMEL-20518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske resolved CAMEL-20518.
--
Assignee: Otavio Rodolfo Piske
Resolution: Fixed
Oh, thanks for the reminder [~davsclaus]
Yeah, it's fixed.
> Camel project - doesn't build on Windows anymore
>
>
> Key: CAMEL-20518
> URL: https://issues.apache.org/jira/browse/CAMEL-20518
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Minor
> Labels: help-wanted
> Fix For: 4.5.0
>
>
> Apache Camel is not building on Windows.
> Trying to build it on Windows fails with the following error:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.camel:camel-package-maven-plugin:4.5.0-SNAPSHOT:prepare-catalog
> (default) on project camel-catalog: Error preparing catalog: Error reading
> json file:
> D:\a\camel\camel\catalog\camel-catalog\..\..\components\camel-salesforce\camel-salesforce-component\target\classes\META-INF\org\apache\camel\component\salesforce\salesforce.json:
> Input length = 3 -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20565) Azure Service Bus Component: Support SubQueue as configuration parameter
Andrea Cosentino created CAMEL-20565: Summary: Azure Service Bus Component: Support SubQueue as configuration parameter 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 Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel=17827046#comment-17827046
]
Claus Ibsen commented on CAMEL-20557:
-
TODO: openapi into rest-dsl model
TODO: api for creating consumer (impl in platform-http-vertx)
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations)
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup)
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: documentation
TODO: example
TODO: api-context-path to return the schema file as-is (change host url)
> 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.5.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] [Commented] (CAMEL-20518) Camel project - doesn't build on Windows anymore
[
https://issues.apache.org/jira/browse/CAMEL-20518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827044#comment-17827044
]
Claus Ibsen commented on CAMEL-20518:
-
Otavio, I guess you have fixed this now
> Camel project - doesn't build on Windows anymore
>
>
> Key: CAMEL-20518
> URL: https://issues.apache.org/jira/browse/CAMEL-20518
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: Otavio Rodolfo Piske
>Priority: Minor
> Labels: help-wanted
> Fix For: 4.5.0
>
>
> Apache Camel is not building on Windows.
> Trying to build it on Windows fails with the following error:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.camel:camel-package-maven-plugin:4.5.0-SNAPSHOT:prepare-catalog
> (default) on project camel-catalog: Error preparing catalog: Error reading
> json file:
> D:\a\camel\camel\catalog\camel-catalog\..\..\components\camel-salesforce\camel-salesforce-component\target\classes\META-INF\org\apache\camel\component\salesforce\salesforce.json:
> Input length = 3 -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20522) camel-test - CamelTestSupport does not call tearDown for each test method in some test classes
[ https://issues.apache.org/jira/browse/CAMEL-20522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827042#comment-17827042 ] Claus Ibsen commented on CAMEL-20522: - I have fixed camel-micrometer tests. To find potential other problems then we would need maybe to come up with a way to run tests where we count the start vs stop of camel, and use that to see if there are gaps, to help spot problems. > camel-test - CamelTestSupport does not call tearDown for each test method in > some test classes > -- > > Key: CAMEL-20522 > URL: https://issues.apache.org/jira/browse/CAMEL-20522 > Project: Camel > Issue Type: Bug > Components: camel-test >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > If you have test classes that does not directly extend CamelTestSupport then > your tests may not cleanup after testing. All the tearDown is not invoked. > It seems its due to CamelTestSupport implements both some interfaces from > JUnit and also have @AfterEach annotation and this skrews up junit when you > have test class hierachies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20522) camel-test - CamelTestSupport does not call tearDown for each test method in some test classes
[ https://issues.apache.org/jira/browse/CAMEL-20522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20522: Issue Type: Test (was: Bug) > camel-test - CamelTestSupport does not call tearDown for each test method in > some test classes > -- > > Key: CAMEL-20522 > URL: https://issues.apache.org/jira/browse/CAMEL-20522 > Project: Camel > Issue Type: Test > Components: camel-test >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > If you have test classes that does not directly extend CamelTestSupport then > your tests may not cleanup after testing. All the tearDown is not invoked. > It seems its due to CamelTestSupport implements both some interfaces from > JUnit and also have @AfterEach annotation and this skrews up junit when you > have test class hierachies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20522) camel-test - CamelTestSupport does not call tearDown for each test method in some test classes
[ https://issues.apache.org/jira/browse/CAMEL-20522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20522: Fix Version/s: 4.x (was: 4.5.0) > camel-test - CamelTestSupport does not call tearDown for each test method in > some test classes > -- > > Key: CAMEL-20522 > URL: https://issues.apache.org/jira/browse/CAMEL-20522 > Project: Camel > Issue Type: Bug > Components: camel-test >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > If you have test classes that does not directly extend CamelTestSupport then > your tests may not cleanup after testing. All the tearDown is not invoked. > It seems its due to CamelTestSupport implements both some interfaces from > JUnit and also have @AfterEach annotation and this skrews up junit when you > have test class hierachies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20564) camel-xslt: Make variables available as xsl:param
[ https://issues.apache.org/jira/browse/CAMEL-20564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20564. - Resolution: Fixed > camel-xslt: Make variables available as xsl:param > - > > Key: CAMEL-20564 > URL: https://issues.apache.org/jira/browse/CAMEL-20564 > Project: Camel > Issue Type: Improvement > Components: camel-xslt >Affects Versions: 4.4.0 >Reporter: Tomohisa Igarashi >Assignee: Tomohisa Igarashi >Priority: Major > Fix For: 4.4.2, 4.5.0 > > > Just like we're doing already for exchange properties and message headers, it > would be nice to make variables available as xsl:param for camel-xslt. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20564) camel-xslt: Make variables available as xsl:param
[ https://issues.apache.org/jira/browse/CAMEL-20564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20564: Fix Version/s: 4.4.2 > camel-xslt: Make variables available as xsl:param > - > > Key: CAMEL-20564 > URL: https://issues.apache.org/jira/browse/CAMEL-20564 > Project: Camel > Issue Type: Improvement > Components: camel-xslt >Affects Versions: 4.4.0 >Reporter: Tomohisa Igarashi >Assignee: Tomohisa Igarashi >Priority: Major > Fix For: 4.4.2, 4.5.0 > > > Just like we're doing already for exchange properties and message headers, it > would be nice to make variables available as xsl:param for camel-xslt. -- This message was sent by Atlassian Jira (v8.20.10#820010)
