[jira] [Work started] (CAMEL-19341) camel-spring-boot - Example with ActiveMQ Artemis
[ https://issues.apache.org/jira/browse/CAMEL-19341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-19341 started by Ramu. > camel-spring-boot - Example with ActiveMQ Artemis > - > > Key: CAMEL-19341 > URL: https://issues.apache.org/jira/browse/CAMEL-19341 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 4.0 > > > We should add an example how to use Artemis with SB3. There is some SB auto > configuration for Artemis that users would use. > And then we need a little Camel route that uses jms > https://stackoverflow.com/questions/76215514/activemq-artemis-spring-boot-3-apache-camel-routebuilder-is-not-working/76215788?noredirect=1#comment134405646_76215788 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19341) camel-spring-boot - Example with ActiveMQ Artemis
[ https://issues.apache.org/jira/browse/CAMEL-19341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-19341: Assignee: Ramu > camel-spring-boot - Example with ActiveMQ Artemis > - > > Key: CAMEL-19341 > URL: https://issues.apache.org/jira/browse/CAMEL-19341 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 4.0 > > > We should add an example how to use Artemis with SB3. There is some SB auto > configuration for Artemis that users would use. > And then we need a little Camel route that uses jms > https://stackoverflow.com/questions/76215514/activemq-artemis-spring-boot-3-apache-camel-routebuilder-is-not-working/76215788?noredirect=1#comment134405646_76215788 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-18887) camel-kotlin - Upgrade to 1.8
[ https://issues.apache.org/jira/browse/CAMEL-18887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18887 started by Ramu. > camel-kotlin - Upgrade to 1.8 > - > > Key: CAMEL-18887 > URL: https://issues.apache.org/jira/browse/CAMEL-18887 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kotlin >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Minor > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18887) camel-kotlin - Upgrade to 1.8
[ https://issues.apache.org/jira/browse/CAMEL-18887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-18887: Assignee: Ramu > camel-kotlin - Upgrade to 1.8 > - > > Key: CAMEL-18887 > URL: https://issues.apache.org/jira/browse/CAMEL-18887 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kotlin >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Minor > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18771) camel-core - Route template with hardcoded node IDs - Allow to specify prefix
[
https://issues.apache.org/jira/browse/CAMEL-18771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramu updated CAMEL-18771:
-
Description:
When using a route template with hardcoded nodeIDs, then these IDs are used
as-is, and therefore if you create 2+ routes then the 2nd route will have
duplicate.
So you need to use a template parameter and prefix with
id="{{myPrefix}}ValueHere".
We could maybe add a option "nodePrefix" or something that allows users to
create route templates where nodeIDs are then prefixed.
was:
When using a route template with hardcoded nodeIDs, then these IDs are used
as-is, and therefore if you create 2+ routes then the 2nd route will have
duplicate.
So you need to use a template parameter and prefix with
id="{{myPrefix}}ValueHere".
We could maybe add a option "nodePrefix" or something that allows users to
create route templates where nodeIDs are then prefixed.
created in upstream [JIRA|https://issues.apache.org/jira/browse/CAMEL-18771]
> camel-core - Route template with hardcoded node IDs - Allow to specify prefix
> -
>
> Key: CAMEL-18771
> URL: https://issues.apache.org/jira/browse/CAMEL-18771
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Priority: Major
>
> When using a route template with hardcoded nodeIDs, then these IDs are used
> as-is, and therefore if you create 2+ routes then the 2nd route will have
> duplicate.
> So you need to use a template parameter and prefix with
> id="{{myPrefix}}ValueHere".
> We could maybe add a option "nodePrefix" or something that allows users to
> create route templates where nodeIDs are then prefixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18771) camel-core - Route template with hardcoded node IDs - Allow to specify prefix
[
https://issues.apache.org/jira/browse/CAMEL-18771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramu updated CAMEL-18771:
-
Description:
When using a route template with hardcoded nodeIDs, then these IDs are used
as-is, and therefore if you create 2+ routes then the 2nd route will have
duplicate.
So you need to use a template parameter and prefix with
id="{{myPrefix}}ValueHere".
We could maybe add a option "nodePrefix" or something that allows users to
create route templates where nodeIDs are then prefixed.
created in upstream [JIRA|https://issues.apache.org/jira/browse/CAMEL-18771]
was:
When using a route template with hardcoded nodeIDs, then these IDs are used
as-is, and therefore if you create 2+ routes then the 2nd route will have
duplicate.
So you need to use a template parameter and prefix with
id="{{myPrefix}}ValueHere".
We could maybe add a option "nodePrefix" or something that allows users to
create route templates where nodeIDs are then prefixed.
> camel-core - Route template with hardcoded node IDs - Allow to specify prefix
> -
>
> Key: CAMEL-18771
> URL: https://issues.apache.org/jira/browse/CAMEL-18771
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Priority: Major
>
> When using a route template with hardcoded nodeIDs, then these IDs are used
> as-is, and therefore if you create 2+ routes then the 2nd route will have
> duplicate.
> So you need to use a template parameter and prefix with
> id="{{myPrefix}}ValueHere".
> We could maybe add a option "nodePrefix" or something that allows users to
> create route templates where nodeIDs are then prefixed.
> created in upstream [JIRA|https://issues.apache.org/jira/browse/CAMEL-18771]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work stopped] (CAMEL-18416) Upgrade to slf4j 2.0
[ https://issues.apache.org/jira/browse/CAMEL-18416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18416 stopped by Ramu. > Upgrade to slf4j 2.0 > > > Key: CAMEL-18416 > URL: https://issues.apache.org/jira/browse/CAMEL-18416 > Project: Camel > Issue Type: Dependency upgrade > Components: build system >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work stopped] (CAMEL-18577) Camel-Solr: Upgrade to Solr 9.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18577 stopped by Ramu. > Camel-Solr: Upgrade to Solr 9.0.0 > - > > Key: CAMEL-18577 > URL: https://issues.apache.org/jira/browse/CAMEL-18577 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18416) Upgrade to slf4j 2.0
[ https://issues.apache.org/jira/browse/CAMEL-18416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-18416: Assignee: Ramu > Upgrade to slf4j 2.0 > > > Key: CAMEL-18416 > URL: https://issues.apache.org/jira/browse/CAMEL-18416 > Project: Camel > Issue Type: Dependency upgrade > Components: build system >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-18416) Upgrade to slf4j 2.0
[ https://issues.apache.org/jira/browse/CAMEL-18416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18416 started by Ramu. > Upgrade to slf4j 2.0 > > > Key: CAMEL-18416 > URL: https://issues.apache.org/jira/browse/CAMEL-18416 > Project: Camel > Issue Type: Dependency upgrade > Components: build system >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18577) Camel-Solr: Upgrade to Solr 9.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-18577: Assignee: Ramu > Camel-Solr: Upgrade to Solr 9.0.0 > - > > Key: CAMEL-18577 > URL: https://issues.apache.org/jira/browse/CAMEL-18577 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-18577) Camel-Solr: Upgrade to Solr 9.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18577 started by Ramu. > Camel-Solr: Upgrade to Solr 9.0.0 > - > > Key: CAMEL-18577 > URL: https://issues.apache.org/jira/browse/CAMEL-18577 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18121) camel-kafka - Upgrade to Kafka clients 3.2.x
[ https://issues.apache.org/jira/browse/CAMEL-18121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-18121: Assignee: Ramu > camel-kafka - Upgrade to Kafka clients 3.2.x > > > Key: CAMEL-18121 > URL: https://issues.apache.org/jira/browse/CAMEL-18121 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work stopped] (CAMEL-17093) Debezium 1.7.0 - Vitess Connector
[ https://issues.apache.org/jira/browse/CAMEL-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-17093 stopped by Ramu. > Debezium 1.7.0 - Vitess Connector > - > > Key: CAMEL-17093 > URL: https://issues.apache.org/jira/browse/CAMEL-17093 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work started] (CAMEL-17093) Debezium 1.7.0 - Vitess Connector
[ https://issues.apache.org/jira/browse/CAMEL-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-17093 started by Ramu. > Debezium 1.7.0 - Vitess Connector > - > > Key: CAMEL-17093 > URL: https://issues.apache.org/jira/browse/CAMEL-17093 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-17093) Debezium 1.7.0 - Vitess Connector
[ https://issues.apache.org/jira/browse/CAMEL-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17521048#comment-17521048 ] Ramu commented on CAMEL-17093: -- [~acosentino] have you started working on this. can i work on this.? > Debezium 1.7.0 - Vitess Connector > - > > Key: CAMEL-17093 > URL: https://issues.apache.org/jira/browse/CAMEL-17093 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17091) Debezium 1.7.0 - DB2 Connector
[ https://issues.apache.org/jira/browse/CAMEL-17091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516937#comment-17516937 ] Ramu commented on CAMEL-17091: -- Sure > Debezium 1.7.0 - DB2 Connector > -- > > Key: CAMEL-17091 > URL: https://issues.apache.org/jira/browse/CAMEL-17091 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.17.0 > > > https://github.com/apache/camel/pull/7343 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17091) Debezium 1.7.0 - DB2 Connector
[ https://issues.apache.org/jira/browse/CAMEL-17091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516937#comment-17516937 ] Ramu edited comment on CAMEL-17091 at 4/4/22 4:28 PM: -- Sure ,will add spring-boot starter was (Author: ramu11): Sure > Debezium 1.7.0 - DB2 Connector > -- > > Key: CAMEL-17091 > URL: https://issues.apache.org/jira/browse/CAMEL-17091 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.17.0 > > > https://github.com/apache/camel/pull/7343 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (CAMEL-17092) Debezium 1.7.0 - Oracle Connector
[ https://issues.apache.org/jira/browse/CAMEL-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu closed CAMEL-17092. Estimated Complexity: (was: Unknown) > Debezium 1.7.0 - Oracle Connector > - > > Key: CAMEL-17092 > URL: https://issues.apache.org/jira/browse/CAMEL-17092 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.17.0 > > > https://github.com/apache/camel/pull/7314 > https://github.com/apache/camel-spring-boot/pull/495 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17091) Debezium 1.7.0 - DB2 Connector
[ https://issues.apache.org/jira/browse/CAMEL-17091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-17091: - Description: https://github.com/apache/camel/pull/7343 > Debezium 1.7.0 - DB2 Connector > -- > > Key: CAMEL-17091 > URL: https://issues.apache.org/jira/browse/CAMEL-17091 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > https://github.com/apache/camel/pull/7343 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17092) Debezium 1.7.0 - Oracle Connector
[ https://issues.apache.org/jira/browse/CAMEL-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu resolved CAMEL-17092. -- Resolution: Resolved > Debezium 1.7.0 - Oracle Connector > - > > Key: CAMEL-17092 > URL: https://issues.apache.org/jira/browse/CAMEL-17092 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.17.0 > > > https://github.com/apache/camel/pull/7314 > https://github.com/apache/camel-spring-boot/pull/495 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17092) Debezium 1.7.0 - Oracle Connector
[ https://issues.apache.org/jira/browse/CAMEL-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-17092: - Description: https://github.com/apache/camel/pull/7314 https://github.com/apache/camel-spring-boot/pull/495 was:https://github.com/apache/camel/pull/7314 > Debezium 1.7.0 - Oracle Connector > - > > Key: CAMEL-17092 > URL: https://issues.apache.org/jira/browse/CAMEL-17092 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.17.0 > > > https://github.com/apache/camel/pull/7314 > https://github.com/apache/camel-spring-boot/pull/495 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17092) Debezium 1.7.0 - Oracle Connector
[ https://issues.apache.org/jira/browse/CAMEL-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516227#comment-17516227 ] Ramu commented on CAMEL-17092: -- [~davsclaus] sure I will complete it by monday > Debezium 1.7.0 - Oracle Connector > - > > Key: CAMEL-17092 > URL: https://issues.apache.org/jira/browse/CAMEL-17092 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.17.0 > > > https://github.com/apache/camel/pull/7314 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-16024) [camel-mongodb] ChangeStreams Consumer cannot handle string based _id
[
https://issues.apache.org/jira/browse/CAMEL-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515828#comment-17515828
]
Ramu commented on CAMEL-16024:
--
have you tried above suggestion?
> [camel-mongodb] ChangeStreams Consumer cannot handle string based _id
> -
>
> Key: CAMEL-16024
> URL: https://issues.apache.org/jira/browse/CAMEL-16024
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
>Affects Versions: 3.7.0
>Reporter: Dario Nuevo
>Assignee: Ramu
>Priority: Major
> Fix For: 3.x
>
>
> We're having quite a basic use case: Our documents in MongoDB have string
> based IDs (field _id) - as opposed to having ObjectId() instances. It seems,
> the current release of camel-mongodb cannot handle that.
> Having defined a route based on ChangeStreams like that:
> {code}
> from("mongodb:mongoConnection?database=db=changeStreams=coll")
> .routeId("changestream")
>.process("changeStreamProcessor")
>.to("stream:out");
> {code}
> When an event arrives on an object with a string based _id; I get this
> Exception:
> {code}
> Exception in thread "Camel (camel-1) thread #1 - mongodb://mongoConnection"
> org.bson.BsonInvalidOperationException: Value expected to be of type
> OBJECT_ID is of unexpected type STRING
> at org.bson.BsonValue.throwIfInvalidType(BsonValue.java:419)
> at org.bson.BsonValue.asObjectId(BsonValue.java:150)
> at org.bson.BsonDocument.getObjectId(BsonDocument.java:271)
> at
> org.apache.camel.component.mongodb.MongoDbChangeStreamsThread.doRun(MongoDbChangeStreamsThread.java:75)
> at
> org.apache.camel.component.mongodb.MongoAbstractConsumerThread.run(MongoAbstractConsumerThread.java:68)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:830)
> {code}
> So we basically have a problem here:
> https://github.com/apache/camel/blob/camel-3.7.0/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbChangeStreamsThread.java#L75
> So now the fix would be easy - check the type with _instanceof ObjectId_ and
> act accordingly - and i could also contribute that - but I'm not clear if
> that can succeed.
> As I see it, the _id is later set on the header as MongoDbConstants.MONGO_ID
> - which then also would be a string. IMHO that's totally fine, everybody
> knows what type their _id's have.
> How to resolve this? IMHO it's quite a normal use case to have
> non-ObjectId-IDs.. ;-)
> Thanks for any input
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Work started] (CAMEL-17091) Debezium 1.7.0 - DB2 Connector
[ https://issues.apache.org/jira/browse/CAMEL-17091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-17091 started by Ramu. > Debezium 1.7.0 - DB2 Connector > -- > > Key: CAMEL-17091 > URL: https://issues.apache.org/jira/browse/CAMEL-17091 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17091) Debezium 1.7.0 - DB2 Connector
[ https://issues.apache.org/jira/browse/CAMEL-17091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-17091: Assignee: Ramu > Debezium 1.7.0 - DB2 Connector > -- > > Key: CAMEL-17091 > URL: https://issues.apache.org/jira/browse/CAMEL-17091 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17092) Debezium 1.7.0 - Oracle Connector
[ https://issues.apache.org/jira/browse/CAMEL-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-17092: - Description: https://github.com/apache/camel/pull/7314 > Debezium 1.7.0 - Oracle Connector > - > > Key: CAMEL-17092 > URL: https://issues.apache.org/jira/browse/CAMEL-17092 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > https://github.com/apache/camel/pull/7314 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17092) Debezium 1.7.0 - Oracle Connector
[ https://issues.apache.org/jira/browse/CAMEL-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515708#comment-17515708 ] Ramu edited comment on CAMEL-17092 at 4/1/22 5:09 AM: -- I have started working on this. I am almost done will commit soon was (Author: ramu11): I have started working on this. > Debezium 1.7.0 - Oracle Connector > - > > Key: CAMEL-17092 > URL: https://issues.apache.org/jira/browse/CAMEL-17092 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17092) Debezium 1.7.0 - Oracle Connector
[ https://issues.apache.org/jira/browse/CAMEL-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515708#comment-17515708 ] Ramu commented on CAMEL-17092: -- I have started working on this. > Debezium 1.7.0 - Oracle Connector > - > > Key: CAMEL-17092 > URL: https://issues.apache.org/jira/browse/CAMEL-17092 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (CAMEL-17092) Debezium 1.7.0 - Oracle Connector
[ https://issues.apache.org/jira/browse/CAMEL-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-17092 started by Ramu. > Debezium 1.7.0 - Oracle Connector > - > > Key: CAMEL-17092 > URL: https://issues.apache.org/jira/browse/CAMEL-17092 > Project: Camel > Issue Type: Sub-task > Components: camel-debezium >Reporter: Andrea Cosentino >Assignee: Ramu >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17705) Camel Salesforce - Http Client timeout is hardcoded
[
https://issues.apache.org/jira/browse/CAMEL-17705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499856#comment-17499856
]
Ramu edited comment on CAMEL-17705 at 4/1/22 2:03 AM:
--
static final int CONNECTION_TIMEOUT = 6; //hardcoded
@Metadata(description = "Connection timeout used by the HttpClient when
connecting to the Salesforce server.",
label = "common", defaultValue = "" + CONNECTION_TIMEOUT)
private long httpClientConnectionTimeout = CONNECTION_TIMEOUT;
putValueIfGivenTo(httpClientProperties, HTTP_CONNECTION_TIMEOUT,
salesforce::getHttpClientConnectionTimeout);
[~jawwad124] how you are passing httpClient values could you please share your
configuration?
> Camel Salesforce - Http Client timeout is hardcoded
> ---
>
> Key: CAMEL-17705
> URL: https://issues.apache.org/jira/browse/CAMEL-17705
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
>Affects Versions: 3.14.0, 3.15.0
>Reporter: Jawad Ahmad
>Assignee: Jeremy Ross
>Priority: Major
> Fix For: 3.17.0
>
>
> I am using Bulk V2 API to upload large files to Salesforce. I have noticed
> that on creating the job from Producer it times out with Timeout exception. I
> tried to change the timeout configuration but noticed its always gets set to
> a hardcoded one.
> Class : SalesforceComponent
> {code:java}
> static SalesforceHttpClient createHttpClient(
> Object source, final SslContextFactory sslContextFactory, final
> CamelContext context, int workerPoolSize,
> int workerPoolMaxSize) {
> SecurityUtils.adaptToIBMCipherNames(sslContextFactory);
> final SalesforceHttpClient httpClient = new SalesforceHttpClient(
> context,
> context.getExecutorServiceManager().newThreadPool(source,
> "SalesforceHttpClient", workerPoolSize,
> workerPoolMaxSize),
> sslContextFactory);
> // default settings, use httpClientProperties to set other
> // properties
> httpClient.setConnectTimeout(CONNECTION_TIMEOUT);
> httpClient.setIdleTimeout(IDLE_TIMEOUT);
> return httpClient;
> }
> {code}
> As suggested by Claus to use httpClientProperties. In that case, HTTP client
> does set the connection timeout of the configured value. But it passes
> timeout value to SalesforceSession instead of ConnectionTimeout value. So it
> still gets failed with a Timeout error.
> Class : SalesforceComponent
> Method: doStart
> {code:java}
> setupHttpClient(httpClient, getCamelContext(), httpClientProperties);
> // support restarts
> if (session == null) {
> session = new SalesforceSession(getCamelContext(), httpClient,
> httpClient.getTimeout(), loginConfig);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (CAMEL-17705) Camel Salesforce - Http Client timout is hardcoded
[
https://issues.apache.org/jira/browse/CAMEL-17705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramu reassigned CAMEL-17705:
Assignee: Ramu
> Camel Salesforce - Http Client timout is hardcoded
> --
>
> Key: CAMEL-17705
> URL: https://issues.apache.org/jira/browse/CAMEL-17705
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
>Affects Versions: 3.14.0, 3.15.0
>Reporter: Jawad Ahmad
>Assignee: Ramu
>Priority: Major
>
> I am using Bulk V2 API to upload large files to Salesforce. I have noticed
> that on creating the job from Producer it times out with Timeout exception. I
> tried to change the timeout configuration but noticed its always gets set to
> a hardcoded one.
> Class : SalesforceComponent
> {code:java}
> static SalesforceHttpClient createHttpClient(
> Object source, final SslContextFactory sslContextFactory, final
> CamelContext context, int workerPoolSize,
> int workerPoolMaxSize) {
> SecurityUtils.adaptToIBMCipherNames(sslContextFactory);
> final SalesforceHttpClient httpClient = new SalesforceHttpClient(
> context,
> context.getExecutorServiceManager().newThreadPool(source,
> "SalesforceHttpClient", workerPoolSize,
> workerPoolMaxSize),
> sslContextFactory);
> // default settings, use httpClientProperties to set other
> // properties
> httpClient.setConnectTimeout(CONNECTION_TIMEOUT);
> httpClient.setIdleTimeout(IDLE_TIMEOUT);
> return httpClient;
> }
> {code}
> As suggested by Claus to use httpClientProperties. In that case, HTTP client
> does set the connection timeout of the configured value. But it passes
> timeout value to SalesforceSession instead of ConnectionTimeout value. So it
> still gets failed with a Timeout error.
> Class : SalesforceComponent
> Method: doStart
> {code:java}
> setupHttpClient(httpClient, getCamelContext(), httpClientProperties);
> // support restarts
> if (session == null) {
> session = new SalesforceSession(getCamelContext(), httpClient,
> httpClient.getTimeout(), loginConfig);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17469) camel-jackson - Upgrade to 2.13.x
[ https://issues.apache.org/jira/browse/CAMEL-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17475955#comment-17475955 ] Ramu commented on CAMEL-17469: -- PR:https://github.com/apache/camel/pull/6734 > camel-jackson - Upgrade to 2.13.x > - > > Key: CAMEL-17469 > URL: https://issues.apache.org/jira/browse/CAMEL-17469 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.15.0 > > > We are on 2.12, but there is a 2.13. > However it would be good to check up on what spring boot / quarkus uses to > better align with them too. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17469) camel-jackson - Upgrade to 2.13.x
[ https://issues.apache.org/jira/browse/CAMEL-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu resolved CAMEL-17469. -- Resolution: Fixed > camel-jackson - Upgrade to 2.13.x > - > > Key: CAMEL-17469 > URL: https://issues.apache.org/jira/browse/CAMEL-17469 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.15.0 > > > We are on 2.12, but there is a 2.13. > However it would be good to check up on what spring boot / quarkus uses to > better align with them too. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17469) camel-jackson - Upgrade to 2.13.x
[ https://issues.apache.org/jira/browse/CAMEL-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-17469: Assignee: Ramu > camel-jackson - Upgrade to 2.13.x > - > > Key: CAMEL-17469 > URL: https://issues.apache.org/jira/browse/CAMEL-17469 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > We are on 2.12, but there is a 2.13. > However it would be good to check up on what spring boot / quarkus uses to > better align with them too. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (CAMEL-17469) camel-jackson - Upgrade to 2.13.x
[ https://issues.apache.org/jira/browse/CAMEL-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-17469 started by Ramu. > camel-jackson - Upgrade to 2.13.x > - > > Key: CAMEL-17469 > URL: https://issues.apache.org/jira/browse/CAMEL-17469 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > We are on 2.12, but there is a 2.13. > However it would be good to check up on what spring boot / quarkus uses to > better align with them too. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17284) camel-kafka - Upgrade to kafka clients 3.0.x
[ https://issues.apache.org/jira/browse/CAMEL-17284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-17284: Assignee: Ramu > camel-kafka - Upgrade to kafka clients 3.0.x > > > Key: CAMEL-17284 > URL: https://issues.apache.org/jira/browse/CAMEL-17284 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.15.0 > > > We should upgrade to newer kafka clients. > They should be backwards compatible and major runtimes like SB and Quarkus > is/have upgraded too. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (CAMEL-17116) components - Loading resource from classpath should use ClassResolver API
[
https://issues.apache.org/jira/browse/CAMEL-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-17116 started by Ramu.
> components - Loading resource from classpath should use ClassResolver API
> -
>
> Key: CAMEL-17116
> URL: https://issues.apache.org/jira/browse/CAMEL-17116
> Project: Camel
> Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Ramu
>Priority: Major
> Fix For: 3.13.0
>
>
> See CAMEL-17114
> There are a number of components that load resources from classpath as:
> {code}
> camel-infinispan/camel-infinispan-common/src/main/java/org/apache/camel/component/infinispan/InfinispanUtil.java:
> return
> Thread.currentThread().getContextClassLoader().getResourceAsStream(uri);
> camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java:
> try (InputStream is =
> this.getClass().getResourceAsStream("/global-camel-routes.xml")) {
> camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java:
> try (InputStream is =
> classloader.getResourceAsStream("camel-routes.xml")) {
> camel-jira/src/main/java/org/apache/camel/component/jira/oauth/OAuthAsynchronousHttpClientFactory.java:
> try (InputStream resourceAsStream =
> AuthenticationHandler.class.getResourceAsStream(pomProps)) {
> camel-jslt/src/main/java/org/apache/camel/component/jslt/JsltEndpoint.java:
> stream =
> JsltEndpoint.class.getClassLoader().getResourceAsStream(getResourceUri());
> camel-quartz/src/main/java/org/apache/camel/component/quartz/QuartzComponent.java:
> InputStream is =
> StdSchedulerFactory.class.getClassLoader().getResourceAsStream("org/quartz/quartz.properties");
> camel-schematron/src/main/java/org/apache/camel/component/schematron/processor/ClassPathURIResolver.java:
> .getResourceAsStream(rulesDir.concat("/").concat(href));
> camel-schematron/src/main/java/org/apache/camel/component/schematron/processor/TemplatesFactory.java:
> InputStream xsl =
> this.getClass().getClassLoader().getResourceAsStream(path);
> camel-xmlsecurity/src/main/java/org/apache/camel/component/xmlsecurity/api/XmlSignatureHelper.java:
> return XmlSignatureHelper.class.getResourceAsStream(path);
> {code}
> Instead we should use ClassResolver API via CamelContext - This has the
> mehanism to load correctly in different runtimes - standalone, OSGi, spring
> boot, quarkus etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work stopped] (CAMEL-17116) components - Loading resource from classpath should use ClassResolver API
[
https://issues.apache.org/jira/browse/CAMEL-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-17116 stopped by Ramu.
> components - Loading resource from classpath should use ClassResolver API
> -
>
> Key: CAMEL-17116
> URL: https://issues.apache.org/jira/browse/CAMEL-17116
> Project: Camel
> Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Ramu
>Priority: Major
> Fix For: 3.13.0
>
>
> See CAMEL-17114
> There are a number of components that load resources from classpath as:
> {code}
> camel-infinispan/camel-infinispan-common/src/main/java/org/apache/camel/component/infinispan/InfinispanUtil.java:
> return
> Thread.currentThread().getContextClassLoader().getResourceAsStream(uri);
> camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java:
> try (InputStream is =
> this.getClass().getResourceAsStream("/global-camel-routes.xml")) {
> camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java:
> try (InputStream is =
> classloader.getResourceAsStream("camel-routes.xml")) {
> camel-jira/src/main/java/org/apache/camel/component/jira/oauth/OAuthAsynchronousHttpClientFactory.java:
> try (InputStream resourceAsStream =
> AuthenticationHandler.class.getResourceAsStream(pomProps)) {
> camel-jslt/src/main/java/org/apache/camel/component/jslt/JsltEndpoint.java:
> stream =
> JsltEndpoint.class.getClassLoader().getResourceAsStream(getResourceUri());
> camel-quartz/src/main/java/org/apache/camel/component/quartz/QuartzComponent.java:
> InputStream is =
> StdSchedulerFactory.class.getClassLoader().getResourceAsStream("org/quartz/quartz.properties");
> camel-schematron/src/main/java/org/apache/camel/component/schematron/processor/ClassPathURIResolver.java:
> .getResourceAsStream(rulesDir.concat("/").concat(href));
> camel-schematron/src/main/java/org/apache/camel/component/schematron/processor/TemplatesFactory.java:
> InputStream xsl =
> this.getClass().getClassLoader().getResourceAsStream(path);
> camel-xmlsecurity/src/main/java/org/apache/camel/component/xmlsecurity/api/XmlSignatureHelper.java:
> return XmlSignatureHelper.class.getResourceAsStream(path);
> {code}
> Instead we should use ClassResolver API via CamelContext - This has the
> mehanism to load correctly in different runtimes - standalone, OSGi, spring
> boot, quarkus etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-17120) camel-xmlsecurity:Test cases failing
Ramu created CAMEL-17120:
Summary: camel-xmlsecurity:Test cases failing
Key: CAMEL-17120
URL: https://issues.apache.org/jira/browse/CAMEL-17120
Project: Camel
Issue Type: Test
Components: camel-xmlsecurity
Affects Versions: 3.12.0
Reporter: Ramu
{code:java}
[ERROR]
org.apache.camel.component.xmlsecurity.XmlSignatureTest.testExceptionDetachedXpathInvalid
Time elapsed: 0.038 s <<< ERROR!
java.lang.IllegalStateException: java.lang.IllegalStateException: XSL file
/org/apache/camel/component/xmlsecurity/xslt_test.xsl not found
at
org.apache.camel.component.xmlsecurity.XmlSignatureTest.getTransformsXsltXpath(XmlSignatureTest.java:1534)
at
org.apache.camel.component.xmlsecurity.XmlSignatureTest.createCamelRegistry(XmlSignatureTest.java:141)
at
org.apache.camel.test.junit5.CamelTestSupport.createCamelContext(CamelTestSupport.java:763)
at
org.apache.camel.test.junit5.CamelTestSupport.doSetUp(CamelTestSupport.java:427)
at
org.apache.camel.test.junit5.CamelTestSupport.setUp(CamelTestSupport.java:382)
at
org.apache.camel.component.xmlsecurity.XmlSignatureTest.setUp(XmlSignatureTest.java:1456)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:688)
at
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
at
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
at
org.junit.jupiter.engine.extension.TimeoutExtension.interceptLifecycleMethod(TimeoutExtension.java:126)
at
org.junit.jupiter.engine.extension.TimeoutExtension.interceptBeforeEachMethod(TimeoutExtension.java:76)
at
org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
at
org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
at
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:104)
at
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:98)
at
org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.invokeMethodInExtensionContext(ClassBasedTestDescriptor.java:490)
at
org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.lambda$synthesizeBeforeEachMethodAdapter$19(ClassBasedTestDescriptor.java:475)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeEachMethods$2(TestMethodTestDescriptor.java:167)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeMethodsOrCallbacksUntilExceptionOccurs$5(TestMethodTestDescriptor.java:195)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeMethodsOrCallbacksUntilExceptionOccurs(TestMethodTestDescriptor.java:195)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeEachMethods(TestMethodTestDescriptor.java:164)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:127)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:65)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:139)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$7(NodeTestTask.java:129)
at
org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:127)
at
[jira] [Work started] (CAMEL-17116) components - Loading resource from classpath should use ClassResolver API
[
https://issues.apache.org/jira/browse/CAMEL-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-17116 started by Ramu.
> components - Loading resource from classpath should use ClassResolver API
> -
>
> Key: CAMEL-17116
> URL: https://issues.apache.org/jira/browse/CAMEL-17116
> Project: Camel
> Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Ramu
>Priority: Major
> Fix For: 3.13.0
>
>
> See CAMEL-17114
> There are a number of components that load resources from classpath as:
> {code}
> camel-infinispan/camel-infinispan-common/src/main/java/org/apache/camel/component/infinispan/InfinispanUtil.java:
> return
> Thread.currentThread().getContextClassLoader().getResourceAsStream(uri);
> camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java:
> try (InputStream is =
> this.getClass().getResourceAsStream("/global-camel-routes.xml")) {
> camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java:
> try (InputStream is =
> classloader.getResourceAsStream("camel-routes.xml")) {
> camel-jira/src/main/java/org/apache/camel/component/jira/oauth/OAuthAsynchronousHttpClientFactory.java:
> try (InputStream resourceAsStream =
> AuthenticationHandler.class.getResourceAsStream(pomProps)) {
> camel-jslt/src/main/java/org/apache/camel/component/jslt/JsltEndpoint.java:
> stream =
> JsltEndpoint.class.getClassLoader().getResourceAsStream(getResourceUri());
> camel-quartz/src/main/java/org/apache/camel/component/quartz/QuartzComponent.java:
> InputStream is =
> StdSchedulerFactory.class.getClassLoader().getResourceAsStream("org/quartz/quartz.properties");
> camel-schematron/src/main/java/org/apache/camel/component/schematron/processor/ClassPathURIResolver.java:
> .getResourceAsStream(rulesDir.concat("/").concat(href));
> camel-schematron/src/main/java/org/apache/camel/component/schematron/processor/TemplatesFactory.java:
> InputStream xsl =
> this.getClass().getClassLoader().getResourceAsStream(path);
> camel-xmlsecurity/src/main/java/org/apache/camel/component/xmlsecurity/api/XmlSignatureHelper.java:
> return XmlSignatureHelper.class.getResourceAsStream(path);
> {code}
> Instead we should use ClassResolver API via CamelContext - This has the
> mehanism to load correctly in different runtimes - standalone, OSGi, spring
> boot, quarkus etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-17116) components - Loading resource from classpath should use ClassResolver API
[
https://issues.apache.org/jira/browse/CAMEL-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramu reassigned CAMEL-17116:
Assignee: Ramu
> components - Loading resource from classpath should use ClassResolver API
> -
>
> Key: CAMEL-17116
> URL: https://issues.apache.org/jira/browse/CAMEL-17116
> Project: Camel
> Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Ramu
>Priority: Major
> Fix For: 3.13.0
>
>
> See CAMEL-17114
> There are a number of components that load resources from classpath as:
> {code}
> camel-infinispan/camel-infinispan-common/src/main/java/org/apache/camel/component/infinispan/InfinispanUtil.java:
> return
> Thread.currentThread().getContextClassLoader().getResourceAsStream(uri);
> camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java:
> try (InputStream is =
> this.getClass().getResourceAsStream("/global-camel-routes.xml")) {
> camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java:
> try (InputStream is =
> classloader.getResourceAsStream("camel-routes.xml")) {
> camel-jira/src/main/java/org/apache/camel/component/jira/oauth/OAuthAsynchronousHttpClientFactory.java:
> try (InputStream resourceAsStream =
> AuthenticationHandler.class.getResourceAsStream(pomProps)) {
> camel-jslt/src/main/java/org/apache/camel/component/jslt/JsltEndpoint.java:
> stream =
> JsltEndpoint.class.getClassLoader().getResourceAsStream(getResourceUri());
> camel-quartz/src/main/java/org/apache/camel/component/quartz/QuartzComponent.java:
> InputStream is =
> StdSchedulerFactory.class.getClassLoader().getResourceAsStream("org/quartz/quartz.properties");
> camel-schematron/src/main/java/org/apache/camel/component/schematron/processor/ClassPathURIResolver.java:
> .getResourceAsStream(rulesDir.concat("/").concat(href));
> camel-schematron/src/main/java/org/apache/camel/component/schematron/processor/TemplatesFactory.java:
> InputStream xsl =
> this.getClass().getClassLoader().getResourceAsStream(path);
> camel-xmlsecurity/src/main/java/org/apache/camel/component/xmlsecurity/api/XmlSignatureHelper.java:
> return XmlSignatureHelper.class.getResourceAsStream(path);
> {code}
> Instead we should use ClassResolver API via CamelContext - This has the
> mehanism to load correctly in different runtimes - standalone, OSGi, spring
> boot, quarkus etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work stopped] (CAMEL-16656) camel-core - RoutesLoader SPI - Allow to reload on changes
[ https://issues.apache.org/jira/browse/CAMEL-16656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-16656 stopped by Ramu. > camel-core - RoutesLoader SPI - Allow to reload on changes > -- > > Key: CAMEL-16656 > URL: https://issues.apache.org/jira/browse/CAMEL-16656 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > Add some kind of feature to the RoutesLoader SPI whether it supports > re-loading, such as the file based from yaml, or xml (though its harder to > reload from classpath). But from file source or over http/github it can > reload. > We had in the past some file watcher thingy that could re-load routes if the > file was changed/save. > This allows to play with kamelets, xml | yaml routes etc from vanilla camel. > For example to change this route > https://github.com/apache/camel-examples/tree/main/examples/kamelet-main/src/main/resources/camel > While the app is running, then we can have a mode where camel detects changes > and reload the routes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16656) camel-core - RoutesLoader SPI - Allow to reload on changes
[ https://issues.apache.org/jira/browse/CAMEL-16656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-16656: Assignee: Ramu > camel-core - RoutesLoader SPI - Allow to reload on changes > -- > > Key: CAMEL-16656 > URL: https://issues.apache.org/jira/browse/CAMEL-16656 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > Add some kind of feature to the RoutesLoader SPI whether it supports > re-loading, such as the file based from yaml, or xml (though its harder to > reload from classpath). But from file source or over http/github it can > reload. > We had in the past some file watcher thingy that could re-load routes if the > file was changed/save. > This allows to play with kamelets, xml | yaml routes etc from vanilla camel. > For example to change this route > https://github.com/apache/camel-examples/tree/main/examples/kamelet-main/src/main/resources/camel > While the app is running, then we can have a mode where camel detects changes > and reload the routes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-16656) camel-core - RoutesLoader SPI - Allow to reload on changes
[ https://issues.apache.org/jira/browse/CAMEL-16656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-16656 started by Ramu. > camel-core - RoutesLoader SPI - Allow to reload on changes > -- > > Key: CAMEL-16656 > URL: https://issues.apache.org/jira/browse/CAMEL-16656 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > Add some kind of feature to the RoutesLoader SPI whether it supports > re-loading, such as the file based from yaml, or xml (though its harder to > reload from classpath). But from file source or over http/github it can > reload. > We had in the past some file watcher thingy that could re-load routes if the > file was changed/save. > This allows to play with kamelets, xml | yaml routes etc from vanilla camel. > For example to change this route > https://github.com/apache/camel-examples/tree/main/examples/kamelet-main/src/main/resources/camel > While the app is running, then we can have a mode where camel detects changes > and reload the routes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-17083) camel-debezium - More database connectors
[ https://issues.apache.org/jira/browse/CAMEL-17083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17429074#comment-17429074 ] Ramu commented on CAMEL-17083: -- yes I will start with oracle first. It would be better to create sub-tasks for every component It would be easy to track and work > camel-debezium - More database connectors > - > > Key: CAMEL-17083 > URL: https://issues.apache.org/jira/browse/CAMEL-17083 > Project: Camel > Issue Type: New Feature > Components: camel-debezium >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.13.0 > > > debezium 1.7 have more connectors out of the box. > We need to generate camel components for > - oracle > - db2 > - cassandra > - vitess -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15842) camel-cdi - Drop 1.x workarounds
[ https://issues.apache.org/jira/browse/CAMEL-15842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-15842: Assignee: Ramu > camel-cdi - Drop 1.x workarounds > > > Key: CAMEL-15842 > URL: https://issues.apache.org/jira/browse/CAMEL-15842 > Project: Camel > Issue Type: Improvement > Components: camel-cdi >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > camel-cdi has dropped CDI 1.x support but there are some leftovers for 1.x > and 2.0 workarounds from the past. We should cleanup this module. > See talks at > https://github.com/apache/camel/pull/4562 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16024) [camel-mongodb] ChangeStreams Consumer cannot handle string based _id
[
https://issues.apache.org/jira/browse/CAMEL-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramu reassigned CAMEL-16024:
Assignee: Ramu
> [camel-mongodb] ChangeStreams Consumer cannot handle string based _id
> -
>
> Key: CAMEL-16024
> URL: https://issues.apache.org/jira/browse/CAMEL-16024
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
>Affects Versions: 3.7.0
>Reporter: Dario Nuevo
>Assignee: Ramu
>Priority: Major
> Fix For: 3.x
>
>
> We're having quite a basic use case: Our documents in MongoDB have string
> based IDs (field _id) - as opposed to having ObjectId() instances. It seems,
> the current release of camel-mongodb cannot handle that.
> Having defined a route based on ChangeStreams like that:
> {code}
> from("mongodb:mongoConnection?database=db=changeStreams=coll")
> .routeId("changestream")
>.process("changeStreamProcessor")
>.to("stream:out");
> {code}
> When an event arrives on an object with a string based _id; I get this
> Exception:
> {code}
> Exception in thread "Camel (camel-1) thread #1 - mongodb://mongoConnection"
> org.bson.BsonInvalidOperationException: Value expected to be of type
> OBJECT_ID is of unexpected type STRING
> at org.bson.BsonValue.throwIfInvalidType(BsonValue.java:419)
> at org.bson.BsonValue.asObjectId(BsonValue.java:150)
> at org.bson.BsonDocument.getObjectId(BsonDocument.java:271)
> at
> org.apache.camel.component.mongodb.MongoDbChangeStreamsThread.doRun(MongoDbChangeStreamsThread.java:75)
> at
> org.apache.camel.component.mongodb.MongoAbstractConsumerThread.run(MongoAbstractConsumerThread.java:68)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:830)
> {code}
> So we basically have a problem here:
> https://github.com/apache/camel/blob/camel-3.7.0/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbChangeStreamsThread.java#L75
> So now the fix would be easy - check the type with _instanceof ObjectId_ and
> act accordingly - and i could also contribute that - but I'm not clear if
> that can succeed.
> As I see it, the _id is later set on the header as MongoDbConstants.MONGO_ID
> - which then also would be a string. IMHO that's totally fine, everybody
> knows what type their _id's have.
> How to resolve this? IMHO it's quite a normal use case to have
> non-ObjectId-IDs.. ;-)
> Thanks for any input
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16784) camel-ftp - Disable some FTP tests
[ https://issues.apache.org/jira/browse/CAMEL-16784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu resolved CAMEL-16784. -- Resolution: Fixed > camel-ftp - Disable some FTP tests > -- > > Key: CAMEL-16784 > URL: https://issues.apache.org/jira/browse/CAMEL-16784 > Project: Camel > Issue Type: Test > Components: camel-ftp >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.12.0 > > > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithoutClientAuthAndGlobalSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithoutClientAuthAndSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithoutClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithClientAuthAndSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithoutClientAuthAndSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithoutClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsWithCustomKeyAndTrustStorePropertiesIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsWithCustomTrustStorePropertiesIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsWithFtpClientConfigRefIT.testFromFileToFtp -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-16784) camel-ftp - Disable some FTP tests
[ https://issues.apache.org/jira/browse/CAMEL-16784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-16784 started by Ramu. > camel-ftp - Disable some FTP tests > -- > > Key: CAMEL-16784 > URL: https://issues.apache.org/jira/browse/CAMEL-16784 > Project: Camel > Issue Type: Test > Components: camel-ftp >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.12.0 > > > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithoutClientAuthAndGlobalSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithoutClientAuthAndSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithoutClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithClientAuthAndSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithoutClientAuthAndSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithoutClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsWithCustomKeyAndTrustStorePropertiesIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsWithCustomTrustStorePropertiesIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsWithFtpClientConfigRefIT.testFromFileToFtp -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (CAMEL-16774) camel-debezium - Upgrade to 1.6
[ https://issues.apache.org/jira/browse/CAMEL-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-16774: - Comment: was deleted (was: I will look into it ) > camel-debezium - Upgrade to 1.6 > --- > > Key: CAMEL-16774 > URL: https://issues.apache.org/jira/browse/CAMEL-16774 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-16774) camel-debezium - Upgrade to 1.6
[ https://issues.apache.org/jira/browse/CAMEL-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-16774 started by Ramu. > camel-debezium - Upgrade to 1.6 > --- > > Key: CAMEL-16774 > URL: https://issues.apache.org/jira/browse/CAMEL-16774 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16784) camel-ftp - Disable some FTP tests
[ https://issues.apache.org/jira/browse/CAMEL-16784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-16784: Assignee: Ramu > camel-ftp - Disable some FTP tests > -- > > Key: CAMEL-16784 > URL: https://issues.apache.org/jira/browse/CAMEL-16784 > Project: Camel > Issue Type: Test > Components: camel-ftp >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.12.0 > > > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithoutClientAuthAndGlobalSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithoutClientAuthAndSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsExplicitSSLWithoutClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithClientAuthAndSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithoutClientAuthAndSSLContextParametersIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsImplicitSSLWithoutClientAuthIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsWithCustomKeyAndTrustStorePropertiesIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsWithCustomTrustStorePropertiesIT.testFromFileToFtp > org.apache.camel.component.file.remote.integration.FileToFtpsWithFtpClientConfigRefIT.testFromFileToFtp -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16774) camel-debezium - Upgrade to 1.6
[ https://issues.apache.org/jira/browse/CAMEL-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-16774: Assignee: Ramu > camel-debezium - Upgrade to 1.6 > --- > > Key: CAMEL-16774 > URL: https://issues.apache.org/jira/browse/CAMEL-16774 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16771) camel-spring-boot - Upgrade to 2.5.2
[ https://issues.apache.org/jira/browse/CAMEL-16771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-16771: Assignee: Ramu > camel-spring-boot - Upgrade to 2.5.2 > > > Key: CAMEL-16771 > URL: https://issues.apache.org/jira/browse/CAMEL-16771 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.11.1, 3.12.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16774) camel-debezium - Upgrade to 1.6
[ https://issues.apache.org/jira/browse/CAMEL-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17372768#comment-17372768 ] Ramu commented on CAMEL-16774: -- I will look into it > camel-debezium - Upgrade to 1.6 > --- > > Key: CAMEL-16774 > URL: https://issues.apache.org/jira/browse/CAMEL-16774 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16414) camel-kafka set custom timestamp
[ https://issues.apache.org/jira/browse/CAMEL-16414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320622#comment-17320622 ] Ramu commented on CAMEL-16414: -- [~jenskordowski] we have discussed accepting date in String format. But kafkaProducer class accepts time in Long format. so we have to do lot of transformations depending on the input time format. There are lot of time formats we can set in String and it does eventually adds complexity at camel-kafka side. Please raise a new Jira with the Improvement to provide time as string format. In this case camel-kafka should have a utility/helper method to convert string date format to Long format . Helper method should accept all existing time formats and have a logic to convert to Long Coming to other question ,if any jira in un assigned state. any body can own and work. if you want to work on jira own and change to inprogress. If you can not own jira,then at least update the jira saying working on the jira so that others know some body is already working > camel-kafka set custom timestamp > > > Key: CAMEL-16414 > URL: https://issues.apache.org/jira/browse/CAMEL-16414 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Affects Versions: 2.25.3, 3.8.0 >Reporter: Jens Kordowski >Assignee: Ramu >Priority: Major > Fix For: 3.10.0 > > > The kafka producer supports the possibility to pass on a (custom) timestamp > with the record. The camel-kafka component does not leverage this, currently. > A Camel header seems like a good option to provide this. The consumer already > creates a kafka.TIMESTAMP header (not yet documented). I suggest to use a > different header to avoid misconfiguration in case of "kafka to kafka" > scenarios. kafka.OVERRIDE_TIMESTAMP (being a one-time header) looks like a > good idea, similar to the existing kafka.OVERRIDE_TOPIC. > What do you think? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16481) camel-vertx-kafka set custom timestamp
[ https://issues.apache.org/jira/browse/CAMEL-16481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-16481: - Summary: camel-vertx-kafka set custom timestamp (was: vertx-kafka set custom timestamp ) > camel-vertx-kafka set custom timestamp > --- > > Key: CAMEL-16481 > URL: https://issues.apache.org/jira/browse/CAMEL-16481 > Project: Camel > Issue Type: Improvement > Components: camel-vertx >Affects Versions: 2.25.3, 3.8.0 >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.10.0 > > > Implement CAMEL-16414:camel-kafka set custom timestamp for vertx-kafka -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16481) vertx-kafka set custom timestamp
[ https://issues.apache.org/jira/browse/CAMEL-16481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-16481: - Component/s: camel-vertx > vertx-kafka set custom timestamp > - > > Key: CAMEL-16481 > URL: https://issues.apache.org/jira/browse/CAMEL-16481 > Project: Camel > Issue Type: Improvement > Components: camel-vertx >Affects Versions: 2.25.3, 3.8.0 >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.10.0 > > > Implement CAMEL-16414:camel-kafka set custom timestamp for vertx-kafka -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-16481) vertx-kafka set custom timestamp
[ https://issues.apache.org/jira/browse/CAMEL-16481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-16481 started by Ramu. > vertx-kafka set custom timestamp > - > > Key: CAMEL-16481 > URL: https://issues.apache.org/jira/browse/CAMEL-16481 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.25.3, 3.8.0 >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.10.0 > > > Implement CAMEL-16414:camel-kafka set custom timestamp for vertx-kafka -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16481) vertx-kafka set custom timestamp
[ https://issues.apache.org/jira/browse/CAMEL-16481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-16481: - Description: Implement CAMEL-16414:camel-kafka set custom timestamp for vertx-kafka was: The kafka producer supports the possibility to pass on a (custom) timestamp with the record. The camel-kafka component does not leverage this, currently. A Camel header seems like a good option to provide this. The consumer already creates a kafka.TIMESTAMP header (not yet documented). I suggest to use a different header to avoid misconfiguration in case of "kafka to kafka" scenarios. kafka.OVERRIDE_TIMESTAMP (being a one-time header) looks like a good idea, similar to the existing kafka.OVERRIDE_TOPIC. What do you think? > vertx-kafka set custom timestamp > - > > Key: CAMEL-16481 > URL: https://issues.apache.org/jira/browse/CAMEL-16481 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.25.3, 3.8.0 >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.10.0 > > > Implement CAMEL-16414:camel-kafka set custom timestamp for vertx-kafka -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16481) vertx-kafka set custom timestamp
Ramu created CAMEL-16481: Summary: vertx-kafka set custom timestamp Key: CAMEL-16481 URL: https://issues.apache.org/jira/browse/CAMEL-16481 Project: Camel Issue Type: Improvement Components: camel-kafka Affects Versions: 2.25.3, 3.8.0 Reporter: Ramu Assignee: Ramu Fix For: 3.10.0 The kafka producer supports the possibility to pass on a (custom) timestamp with the record. The camel-kafka component does not leverage this, currently. A Camel header seems like a good option to provide this. The consumer already creates a kafka.TIMESTAMP header (not yet documented). I suggest to use a different header to avoid misconfiguration in case of "kafka to kafka" scenarios. kafka.OVERRIDE_TIMESTAMP (being a one-time header) looks like a good idea, similar to the existing kafka.OVERRIDE_TOPIC. What do you think? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16481) vertx-kafka set custom timestamp
[ https://issues.apache.org/jira/browse/CAMEL-16481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-16481: - Component/s: (was: camel-kafka) > vertx-kafka set custom timestamp > - > > Key: CAMEL-16481 > URL: https://issues.apache.org/jira/browse/CAMEL-16481 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.25.3, 3.8.0 >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.10.0 > > > The kafka producer supports the possibility to pass on a (custom) timestamp > with the record. The camel-kafka component does not leverage this, currently. > A Camel header seems like a good option to provide this. The consumer already > creates a kafka.TIMESTAMP header (not yet documented). I suggest to use a > different header to avoid misconfiguration in case of "kafka to kafka" > scenarios. kafka.OVERRIDE_TIMESTAMP (being a one-time header) looks like a > good idea, similar to the existing kafka.OVERRIDE_TOPIC. > What do you think? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16414) camel-kafka set custom timestamp
[ https://issues.apache.org/jira/browse/CAMEL-16414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317219#comment-17317219 ] Ramu commented on CAMEL-16414: -- Hi it is done.i have already raised pull request. > camel-kafka set custom timestamp > > > Key: CAMEL-16414 > URL: https://issues.apache.org/jira/browse/CAMEL-16414 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Affects Versions: 2.25.3, 3.8.0 >Reporter: Jens Kordowski >Assignee: Ramu >Priority: Major > Fix For: 3.10.0 > > > The kafka producer supports the possibility to pass on a (custom) timestamp > with the record. The camel-kafka component does not leverage this, currently. > A Camel header seems like a good option to provide this. The consumer already > creates a kafka.TIMESTAMP header (not yet documented). I suggest to use a > different header to avoid misconfiguration in case of "kafka to kafka" > scenarios. kafka.OVERRIDE_TIMESTAMP (being a one-time header) looks like a > good idea, similar to the existing kafka.OVERRIDE_TOPIC. > What do you think? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16414) camel-kafka set custom timestamp
[ https://issues.apache.org/jira/browse/CAMEL-16414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-16414: Assignee: Ramu > camel-kafka set custom timestamp > > > Key: CAMEL-16414 > URL: https://issues.apache.org/jira/browse/CAMEL-16414 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Affects Versions: 2.25.3, 3.8.0 >Reporter: Jens Kordowski >Assignee: Ramu >Priority: Major > Fix For: 3.10.0 > > > The kafka producer supports the possibility to pass on a (custom) timestamp > with the record. The camel-kafka component does not leverage this, currently. > A Camel header seems like a good option to provide this. The consumer already > creates a kafka.TIMESTAMP header (not yet documented). I suggest to use a > different header to avoid misconfiguration in case of "kafka to kafka" > scenarios. kafka.OVERRIDE_TIMESTAMP (being a one-time header) looks like a > good idea, similar to the existing kafka.OVERRIDE_TOPIC. > What do you think? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-16414) camel-kafka set custom timestamp
[ https://issues.apache.org/jira/browse/CAMEL-16414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-16414 started by Ramu. > camel-kafka set custom timestamp > > > Key: CAMEL-16414 > URL: https://issues.apache.org/jira/browse/CAMEL-16414 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Affects Versions: 2.25.3, 3.8.0 >Reporter: Jens Kordowski >Assignee: Ramu >Priority: Major > Fix For: 3.10.0 > > > The kafka producer supports the possibility to pass on a (custom) timestamp > with the record. The camel-kafka component does not leverage this, currently. > A Camel header seems like a good option to provide this. The consumer already > creates a kafka.TIMESTAMP header (not yet documented). I suggest to use a > different header to avoid misconfiguration in case of "kafka to kafka" > scenarios. kafka.OVERRIDE_TIMESTAMP (being a one-time header) looks like a > good idea, similar to the existing kafka.OVERRIDE_TOPIC. > What do you think? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu resolved CAMEL-15323. -- Resolution: Fixed > Add example camel-spring-boot - http endpoint for route information > --- > > Key: CAMEL-15323 > URL: https://issues.apache.org/jira/browse/CAMEL-15323 > Project: Camel > Issue Type: Task > Components: camel-spring-boot, examples >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > Add example for spring boot actuator that could output route details, eg a > list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14736) Upgrade to Hadoop 3.x
[ https://issues.apache.org/jira/browse/CAMEL-14736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17209479#comment-17209479 ] Ramu commented on CAMEL-14736: -- camel-hdfc is already om 3.x . wil upgrade to latest 3.x and test. looks like no karaf feature available for this > Upgrade to Hadoop 3.x > - > > Key: CAMEL-14736 > URL: https://issues.apache.org/jira/browse/CAMEL-14736 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Labels: help-wanted > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-14736) Upgrade to Hadoop 3.x
[ https://issues.apache.org/jira/browse/CAMEL-14736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-14736 started by Ramu. > Upgrade to Hadoop 3.x > - > > Key: CAMEL-14736 > URL: https://issues.apache.org/jira/browse/CAMEL-14736 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Labels: help-wanted > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14736) Upgrade to Hadoop 3.x
[ https://issues.apache.org/jira/browse/CAMEL-14736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-14736: Assignee: Ramu > Upgrade to Hadoop 3.x > - > > Key: CAMEL-14736 > URL: https://issues.apache.org/jira/browse/CAMEL-14736 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Labels: help-wanted > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15616) camel-saxon - Upgrade to Saxon 10.x
[ https://issues.apache.org/jira/browse/CAMEL-15616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17208520#comment-17208520 ] Ramu commented on CAMEL-15616: -- [~acosentino] looking > camel-saxon - Upgrade to Saxon 10.x > --- > > Key: CAMEL-15616 > URL: https://issues.apache.org/jira/browse/CAMEL-15616 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > We are using 9.9.x but there is a 10.x release out -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-15616) camel-saxon - Upgrade to Saxon 10.x
[ https://issues.apache.org/jira/browse/CAMEL-15616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15616 started by Ramu. > camel-saxon - Upgrade to Saxon 10.x > --- > > Key: CAMEL-15616 > URL: https://issues.apache.org/jira/browse/CAMEL-15616 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > We are using 9.9.x but there is a 10.x release out -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15485) Migrate camel-spring-boot-examples to use JUnit 5 style
[ https://issues.apache.org/jira/browse/CAMEL-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu resolved CAMEL-15485. -- Resolution: Fixed > Migrate camel-spring-boot-examples to use JUnit 5 style > --- > > Key: CAMEL-15485 > URL: https://issues.apache.org/jira/browse/CAMEL-15485 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Labels: help-wanted > Fix For: 3.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-15485) Migrate camel-spring-boot-examples to use JUnit 5 style
[ https://issues.apache.org/jira/browse/CAMEL-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15485 started by Ramu. > Migrate camel-spring-boot-examples to use JUnit 5 style > --- > > Key: CAMEL-15485 > URL: https://issues.apache.org/jira/browse/CAMEL-15485 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Labels: help-wanted > Fix For: 3.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14280) camel-rabbitmq - Allow to specify header with override queue name
[ https://issues.apache.org/jira/browse/CAMEL-14280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-14280: Assignee: (was: Ramu) > camel-rabbitmq - Allow to specify header with override queue name > - > > Key: CAMEL-14280 > URL: https://issues.apache.org/jira/browse/CAMEL-14280 > Project: Camel > Issue Type: New Feature > Components: camel-rabbitmq >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > So you can route to dynamic queues via the same rabbitmq endpoint/producer. > There are already a number of headers that can use to control the message > https://camel.apache.org/components/latest/rabbitmq-component.html#_message_headers > Lets see if we can add OVERRIDE_QUEUE_NAME to specify a name that overrides > the queue name from the endpoint uri > See SO > https://stackoverflow.com/questions/59259050/how-to-pass-queue-name-to-camel-route-via-a-variable -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15485) Migrate camel-spring-boot-examples to use JUnit 5 style
[ https://issues.apache.org/jira/browse/CAMEL-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-15485: Assignee: Ramu > Migrate camel-spring-boot-examples to use JUnit 5 style > --- > > Key: CAMEL-15485 > URL: https://issues.apache.org/jira/browse/CAMEL-15485 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Labels: help-wanted > Fix For: 3.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17207803#comment-17207803 ] Ramu commented on CAMEL-15323: -- [~JoshiRaez] the example should go [camel spring boot examples|https://github.com/apache/camel-spring-boot-examples] > Add example camel-spring-boot - http endpoint for route information > --- > > Key: CAMEL-15323 > URL: https://issues.apache.org/jira/browse/CAMEL-15323 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot, examples >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.6.0 > > > Add example for spring boot actuator that could output route details, eg a > list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15596) camel-jacksonxml feature install failed due to stax2 version
[
https://issues.apache.org/jira/browse/CAMEL-15596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17207084#comment-17207084
]
Ramu commented on CAMEL-15596:
--
[~xldai]
2.24.2, 2.25.2 is very old. Please try with camel 3.5
> camel-jacksonxml feature install failed due to stax2 version
>
>
> Key: CAMEL-15596
> URL: https://issues.apache.org/jira/browse/CAMEL-15596
> Project: Camel
> Issue Type: Bug
> Components: osgi
>Affects Versions: 2.24.2, 2.25.2
>Reporter: Xilai Dai
>Assignee: Ramu
>Priority: Major
>
> Start karaf 4.2.9 OSGi container, execute:
> karaf@root()> feature:repo-add camel 2.25.2
> karaf@root()> feature:install camel-jacksonxml
> {code}
> Error executing command: Unable to resolve root: missing requirement [root]
> osgi.identity; osgi.identity=camel-jacksonxml; type=karaf.feature;
> version="[2.25.2,2.25.2]";
> filter:="(&(osgi.identity=camel-jacksonxml)(type=karaf.feature)(version>=2.25.2)(version<=2.25.2))"
> [caused by: Unable to resolve camel-jacksonxml/2.25.2: missing requirement
> [camel-jacksonxml/2.25.2] osgi.identity;
> osgi.identity=org.apache.camel.camel-jacksonxml; type=osgi.bundle;
> version="[2.25.2,2.25.2]"; resolution:=mandatory [caused by: Unable to
> resolve org.apache.camel.camel-jacksonxml/2.25.2: missing requirement
> [org.apache.camel.camel-jacksonxml/2.25.2] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.dataformat.xml)(version>=2.3.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.dataformat.jackson-dataformat-xml/2.9.10: missing
> requirement [com.fasterxml.jackson.dataformat.jackson-dataformat-xml/2.9.10]
> osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.codehaus.stax2)(version>=4.2.0)(!(version>=5.0.0)))"]]]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-15596) camel-jacksonxml feature install failed due to stax2 version
[
https://issues.apache.org/jira/browse/CAMEL-15596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramu reassigned CAMEL-15596:
Assignee: Ramu
> camel-jacksonxml feature install failed due to stax2 version
>
>
> Key: CAMEL-15596
> URL: https://issues.apache.org/jira/browse/CAMEL-15596
> Project: Camel
> Issue Type: Bug
> Components: osgi
>Affects Versions: 2.24.2, 2.25.2
>Reporter: Xilai Dai
>Assignee: Ramu
>Priority: Major
>
> Start karaf 4.2.9 OSGi container, execute:
> karaf@root()> feature:repo-add camel 2.25.2
> karaf@root()> feature:install camel-jacksonxml
> {code}
> Error executing command: Unable to resolve root: missing requirement [root]
> osgi.identity; osgi.identity=camel-jacksonxml; type=karaf.feature;
> version="[2.25.2,2.25.2]";
> filter:="(&(osgi.identity=camel-jacksonxml)(type=karaf.feature)(version>=2.25.2)(version<=2.25.2))"
> [caused by: Unable to resolve camel-jacksonxml/2.25.2: missing requirement
> [camel-jacksonxml/2.25.2] osgi.identity;
> osgi.identity=org.apache.camel.camel-jacksonxml; type=osgi.bundle;
> version="[2.25.2,2.25.2]"; resolution:=mandatory [caused by: Unable to
> resolve org.apache.camel.camel-jacksonxml/2.25.2: missing requirement
> [org.apache.camel.camel-jacksonxml/2.25.2] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.dataformat.xml)(version>=2.3.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.dataformat.jackson-dataformat-xml/2.9.10: missing
> requirement [com.fasterxml.jackson.dataformat.jackson-dataformat-xml/2.9.10]
> osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.codehaus.stax2)(version>=4.2.0)(!(version>=5.0.0)))"]]]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-15616) camel-saxon - Upgrade to Saxon 10.x
[ https://issues.apache.org/jira/browse/CAMEL-15616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-15616: Assignee: Ramu > camel-saxon - Upgrade to Saxon 10.x > --- > > Key: CAMEL-15616 > URL: https://issues.apache.org/jira/browse/CAMEL-15616 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > We are using 9.9.x but there is a 10.x release out -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17207080#comment-17207080 ] Ramu edited comment on CAMEL-15323 at 10/4/20, 2:39 AM: [~JoshiRaez] I already started working on it. I see 'camel-example-spring-boot-xml' 'camel-example-spring-boot' present The only functionality missing is start and stopping routes. [~JoshiRaez] you are welcome to work on this Thanks for your interest was (Author: ramu11): [~JoshiRaez] I already started working on it. > Add example camel-spring-boot - http endpoint for route information > --- > > Key: CAMEL-15323 > URL: https://issues.apache.org/jira/browse/CAMEL-15323 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot, examples >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.6.0 > > > Add example for spring boot actuator that could output route details, eg a > list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work stopped] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15323 stopped by Ramu. > Add example camel-spring-boot - http endpoint for route information > --- > > Key: CAMEL-15323 > URL: https://issues.apache.org/jira/browse/CAMEL-15323 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot, examples >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.6.0 > > > Add example for spring boot actuator that could output route details, eg a > list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17207080#comment-17207080 ] Ramu commented on CAMEL-15323: -- [~JoshiRaez] I already started working on it. > Add example camel-spring-boot - http endpoint for route information > --- > > Key: CAMEL-15323 > URL: https://issues.apache.org/jira/browse/CAMEL-15323 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot, examples >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.6.0 > > > Add example for spring boot actuator that could output route details, eg a > list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15323 started by Ramu. > Add example camel-spring-boot - http endpoint for route information > --- > > Key: CAMEL-15323 > URL: https://issues.apache.org/jira/browse/CAMEL-15323 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot, examples >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.6.0 > > > Add example for spring boot actuator that could output route details, eg a > list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-15323: - Issue Type: New Feature (was: Task) > Add example camel-spring-boot - http endpoint for route information > --- > > Key: CAMEL-15323 > URL: https://issues.apache.org/jira/browse/CAMEL-15323 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Ramu >Assignee: Ramu >Priority: Major > > Add example for spring boot actuator that could output route details, eg a > list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-15323: - Fix Version/s: 3.5.0 > Add example camel-spring-boot - http endpoint for route information > --- > > Key: CAMEL-15323 > URL: https://issues.apache.org/jira/browse/CAMEL-15323 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Ramu >Assignee: Ramu >Priority: Major > Fix For: 3.5.0 > > > Add example for spring boot actuator that could output route details, eg a > list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu updated CAMEL-15323: - Description: Add example for spring boot actuator that could output route details, eg a list of the routes and their state, and some metrics. It was also possible to stop/start routes etc. However the latter was a concern for security. But having a basic http endpoint service to dump route details would be good > Add example camel-spring-boot - http endpoint for route information > --- > > Key: CAMEL-15323 > URL: https://issues.apache.org/jira/browse/CAMEL-15323 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Ramu >Assignee: Ramu >Priority: Major > > Add example for spring boot actuator that could output route details, eg a > list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-15323: Assignee: Ramu > Add example camel-spring-boot - http endpoint for route information > --- > > Key: CAMEL-15323 > URL: https://issues.apache.org/jira/browse/CAMEL-15323 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Ramu >Assignee: Ramu >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15323) Add example camel-spring-boot - http endpoint for route information
Ramu created CAMEL-15323: Summary: Add example camel-spring-boot - http endpoint for route information Key: CAMEL-15323 URL: https://issues.apache.org/jira/browse/CAMEL-15323 Project: Camel Issue Type: Task Components: camel-spring-boot Reporter: Ramu -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15274) camel-spring-boot - Add back http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu resolved CAMEL-15274. -- Resolution: Fixed > camel-spring-boot - Add back http endpoint for route information > > > Key: CAMEL-15274 > URL: https://issues.apache.org/jira/browse/CAMEL-15274 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.5.0 > > > In Camel 2.x we had spring boot actuator that could output route details, eg > a list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good. > It should be disabled by default and only be a read-only service if enabled. > The old code in 2.x can be of inspiration. > And the old code is not compatible with newer spring boot so it needs to be > migrated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work stopped] (CAMEL-15274) camel-spring-boot - Add back http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15274 stopped by Ramu. > camel-spring-boot - Add back http endpoint for route information > > > Key: CAMEL-15274 > URL: https://issues.apache.org/jira/browse/CAMEL-15274 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > In Camel 2.x we had spring boot actuator that could output route details, eg > a list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good. > It should be disabled by default and only be a read-only service if enabled. > The old code in 2.x can be of inspiration. > And the old code is not compatible with newer spring boot so it needs to be > migrated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-15274) camel-spring-boot - Add back http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15274 started by Ramu. > camel-spring-boot - Add back http endpoint for route information > > > Key: CAMEL-15274 > URL: https://issues.apache.org/jira/browse/CAMEL-15274 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > In Camel 2.x we had spring boot actuator that could output route details, eg > a list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good. > It should be disabled by default and only be a read-only service if enabled. > The old code in 2.x can be of inspiration. > And the old code is not compatible with newer spring boot so it needs to be > migrated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15274) camel-spring-boot - Add back http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159898#comment-17159898 ] Ramu commented on CAMEL-15274: -- looking into it > camel-spring-boot - Add back http endpoint for route information > > > Key: CAMEL-15274 > URL: https://issues.apache.org/jira/browse/CAMEL-15274 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > In Camel 2.x we had spring boot actuator that could output route details, eg > a list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good. > It should be disabled by default and only be a read-only service if enabled. > The old code in 2.x can be of inspiration. > And the old code is not compatible with newer spring boot so it needs to be > migrated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15274) camel-spring-boot - Add back http endpoint for route information
[ https://issues.apache.org/jira/browse/CAMEL-15274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-15274: Assignee: Ramu > camel-spring-boot - Add back http endpoint for route information > > > Key: CAMEL-15274 > URL: https://issues.apache.org/jira/browse/CAMEL-15274 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > > In Camel 2.x we had spring boot actuator that could output route details, eg > a list of the routes and their state, and some metrics. > It was also possible to stop/start routes etc. > However the latter was a concern for security. > But having a basic http endpoint service to dump route details would be good. > It should be disabled by default and only be a read-only service if enabled. > The old code in 2.x can be of inspiration. > And the old code is not compatible with newer spring boot so it needs to be > migrated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15228) camel-kafka - Missing end of polling signal in Processors
[
https://issues.apache.org/jira/browse/CAMEL-15228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147581#comment-17147581
]
Ramu commented on CAMEL-15228:
--
[~apjoe] are you working on fix
> camel-kafka - Missing end of polling signal in Processors
> -
>
> Key: CAMEL-15228
> URL: https://issues.apache.org/jira/browse/CAMEL-15228
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Affects Versions: 3.4.0
>Reporter: Jörg
>Assignee: Ramu
>Priority: Major
>
> For batch requirements it is currently not possible to get a signal for the
> last result within a poll request in processors (over all partitions and
> topics).
> The problem with this is, that a Processor cannot know when the last record
> of a poll received and it is time for commits to all of the affected
> partitions, because you cannot be sure that there is always a content in
> every partition and therefore you have no info in Processer, if any further
> message arrives.
> Solution could be to add a property to the manual commit handler in the
> [KafkaConsumer.KafkaFetchRecords.doRun|https://github.com/apache/camel/blob/c86c860b7c5b5ef754970291b7ad7c4b32b443c6/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java#L248]
>
> {code:java}
> exchange.getIn().setHeader(KafkaConstants.MANUAL_COMMIT, manual);
> //adding new exchange property
> exchange.getIn().setHeader(KafkaConstants.LAST_RECORD_OF_CURRENT_POLL_REQUEST,
> last_record_of_last_partition);
> {code}
> LAST_RECORD_IN_CURRENT_POLL_REQUEST should be a boolean to signal end of the
> [loop over all
> partitions|https://github.com/apache/camel/blob/c86c860b7c5b5ef754970291b7ad7c4b32b443c6/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java#L313]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-15228) camel-kafka - Missing end of polling signal in Processors
[
https://issues.apache.org/jira/browse/CAMEL-15228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramu reassigned CAMEL-15228:
Assignee: Ramu
> camel-kafka - Missing end of polling signal in Processors
> -
>
> Key: CAMEL-15228
> URL: https://issues.apache.org/jira/browse/CAMEL-15228
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Affects Versions: 3.4.0
>Reporter: Jörg
>Assignee: Ramu
>Priority: Major
>
> For batch requirements it is currently not possible to get a signal for the
> last result within a poll request in processors (over all partitions and
> topics).
> The problem with this is, that a Processor cannot know when the last record
> of a poll received and it is time for commits to all of the affected
> partitions, because you cannot be sure that there is always a content in
> every partition and therefore you have no info in Processer, if any further
> message arrives.
> Solution could be to add a property to the manual commit handler in the
> [KafkaConsumer.KafkaFetchRecords.doRun|https://github.com/apache/camel/blob/c86c860b7c5b5ef754970291b7ad7c4b32b443c6/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java#L248]
>
> {code:java}
> exchange.getIn().setHeader(KafkaConstants.MANUAL_COMMIT, manual);
> //adding new exchange property
> exchange.getIn().setHeader(KafkaConstants.LAST_RECORD_OF_CURRENT_POLL_REQUEST,
> last_record_of_last_partition);
> {code}
> LAST_RECORD_IN_CURRENT_POLL_REQUEST should be a boolean to signal end of the
> [loop over all
> partitions|https://github.com/apache/camel/blob/c86c860b7c5b5ef754970291b7ad7c4b32b443c6/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java#L313]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14980) camel-kafka - SerializationException - consumer keeps leaving and rejoining the group
[
https://issues.apache.org/jira/browse/CAMEL-14980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147518#comment-17147518
]
Ramu commented on CAMEL-14980:
--
we can get rid of these type of issues by implementing deadletterqueue for
kafka .
we can implement a failure-strategy similar to kafka-connect
failure-strategy : Specify the failure strategy to apply when a message
produced from a record is nacked. Values can be fail (default), ignore, or
dead-letter-queue
Type: string
supports 3 strategies:
fail - fail the application, no more records will be processed. (default) The
offset of the record that has not been processed correctly is not committed.
ignore - the failure is logged, but the processing continue. The offset of the
record that has not been processed correctly is committed.
dead-letter-queue - the offset of the record that has not been processed
correctly is committed, but the record is written to a (Kafka) dead letter
topic.
The strategy is selected using the failure-strategy attribute.
In the case of dead-letter-queue, you can configure the following attributes:
dead-letter-queue.topic: the topic to use to write the records not processed
correctly, default is dead-letter-topic-$channel, with $channel being the name
of the channel.
dead-letter-queue.key.serializer: the serializer used to write the record key
on the dead letter queue. By default, it deduces the serializer from the key
deserializer.
dead-letter-queue.value.serializer: the serializer used to write the record
value on the dead letter queue. By default, it deduces the serializer from the
value deserializer.
The record written on the dead letter queue contains the dead-letter-reason
header with the nack reason (message from the exception passed to the nack
method). It may also contain the dead-letter-cause with the message from the
cause, if any.
your comments welcome
> camel-kafka - SerializationException - consumer keeps leaving and rejoining
> the group
> -
>
> Key: CAMEL-14980
> URL: https://issues.apache.org/jira/browse/CAMEL-14980
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 3.2.0
>Reporter: joseph m'bimbi-bene
>Assignee: Ramu
>Priority: Major
> Fix For: 3.5.0
>
> Attachments: camel-kafka-errors.txt, poc_camel_kafka.tar.gz
>
>
> Hello everyone,
>
> I found out i few days ago that if a `SerializationException` is thrown when
> the consumer tries to poll messages, it will keep leaving and joining the
> consumer-group indefinitely and without any informative log.
> The exception cannot either be handled by any camel exception handler.
> After some searching in the code i found out the culprit:
> {code:java}
> // org.apache.camel.component.kafka.KafkaConsumer (ligns 406-415):
> catch (KafkaException e) {
> // some kind of error in kafka, it may happen during
> // unsubscribing or during normal processing
> if (unsubscribing){
> getExceptionHandler().handleException("Error unsubscribing " + threadId +
> " from kafka topic " + topicName, e);
> }else {
> LOG.debug("KafkaException consuming {} from topic {} causedby {}. Will
> attempt to re-connect on next run", threadId, topicName, e.getMessage());
> reConnect = true;
> }
> }
> {code}
>
> `SerializationException` extends from `KafkaException`, but it is definitely
> not a recoverable exception.
> It logs with debug level, which makes it hard to track, there are SO many
> things logging in debug.
> It it cannot be handled by any camel exception handling mechanism.
> I think it would be better to either:
> - change that catch so that it pinpoints the subclasses of `KafkaException`
> that are actually recoverable from rejoining (maybe `WakeupException` and a
> couple others)
> - add a `catch` block for `SerializationException` and maybe
> `ConfigException` and `OAuthBearerConfigException` before, with a log error
> andallow the user to handle those exceptions
> - remove that catch block entirely and let users handle any KafkaException
> however they see fit.
> Thank you
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14980) camel-kafka - SerializationException - consumer keeps leaving and rejoining the group
[
https://issues.apache.org/jira/browse/CAMEL-14980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17099555#comment-17099555
]
Ramu commented on CAMEL-14980:
--
Thanks for the logs and example. i will look in to it
> camel-kafka - SerializationException - consumer keeps leaving and rejoining
> the group
> -
>
> Key: CAMEL-14980
> URL: https://issues.apache.org/jira/browse/CAMEL-14980
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 3.2.0
>Reporter: joseph m'bimbi-bene
>Assignee: Ramu
>Priority: Major
> Fix For: 3.3.0
>
> Attachments: camel-kafka-errors.txt, poc_camel_kafka.tar.gz
>
>
> Hello everyone,
>
> I found out i few days ago that if a `SerializationException` is thrown when
> the consumer tries to poll messages, it will keep leaving and joining the
> consumer-group indefinitely and without any informative log.
> The exception cannot either be handled by any camel exception handler.
> After some searching in the code i found out the culprit:
> {code:java}
> // org.apache.camel.component.kafka.KafkaConsumer (ligns 406-415):
> catch (KafkaException e) {
> // some kind of error in kafka, it may happen during
> // unsubscribing or during normal processing
> if (unsubscribing){
> getExceptionHandler().handleException("Error unsubscribing " + threadId +
> " from kafka topic " + topicName, e);
> }else {
> LOG.debug("KafkaException consuming {} from topic {} causedby {}. Will
> attempt to re-connect on next run", threadId, topicName, e.getMessage());
> reConnect = true;
> }
> }
> {code}
>
> `SerializationException` extends from `KafkaException`, but it is definitely
> not a recoverable exception.
> It logs with debug level, which makes it hard to track, there are SO many
> things logging in debug.
> It it cannot be handled by any camel exception handling mechanism.
> I think it would be better to either:
> - change that catch so that it pinpoints the subclasses of `KafkaException`
> that are actually recoverable from rejoining (maybe `WakeupException` and a
> couple others)
> - add a `catch` block for `SerializationException` and maybe
> `ConfigException` and `OAuthBearerConfigException` before, with a log error
> andallow the user to handle those exceptions
> - remove that catch block entirely and let users handle any KafkaException
> however they see fit.
> Thank you
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14948) Slack consumer uses deprecated channels.list API
[ https://issues.apache.org/jira/browse/CAMEL-14948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu resolved CAMEL-14948. -- Resolution: Fixed > Slack consumer uses deprecated channels.list API > > > Key: CAMEL-14948 > URL: https://issues.apache.org/jira/browse/CAMEL-14948 > Project: Camel > Issue Type: Improvement > Components: camel-slack >Affects Versions: 3.2.0, 2.25.1 >Reporter: Zoran Regvart >Assignee: Ramu >Priority: Major > > [channels.list|https://api.slack.com/methods/channels.list] API has been > deprecated and for new applications will no longer function. We need to > migrate from it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14980) camel-kafka - SerializationException - consumer keeps leaving and rejoining the group
[
https://issues.apache.org/jira/browse/CAMEL-14980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096086#comment-17096086
]
Ramu edited comment on CAMEL-14980 at 4/30/20, 3:45 AM:
[~cless91] Thanks for reporting. It would be good to have multiple catch
blocks to understand better about the error. I would look into it
was (Author: ramu11):
[~cless91] Thanks for reporting. is it possible to attach the stack trace you
are currently getting. It would be good to have multiple catch blocks to
understand better about the error. I would look into it
> camel-kafka - SerializationException - consumer keeps leaving and rejoining
> the group
> -
>
> Key: CAMEL-14980
> URL: https://issues.apache.org/jira/browse/CAMEL-14980
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 3.2.0
>Reporter: joseph m'bimbi-bene
>Assignee: Ramu
>Priority: Major
> Fix For: 3.3.0
>
>
> Hello everyone,
>
> I found out i few days ago that if a `SerializationException` is thrown when
> the consumer tries to poll messages, it will keep leaving and joining the
> consumer-group indefinitely and without any informative log.
> The exception cannot either be handled by any camel exception handler.
> After some searching in the code i found out the culprit:
> ``` java
> // org.apache.camel.component.kafka.KafkaConsumer (ligns 406-415):
> catch (KafkaException e) {
> // some kind of error in kafka, it may happen during
> // unsubscribing or during normal processing
> if (unsubscribing) {
> getExceptionHandler().handleException("Error unsubscribing " + threadId +
> " from kafka topic " + topicName, e); }
> else {
> LOG.debug("KafkaException consuming {} from topic {} causedby {}. Will
> attempt to re-connect on next run", threadId, topicName, e.getMessage());
> reConnect = true;
> }
> }
> ```
> `SerializationException` extends from `KafkaException`, but it is definitely
> not a recoverable exception.
> It logs with debug level, which makes it hard to track, there are SO many
> things logging in debug.
> It it cannot be handled by any camel exception handling mechanism.
> I think it would be better to either:
> - change that catch so that it pinpoints the subclasses of `KafkaException`
> that are actually recoverable from rejoining (maybe `WakeupException` and a
> couple others)
> - add a `catch` block for `SerializationException` and maybe
> `ConfigException` and `OAuthBearerConfigException` before, with a log error
> andallow the user to handle those exceptions
> - remove that catch block entirely and let users handle any KafkaException
> however they see fit.
> Thank you
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
