[jira] [Commented] (CAMEL-18871) camel-netty - Application does not recover (threads are WAITING) when NettyProducer pool is exhausted
[
https://issues.apache.org/jira/browse/CAMEL-18871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675829#comment-17675829
]
Claus Ibsen commented on CAMEL-18871:
-
Are you able to work on a special PR for 3.14.x as the other cannot cleanly be
backported
> camel-netty - Application does not recover (threads are WAITING) when
> NettyProducer pool is exhausted
> -
>
> Key: CAMEL-18871
> URL: https://issues.apache.org/jira/browse/CAMEL-18871
> Project: Camel
> Issue Type: Bug
> Components: camel-netty
>Affects Versions: 3.14.7
>Reporter: Vincenzo Galluccio
>Priority: Major
> Fix For: 3.18.5, 3.20.2, 3.21.0
>
>
> When the Camel Application sends a LOT of requests to a TCP/IP Server (which
> is not available/down) using Netty component, after a bit, it hangs because
> the Producer Pool is exhausted (when *producerPoolMaxTotal* is not -1).
>
> {code:java}
> from("direct:start")
> .to("netty://tcp://localhost:18667?connectTimeout=500=#myDecoders=#myEncoders=10=-1=250=true");
> {code}
>
>
> In previous version 3.14.1 the behavior was to fail when Pool was exhausted
> ({*}GenericObjectPool.{*}{*}WHEN_EXHAUSTED_FAIL{*}), however since version
> 3.14.2 and the migration to `{*}org.apache.commons:commons-pool2{*}`
> (https://issues.apache.org/jira/browse/CAMEL-17461) the default has become to
> block.
>
> The proposal is to adjust
> `[https://github.com/apache/camel/blob/camel-3.14.7/components/camel-netty/src/main/java/org/apache/camel/component/netty/NettyProducer.java]
> ` , method `doStart()` to add optionally set the *BlockWhenExhausted* flag
> (BaseGenericObjectPool.setBlockWhenExhausted) and the
> *{{borrowMaxWaitMillis}}* parameters.
>
> {code:java}
> "Camel Thread #74 - NettyClientTCPWorker" #1166 prio=5 os_prio=0
> tid=0x7fd661a1d800 nid=0x18599 waiting on condition [0x7fd5ffb12000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0005ce0e8338> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at
> org.apache.commons.pool2.impl.LinkedBlockingDeque.takeFirst(LinkedBlockingDeque.java:1323)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:306)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:223)
> at
> org.apache.camel.component.netty.NettyProducer.processWithBody(NettyProducer.java:259)
> at
> org.apache.camel.component.netty.NettyProducer.process(NettyProducer.java:228)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:172)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:398){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18871) camel-netty - Application does not recover (threads are WAITING) when NettyProducer pool is exhausted
[
https://issues.apache.org/jira/browse/CAMEL-18871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18871:
Fix Version/s: (was: 3.14.8)
> camel-netty - Application does not recover (threads are WAITING) when
> NettyProducer pool is exhausted
> -
>
> Key: CAMEL-18871
> URL: https://issues.apache.org/jira/browse/CAMEL-18871
> Project: Camel
> Issue Type: Bug
> Components: camel-netty
>Affects Versions: 3.14.7
>Reporter: Vincenzo Galluccio
>Priority: Major
> Fix For: 3.18.5, 3.20.2, 3.21.0
>
>
> When the Camel Application sends a LOT of requests to a TCP/IP Server (which
> is not available/down) using Netty component, after a bit, it hangs because
> the Producer Pool is exhausted (when *producerPoolMaxTotal* is not -1).
>
> {code:java}
> from("direct:start")
> .to("netty://tcp://localhost:18667?connectTimeout=500=#myDecoders=#myEncoders=10=-1=250=true");
> {code}
>
>
> In previous version 3.14.1 the behavior was to fail when Pool was exhausted
> ({*}GenericObjectPool.{*}{*}WHEN_EXHAUSTED_FAIL{*}), however since version
> 3.14.2 and the migration to `{*}org.apache.commons:commons-pool2{*}`
> (https://issues.apache.org/jira/browse/CAMEL-17461) the default has become to
> block.
>
> The proposal is to adjust
> `[https://github.com/apache/camel/blob/camel-3.14.7/components/camel-netty/src/main/java/org/apache/camel/component/netty/NettyProducer.java]
> ` , method `doStart()` to add optionally set the *BlockWhenExhausted* flag
> (BaseGenericObjectPool.setBlockWhenExhausted) and the
> *{{borrowMaxWaitMillis}}* parameters.
>
> {code:java}
> "Camel Thread #74 - NettyClientTCPWorker" #1166 prio=5 os_prio=0
> tid=0x7fd661a1d800 nid=0x18599 waiting on condition [0x7fd5ffb12000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0005ce0e8338> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at
> org.apache.commons.pool2.impl.LinkedBlockingDeque.takeFirst(LinkedBlockingDeque.java:1323)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:306)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:223)
> at
> org.apache.camel.component.netty.NettyProducer.processWithBody(NettyProducer.java:259)
> at
> org.apache.camel.component.netty.NettyProducer.process(NettyProducer.java:228)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:172)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:398){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18886) The org.apache.camel:camel-test-spring-junit5:jar:4.0.0-SNAPSHOT is not available in the maven repository
[ https://issues.apache.org/jira/browse/CAMEL-18886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675820#comment-17675820 ] Claus Ibsen commented on CAMEL-18886: - Camel 4 is just started in development, use camel-3.x branch > The org.apache.camel:camel-test-spring-junit5:jar:4.0.0-SNAPSHOT is not > available in the maven repository > - > > Key: CAMEL-18886 > URL: https://issues.apache.org/jira/browse/CAMEL-18886 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-test >Reporter: Rhuan Rocha >Priority: Major > > Hello, > I'm trying to build the camel project using maven and the > org.apache.camel:camel-test-spring-junit5:jar:4.0.0-SNAPSHOT is not available > to > [https://repository.apache.org/snapshots/.|https://repository.apache.org/snapshots/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18886) The org.apache.camel:camel-test-spring-junit5:jar:4.0.0-SNAPSHOT is not available in the maven repository
[ https://issues.apache.org/jira/browse/CAMEL-18886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18886. - Resolution: Invalid > The org.apache.camel:camel-test-spring-junit5:jar:4.0.0-SNAPSHOT is not > available in the maven repository > - > > Key: CAMEL-18886 > URL: https://issues.apache.org/jira/browse/CAMEL-18886 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-test >Reporter: Rhuan Rocha >Priority: Major > > Hello, > I'm trying to build the camel project using maven and the > org.apache.camel:camel-test-spring-junit5:jar:4.0.0-SNAPSHOT is not available > to > [https://repository.apache.org/snapshots/.|https://repository.apache.org/snapshots/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18131) camel-health - Add health checks for components that has extension for connectivity verification
[ https://issues.apache.org/jira/browse/CAMEL-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rhuan Rocha updated CAMEL-18131: Description: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS|x| |AWS2-CW|x| |AWS2-DDB|x| |AWS2-DDBStreams|x| |AWS2-EC2|x| |AWS2-EVENTBRIDGE| | |AWS2-IAM|x| |AWS2-KINESIS|x| |camel-aws-cloudtrail| | |camel-aws-secrets-manager| | |camel-aws-xray| | |camel-aws2-ecs|x| |camel-aws2-lambda| | |camel-aws2-mq| | |camel-aws2-msk|x| |camel-aws2-ses|x| |camel-aws2-sns|x| |camel-aws2-sqs|x| |camel-aws2-translate| | was: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS|x| |AWS2-CW|x| |AWS2-DDB|x| |AWS2-DDBStreams|x| |AWS2-EC2|x| |AWS2-EVENTBRIDGE| | |AWS2-IAM|x| |AWS2-KINESIS|x| |camel-aws-cloudtrail| | |camel-aws-secrets-manager| | |camel-aws-xray| | |camel-aws2-ecs|x| |camel-aws2-lambda| | |camel-aws2-mq| | |camel-aws2-msk| | |camel-aws2-ses|x| |camel-aws2-sns|x| |camel-aws2-sqs|x| |camel-aws2-translate| | > camel-health - Add health checks for components that has extension for > connectivity verification > > > Key: CAMEL-18131 > URL: https://issues.apache.org/jira/browse/CAMEL-18131 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Rhuan Rocha >Priority: Major > Fix For: 3.21.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. > > *Components to update (partial table):* > |Component|Done| > |AWS2-S3|x| > |AWS2-ATHENA|x| > |AWS2-EKS|x| > |AWS2-CW|x| > |AWS2-DDB|x| > |AWS2-DDBStreams|x| > |AWS2-EC2|x| > |AWS2-EVENTBRIDGE| | > |AWS2-IAM|x| > |AWS2-KINESIS|x| > |camel-aws-cloudtrail| | > |camel-aws-secrets-manager| | > |camel-aws-xray| | > |camel-aws2-ecs|x| > |camel-aws2-lambda| | > |camel-aws2-mq| | > |camel-aws2-msk|x| > |camel-aws2-ses|x| > |camel-aws2-sns|x| > |camel-aws2-sqs|x| > |camel-aws2-translate| | > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18886) The org.apache.camel:camel-test-spring-junit5:jar:4.0.0-SNAPSHOT is not available in the maven repository
Rhuan Rocha created CAMEL-18886: --- Summary: The org.apache.camel:camel-test-spring-junit5:jar:4.0.0-SNAPSHOT is not available in the maven repository Key: CAMEL-18886 URL: https://issues.apache.org/jira/browse/CAMEL-18886 Project: Camel Issue Type: Dependency upgrade Components: camel-test Reporter: Rhuan Rocha Hello, I'm trying to build the camel project using maven and the org.apache.camel:camel-test-spring-junit5:jar:4.0.0-SNAPSHOT is not available to [https://repository.apache.org/snapshots/.|https://repository.apache.org/snapshots/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18871) camel-netty - Application does not recover (threads are WAITING) when NettyProducer pool is exhausted
[
https://issues.apache.org/jira/browse/CAMEL-18871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675676#comment-17675676
]
Vincenzo Galluccio commented on CAMEL-18871:
Hello [~davsclaus] . I have created the following PR:
[https://github.com/apache/camel/pull/9047]
PS: The PR to add the two new options/params to
[https://github.com/apache/camel-spring-boot/tree/main/components-starter/camel-netty-starter]
will follow..
> camel-netty - Application does not recover (threads are WAITING) when
> NettyProducer pool is exhausted
> -
>
> Key: CAMEL-18871
> URL: https://issues.apache.org/jira/browse/CAMEL-18871
> Project: Camel
> Issue Type: Bug
> Components: camel-netty
>Affects Versions: 3.14.7
>Reporter: Vincenzo Galluccio
>Priority: Major
> Fix For: 3.14.8, 3.18.5, 3.20.2, 3.21.0
>
>
> When the Camel Application sends a LOT of requests to a TCP/IP Server (which
> is not available/down) using Netty component, after a bit, it hangs because
> the Producer Pool is exhausted (when *producerPoolMaxTotal* is not -1).
>
> {code:java}
> from("direct:start")
> .to("netty://tcp://localhost:18667?connectTimeout=500=#myDecoders=#myEncoders=10=-1=250=true");
> {code}
>
>
> In previous version 3.14.1 the behavior was to fail when Pool was exhausted
> ({*}GenericObjectPool.{*}{*}WHEN_EXHAUSTED_FAIL{*}), however since version
> 3.14.2 and the migration to `{*}org.apache.commons:commons-pool2{*}`
> (https://issues.apache.org/jira/browse/CAMEL-17461) the default has become to
> block.
>
> The proposal is to adjust
> `[https://github.com/apache/camel/blob/camel-3.14.7/components/camel-netty/src/main/java/org/apache/camel/component/netty/NettyProducer.java]
> ` , method `doStart()` to add optionally set the *BlockWhenExhausted* flag
> (BaseGenericObjectPool.setBlockWhenExhausted) and the
> *{{borrowMaxWaitMillis}}* parameters.
>
> {code:java}
> "Camel Thread #74 - NettyClientTCPWorker" #1166 prio=5 os_prio=0
> tid=0x7fd661a1d800 nid=0x18599 waiting on condition [0x7fd5ffb12000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0005ce0e8338> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at
> org.apache.commons.pool2.impl.LinkedBlockingDeque.takeFirst(LinkedBlockingDeque.java:1323)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:306)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:223)
> at
> org.apache.camel.component.netty.NettyProducer.processWithBody(NettyProducer.java:259)
> at
> org.apache.camel.component.netty.NettyProducer.process(NettyProducer.java:228)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:172)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:398){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18884) camel-package-maven-plugin - Endpoint and Component DSL should skip v4 that are not migrated yet
[ https://issues.apache.org/jira/browse/CAMEL-18884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675671#comment-17675671 ] Claus Ibsen commented on CAMEL-18884: - I added TODO: camel4 in PrepareCatalogMojo which we can adjust when we have these working > camel-package-maven-plugin - Endpoint and Component DSL should skip v4 that > are not migrated yet > > > Key: CAMEL-18884 > URL: https://issues.apache.org/jira/browse/CAMEL-18884 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > activemq > stomp > websocket > are disabled as they are not migrated yet, but the endpoint/component DSL > will regen source. We need to make it skip that for these -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18884) camel-package-maven-plugin - Endpoint and Component DSL should skip v4 that are not migrated yet
[ https://issues.apache.org/jira/browse/CAMEL-18884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18884: Description: activemq johnzon stomp websocket are disabled as they are not migrated yet, but the endpoint/component DSL will regen source. We need to make it skip that for these was: activemq stomp websocket are disabled as they are not migrated yet, but the endpoint/component DSL will regen source. We need to make it skip that for these > camel-package-maven-plugin - Endpoint and Component DSL should skip v4 that > are not migrated yet > > > Key: CAMEL-18884 > URL: https://issues.apache.org/jira/browse/CAMEL-18884 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > activemq > johnzon > stomp > websocket > are disabled as they are not migrated yet, but the endpoint/component DSL > will regen source. We need to make it skip that for these -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18884) camel-package-maven-plugin - Endpoint and Component DSL should skip v4 that are not migrated yet
[ https://issues.apache.org/jira/browse/CAMEL-18884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18884. - Resolution: Fixed > camel-package-maven-plugin - Endpoint and Component DSL should skip v4 that > are not migrated yet > > > Key: CAMEL-18884 > URL: https://issues.apache.org/jira/browse/CAMEL-18884 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > activemq > johnzon > stomp > websocket > are disabled as they are not migrated yet, but the endpoint/component DSL > will regen source. We need to make it skip that for these -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18884) camel-package-maven-plugin - Endpoint and Component DSL should skip v4 that are not migrated yet
[ https://issues.apache.org/jira/browse/CAMEL-18884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-18884: --- Assignee: Claus Ibsen > camel-package-maven-plugin - Endpoint and Component DSL should skip v4 that > are not migrated yet > > > Key: CAMEL-18884 > URL: https://issues.apache.org/jira/browse/CAMEL-18884 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > activemq > stomp > websocket > are disabled as they are not migrated yet, but the endpoint/component DSL > will regen source. We need to make it skip that for these -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18885) camel-johnzon - Make this component work in v4 if possible
[ https://issues.apache.org/jira/browse/CAMEL-18885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675664#comment-17675664 ] Claus Ibsen commented on CAMEL-18885: - It seems that apache johnzon needs to do a jakarta release before this is possible > camel-johnzon - Make this component work in v4 if possible > -- > > Key: CAMEL-18885 > URL: https://issues.apache.org/jira/browse/CAMEL-18885 > Project: Camel > Issue Type: Task > Components: camel-johnzon >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18882) camel-cdi - Remove in v4
[ https://issues.apache.org/jira/browse/CAMEL-18882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18882. - Resolution: Fixed > camel-cdi - Remove in v4 > > > Key: CAMEL-18882 > URL: https://issues.apache.org/jira/browse/CAMEL-18882 > Project: Camel > Issue Type: Task > Components: camel-cdi >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18885) camel-johnzon - Make this component work in v4 if possible
Claus Ibsen created CAMEL-18885: --- Summary: camel-johnzon - Make this component work in v4 if possible Key: CAMEL-18885 URL: https://issues.apache.org/jira/browse/CAMEL-18885 Project: Camel Issue Type: Task Components: camel-johnzon Reporter: Claus Ibsen Fix For: 4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18884) camel-package-maven-plugin - Endpoint and Component DSL should skip v4 that are not migrated yet
Claus Ibsen created CAMEL-18884: --- Summary: camel-package-maven-plugin - Endpoint and Component DSL should skip v4 that are not migrated yet Key: CAMEL-18884 URL: https://issues.apache.org/jira/browse/CAMEL-18884 Project: Camel Issue Type: Task Components: build system Reporter: Claus Ibsen Fix For: 4.0 activemq stomp websocket are disabled as they are not migrated yet, but the endpoint/component DSL will regen source. We need to make it skip that for these -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18883) Remove deprecated components in v4
Claus Ibsen created CAMEL-18883: --- Summary: Remove deprecated components in v4 Key: CAMEL-18883 URL: https://issues.apache.org/jira/browse/CAMEL-18883 Project: Camel Issue Type: Task Reporter: Claus Ibsen Fix For: 4.0 There is camel-rabbitmq camel-vertx-kafka and potentially others as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18881) Remove camel-swagger-java in v4
[ https://issues.apache.org/jira/browse/CAMEL-18881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18881: Summary: Remove camel-swagger-java in v4 (was: Remove camel-swagger-java) > Remove camel-swagger-java in v4 > --- > > Key: CAMEL-18881 > URL: https://issues.apache.org/jira/browse/CAMEL-18881 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > It is deprecated in v3 and should be removed, we have camel-openapi-java > instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18437) Camel-bigquery: There is a difference in types between @name and ${name}
[
https://issues.apache.org/jira/browse/CAMEL-18437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675617#comment-17675617
]
Claus Ibsen commented on CAMEL-18437:
-
Yes thanks Jiri for the analysis
> Camel-bigquery: There is a difference in types between @name and ${name}
>
>
> Key: CAMEL-18437
> URL: https://issues.apache.org/jira/browse/CAMEL-18437
> Project: Camel
> Issue Type: Bug
> Components: camel-google-bigquery
>Affects Versions: 3.19.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
> Fix For: 3.21.0
>
>
> I noticed a undefined behavior when expanding coverage of google-bigquery in
> camel-quarkus ([ticket|https://github.com/apache/camel-quarkus/issues/3949]).
>
> Here is a relevant chapter from the [documentation|#_uri_format].]
>
> {quote} * parameters in form ${name} are extracted from message headers and
> formed the translated query
> * parameters in form @name are extracted from body or message headers and
> sent to Google Bigquery{quote}
> From my PoV is that in case of parameters in the header, it should not
> matter, whether _@name_ or _${name}_ is used.
> The behavior seems to be more complicated:
> * In case of _@name_ pattern, value types are dynamically resolved (see
> https://issues.apache.org/jira/browse/CAMEL-18382 for more details)
> * In case of {_}${name}{_}, value is inserted into the sql without any
> modification. Which behaves like "undefined".
> # If header value is an integer (like 4), sql is translated into {_}...
> VALUES (4) ...{_}, so it is interpreted as integer.
> # If header value is string with number inside (like "4"), sql is translated
> into {_}... VALUES (4) ...{_}, so it is interpreted as integer.
> # If the header is string (like "s4"), sql is translated into {_}... VALUES
> (s4) ...{_}, and the execution fails.
> It would make sense that the behavior of _@name_ and _${name}_ is the same
> and mainly the case 3 does not cause any failure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-18882) camel-cdi - Remove in v4
[ https://issues.apache.org/jira/browse/CAMEL-18882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-18882: --- Assignee: Claus Ibsen > camel-cdi - Remove in v4 > > > Key: CAMEL-18882 > URL: https://issues.apache.org/jira/browse/CAMEL-18882 > Project: Camel > Issue Type: Task > Components: camel-cdi >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18882) camel-cdi - Remove in v4
Claus Ibsen created CAMEL-18882: --- Summary: camel-cdi - Remove in v4 Key: CAMEL-18882 URL: https://issues.apache.org/jira/browse/CAMEL-18882 Project: Camel Issue Type: Task Components: camel-cdi Reporter: Claus Ibsen Fix For: 4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18437) Camel-bigquery: There is a difference in types between @name and ${name}
[
https://issues.apache.org/jira/browse/CAMEL-18437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675608#comment-17675608
]
Jiri Ondrusek commented on CAMEL-18437:
---
I started working on this issue, but I came to conclusion, that it cannot be
changed in such way. Example follows.
*Fix works in some cases like following one:*
User would like to use a sql query {code} insert into A(id, data) values(${id},
${data}) {code}.
Following header are send in the exchange:
{code}
exchange.getMessage().setHeader("id", 1);
exchange.getMessage().setHeader("data", "test");
{code}
The result without the fix is *insert into A(id, data) values(1, test)*
With the fix the result is OK *insert into A(id, data) values(1, 'test')*
*But fix breaks different cases*:
In case that sql is
{code}insert into A(id, data) values($values) {code}
with values {code}exchange.getMessage().setHeader("values", "1,2");{code}
The result would be (with fix) *insert into A(id, data) values('1,2')*, which
is wrong.
I'd say to keep the behavior as it is. What do you think [~davsclaus]
> Camel-bigquery: There is a difference in types between @name and ${name}
>
>
> Key: CAMEL-18437
> URL: https://issues.apache.org/jira/browse/CAMEL-18437
> Project: Camel
> Issue Type: Bug
> Components: camel-google-bigquery
>Affects Versions: 3.19.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
> Fix For: 3.21.0
>
>
> I noticed a undefined behavior when expanding coverage of google-bigquery in
> camel-quarkus ([ticket|https://github.com/apache/camel-quarkus/issues/3949]).
>
> Here is a relevant chapter from the [documentation|#_uri_format].]
>
> {quote} * parameters in form ${name} are extracted from message headers and
> formed the translated query
> * parameters in form @name are extracted from body or message headers and
> sent to Google Bigquery{quote}
> From my PoV is that in case of parameters in the header, it should not
> matter, whether _@name_ or _${name}_ is used.
> The behavior seems to be more complicated:
> * In case of _@name_ pattern, value types are dynamically resolved (see
> https://issues.apache.org/jira/browse/CAMEL-18382 for more details)
> * In case of {_}${name}{_}, value is inserted into the sql without any
> modification. Which behaves like "undefined".
> # If header value is an integer (like 4), sql is translated into {_}...
> VALUES (4) ...{_}, so it is interpreted as integer.
> # If header value is string with number inside (like "4"), sql is translated
> into {_}... VALUES (4) ...{_}, so it is interpreted as integer.
> # If the header is string (like "s4"), sql is translated into {_}... VALUES
> (s4) ...{_}, and the execution fails.
> It would make sense that the behavior of _@name_ and _${name}_ is the same
> and mainly the case 3 does not cause any failure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675606#comment-17675606 ] Claus Ibsen commented on CAMEL-18880: - Its not critical but would be good to keep up with latest maven. > camel-jbang - upgrade maven-resolver-api to 1.9.2 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18880: Priority: Major (was: Critical) > camel-jbang - upgrade maven-resolver-api to 1.9.2 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18878) Autowiring on endpoint works even if is disabled on component
[ https://issues.apache.org/jira/browse/CAMEL-18878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18878. - Fix Version/s: 3.20.2 3.21.0 4.0 Resolution: Fixed > Autowiring on endpoint works even if is disabled on component > - > > Key: CAMEL-18878 > URL: https://issues.apache.org/jira/browse/CAMEL-18878 > Project: Camel > Issue Type: Bug >Affects Versions: 3.20.1 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.20.2, 3.21.0, 4.0 > > > Simi9lar to https://issues.apache.org/jira/browse/CAMEL-16527 > If autowireEnabled=false is set into the component, the DefaultEndpoint in > method "doInit" ignores the fact, that autowiring might be disabled on > component/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18878) Autowiring on endpoint works even if is disabled on component
[ https://issues.apache.org/jira/browse/CAMEL-18878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18878: Component/s: camel-core > Autowiring on endpoint works even if is disabled on component > - > > Key: CAMEL-18878 > URL: https://issues.apache.org/jira/browse/CAMEL-18878 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.20.1 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.20.2, 3.21.0, 4.0 > > > Simi9lar to https://issues.apache.org/jira/browse/CAMEL-16527 > If autowireEnabled=false is set into the component, the DefaultEndpoint in > method "doInit" ignores the fact, that autowiring might be disabled on > component/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18881) Remove camel-swagger-java
[ https://issues.apache.org/jira/browse/CAMEL-18881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675602#comment-17675602 ] Claus Ibsen commented on CAMEL-18881: - camel-jetty camel-netty-http camel-servlet camel-undertow use camel-openapi-java instead camel-rest = remove mention of camel-swagger-java > Remove camel-swagger-java > - > > Key: CAMEL-18881 > URL: https://issues.apache.org/jira/browse/CAMEL-18881 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > It is deprecated in v3 and should be removed, we have camel-openapi-java > instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-18880: - Priority: Critical (was: Major) > camel-jbang - upgrade maven-resolver-api to 1.9.2 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Critical > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675599#comment-17675599 ] Grzegorz Grzybek commented on CAMEL-18880: -- Sure - I should be able to do it this week. > camel-jbang - upgrade maven-resolver-api to 1.9.2 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Critical > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18881) Remove camel-swagger-java
Claus Ibsen created CAMEL-18881: --- Summary: Remove camel-swagger-java Key: CAMEL-18881 URL: https://issues.apache.org/jira/browse/CAMEL-18881 Project: Camel Issue Type: Task Reporter: Claus Ibsen Fix For: 4.0 It is deprecated in v3 and should be removed, we have camel-openapi-java instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18538) camel-jbang - Add log command
[ https://issues.apache.org/jira/browse/CAMEL-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18538: Fix Version/s: 4.0 > camel-jbang - Add log command > - > > Key: CAMEL-18538 > URL: https://issues.apache.org/jira/browse/CAMEL-18538 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.21.0, 4.0 > > > So you can dump logs from running camel apps. > Also maybe a bit like stern can do in k8s where it can tail multiple pods in > the same output. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18497) camel-jbang - camel run -v x.y.z
[ https://issues.apache.org/jira/browse/CAMEL-18497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18497: Fix Version/s: 4.0 > camel-jbang - camel run -v x.y.z > > > Key: CAMEL-18497 > URL: https://issues.apache.org/jira/browse/CAMEL-18497 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Pasquale Congiusti >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.21.0, 4.0 > > > We can specify any Camel version when using the jbang CLI as documented in: > https://camel.apache.org/manual/camel-jbang.html#_using_a_specific_camel_version > However, it would be nice to have the same feature when using directly camel > CLI, in order to have the very same behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-5963) camel-smpp: Support TRX connection mode to the SMSC
[ https://issues.apache.org/jira/browse/CAMEL-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-5963: --- Fix Version/s: 4.0 > camel-smpp: Support TRX connection mode to the SMSC > --- > > Key: CAMEL-5963 > URL: https://issues.apache.org/jira/browse/CAMEL-5963 > Project: Camel > Issue Type: New Feature > Components: camel-smpp >Affects Versions: 2.10.3 >Reporter: Christian Müller >Assignee: Yasser Zamani >Priority: Major > Fix For: 3.21.0, 4.0 > > > See http://camel.465427.n5.nabble.com/camel-smpp-in-trx-mode-td5724608.html > for details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18620) Add redpanda container to test-infra
[ https://issues.apache.org/jira/browse/CAMEL-18620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18620: Fix Version/s: 4.0 > Add redpanda container to test-infra > > > Key: CAMEL-18620 > URL: https://issues.apache.org/jira/browse/CAMEL-18620 > Project: Camel > Issue Type: Test > Components: camel-kafka, tests >Reporter: Federico Mariani >Priority: Minor > Fix For: 3.21.0, 4.0 > > > Add a new mapping in the KafkaServiceFactory with a Redpanda service -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-15111) camel-as2 component failed to parse entity content for encrypted or compressed data
[
https://issues.apache.org/jira/browse/CAMEL-15111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-15111:
Fix Version/s: 4.0
> camel-as2 component failed to parse entity content for encrypted or
> compressed data
> ---
>
> Key: CAMEL-15111
> URL: https://issues.apache.org/jira/browse/CAMEL-15111
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: S. Youssef
>Assignee: Yasser Zamani
>Priority: Minor
> Labels: AS2, encrypted,, receive, server
> Fix For: 3.18.5, 3.20.1, 3.21.0, 4.0
>
> Attachments: image-2021-09-20-16-26-35-053.png
>
>
> AS2 component can receive only messages that has the following content-type:
> * application/edifact
> * application/edi-x12
> * application/edi-consent
> in case of a PLAIN interchange it works fine, however when i try to receive
> an ENCRYPTED/SIGNED/COMPRESSED messages camel don't recognize the content
> type of the interchange.
> Here is the message sent by my trading partner :
> {code:java}
> AS2-From: ESALINK
> AS2-To: YSF2
> AS2-Version: 1.2
> Date: Mon, 25 May 2020 22:04:47 GMT
> Disposition-Notification-Options:
> signed-receipt-protocol=optional,pkcs7-signature;signed-receipt-micalg=optional,md5
> Disposition-Notification-To: ediint-sync-mdn
> EDIINT-Features: multiple-attachments
> Message-ID: <20200525220447.3200.111@DESKTOP-OT6I4JG>
> Subject: message from YSF
> Content-Type: multipart/signed; protocol="application/pkcs7-signature";
> micalg=md5; boundary="--15ECC40FF5D299411590444287BC801"
> 15ECC40FF5D299411590444287BC801
> Content-Transfer-Encoding: binary
> Content-Disposition: attachment; filename="smime.p7m"
> Content-Type: application/pkcs7-mime; smime-type=compressed-data;
> name="smime.p7m"0€*†H†÷
>€0€0*†H†÷
> 0€ *†H†÷
> €$€‚îxrÎÏ+IÍ+Ñ
> )JÌ+NK-ÒuÍKÎOÉÌK-
> RHÊÌK,ªäår†*qÉ,.È/Î,ÉÌϳRH,)ILÎÈjµVHËÌIÍKÌMµU*ÎÍÌMÕ+0ÏUBh©,Hª/(ÈÉLNiÖ/ÈN.6×)µVëÐ-ª±MÍ+KÍÉ/HMÑMI,I´VÀ4'—Ë
> ‰©€S«Í£í;/#;ó‚&¦D P,#ƒaãqƒ&ÆÃ@¦Aã*ƒÆ%†ÜœlÌ¡,lÂLnA†ü¼ ‡0›Ð§É©†|<
> vaրĢÌbC1ŸK˜×=5/µ(³BÁ½(¿´ÀPÆ@
> $Î-,ìšö»0¨RR#
> ŠR‹‹
> øA²Ì‰E%@}F†Úšpr2ŠÉ"€"W€•;¤CŒN™¬—œŸr,/\5##+K#ƒYOú¿¥Šw6ßíiJ(»œqÉjã±_bE§fýÖas®XµxÚ'Ï™|
> ý;ûÄNN7ßÕÆs{é|ƒ|wïkž<×\ý>- ú!ûFƒ™>{Ÿ™Yîúa:ÙúÊšÚÞná°|zu†- è=îwÅ—VßøW§ÿùëãÎ
> þg¥nš
> «½n°tzwË{Lb]0Kÿ¿ÅÛ
> {code}
> camel will send an MDN containing this message:
> {code:java}
> Failed to parse entity content{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18523) camel-jbang - Add watch option
[ https://issues.apache.org/jira/browse/CAMEL-18523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18523: Fix Version/s: 4.0 > camel-jbang - Add watch option > -- > > Key: CAMEL-18523 > URL: https://issues.apache.org/jira/browse/CAMEL-18523 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.21.0, 4.0 > > > You can use the watch shell command but then it restarts the camel cli per > call. This is fast on new computers but maybe not as fast on slower. > We can add a --watch=5 to some command so we let camel cli do the watch which > keeps the camel cli JVM running -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18659) camel-openapi-java - Support for nullable
[
https://issues.apache.org/jira/browse/CAMEL-18659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18659:
Fix Version/s: 4.0
> camel-openapi-java - Support for nullable
> -
>
> Key: CAMEL-18659
> URL: https://issues.apache.org/jira/browse/CAMEL-18659
> Project: Camel
> Issue Type: Improvement
> Components: camel-openapi-java
>Affects Versions: 3.12.0, 3.13.0
>Reporter: M
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.21.0, 4.0
>
>
> Hi,
> I marked field with @Schema annotation like below:
> {color:#bbb529}@Schema(example = "1234", nullable = true)
> private Long id;{color}
> I got output:
> {code:java}
> "id" : {
> "format" : "int64",
> "type" : "integer",
> "example" : 1234
> } {code}
> when my expectation is:
> {code:java}
> "id" : {
> "format" : "int64",
> "type" : "integer",
> "nullable" : true,
> "example" : 1234
> } {code}
> Or maybe I'm doing something wrong ;).
> Open-api 3.0.2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18826) camel-kudu - Install libtinfo on CI to execute all Kudu's unit tests
[
https://issues.apache.org/jira/browse/CAMEL-18826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18826:
Fix Version/s: 4.0
> camel-kudu - Install libtinfo on CI to execute all Kudu's unit tests
>
>
> Key: CAMEL-18826
> URL: https://issues.apache.org/jira/browse/CAMEL-18826
> Project: Camel
> Issue Type: Test
> Components: build system, camel-kudu
>Reporter: Kengo Seki
>Priority: Minor
> Fix For: 3.21.0, 4.0
>
>
> Currently, Kudu's unit tests are not completely executed on CI. For example,
> the following test seems to be successful at first glance.
> https://github.com/apache/camel/actions/runs/3612434723/jobs/6087540407#step:7:27
> But we can see five tests out of seven were skipped in
> components-camel-kudu.log, which is downloadable as a part of test-logs, as
> follows:
> {code}
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.camel.component.kudu.KuduComponentConfigurationTest
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.789
> s - in org.apache.camel.component.kudu.KuduComponentConfigurationTest
> [INFO] Running org.apache.camel.component.kudu.KuduProducerTest
> ...
> [WARNING] Tests run: 3, Failures: 0, Errors: 0, Skipped: 3, Time elapsed:
> 2.133 s - in org.apache.camel.component.kudu.KuduProducerTest
> [INFO] Running org.apache.camel.component.kudu.KuduScanTest
> [WARNING] Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed:
> 1.032 s - in org.apache.camel.component.kudu.KuduScanTest
> [INFO]
> [INFO] Results:
> [INFO]
> [WARNING] Tests run: 7, Failures: 0, Errors: 0, Skipped: 5
> {code}
> Its root cause is recorded in camel-kudu-test.log, which is also a part of
> test-logs. Starting MiniKuduCluster failed due to the lack of libtinfo, so we
> have to install it first to execute all tests.
> {code}
> 2022-12-04 09:18:30,428 [ stderr printer] INFO MiniKuduCluster
> -
> /tmp/kudu-binary-jar16011888995816483654/kudu-binary-1.15.0-linux-x86_64/bin/kudu:
> error while loading shared libraries: libtinfo.so.5: cannot open shared
> object file: No such file or directory
> ...
> 2022-12-04 09:18:30,569 [main ] INFO MiniKuduCluster
> - Caught exception while closing minicluster stdin
> java.io.IOException: Stream closed
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18828) camel-kudu - Add DELETE, UPDATE, and UPSERT support to the producer
[ https://issues.apache.org/jira/browse/CAMEL-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18828: Fix Version/s: 4.0 > camel-kudu - Add DELETE, UPDATE, and UPSERT support to the producer > --- > > Key: CAMEL-18828 > URL: https://issues.apache.org/jira/browse/CAMEL-18828 > Project: Camel > Issue Type: Improvement > Components: camel-kudu >Reporter: Kengo Seki >Priority: Minor > Fix For: 3.21.0, 4.0 > > > Currently, camel-kudu doesn't support these operations, so let's add them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18827) camel-kudu - Fix unit test failure with JDK 17
[
https://issues.apache.org/jira/browse/CAMEL-18827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18827:
Fix Version/s: 4.0
> camel-kudu - Fix unit test failure with JDK 17
> --
>
> Key: CAMEL-18827
> URL: https://issues.apache.org/jira/browse/CAMEL-18827
> Project: Camel
> Issue Type: Test
> Components: camel-kudu
>Reporter: Kengo Seki
>Priority: Minor
> Fix For: 3.21.0, 4.0
>
>
> Some Kudu's unit tests are skipped for JDK 17, as follows:
> {code}
> $ java -version
> openjdk version "17.0.5" 2022-10-18 LTS
> OpenJDK Runtime Environment Corretto-17.0.5.8.1 (build 17.0.5+8-LTS)
> OpenJDK 64-Bit Server VM Corretto-17.0.5.8.1 (build 17.0.5+8-LTS, mixed mode,
> sharing)
> $ cd components/camel-kudu
> $ ../../mvnw clean test
> ...
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @ camel-kudu ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.camel.component.kudu.KuduComponentConfigurationTest
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.521
> s - in org.apache.camel.component.kudu.KuduComponentConfigurationTest
> [INFO] Running org.apache.camel.component.kudu.KuduProducerTest
> [WARNING] Tests run: 3, Failures: 0, Errors: 0, Skipped: 3, Time elapsed:
> 0.045 s - in org.apache.camel.component.kudu.KuduProducerTest
> [INFO] Running org.apache.camel.component.kudu.KuduScanTest
> [WARNING] Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed:
> 0.011 s - in org.apache.camel.component.kudu.KuduScanTest
> [INFO]
> [INFO] Results:
> [INFO]
> [WARNING] Tests run: 7, Failures: 0, Errors: 0, Skipped: 5
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 6.550 s
> [INFO] Finished at: 2022-12-18T09:39:28+09:00
> [INFO]
>
> {code}
> Its cause is reported in camel-kudu-test.log as follows. We have to add the
> "--add-opens" option for JDK 17+, just like CAMEL-16962.
> {code}
> $ cat target/camel-kudu-test.log
> ...
> 2022-12-18 09:39:28,041 [main ] DEBUG IntegrationKuduConfiguration
> - Kudu harness is not runnable because: Unable to make private static
> java.net.InetAddress$NameService java.net.InetAddress.createNameService()
> accessible: module java.base does not "opens java.net" to unnamed module
> @1572270e
> java.lang.reflect.InaccessibleObjectException: Unable to make private static
> java.net.InetAddress$NameService java.net.InetAddress.createNameService()
> accessible: module java.base does not "opens java.net" to unnamed module
> @1572270e
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18687) camel-salesforce: Support Client Credentials OAuth Flow
[ https://issues.apache.org/jira/browse/CAMEL-18687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18687: Fix Version/s: 4.0 > camel-salesforce: Support Client Credentials OAuth Flow > --- > > Key: CAMEL-18687 > URL: https://issues.apache.org/jira/browse/CAMEL-18687 > Project: Camel > Issue Type: New Feature > Components: camel-salesforce >Affects Versions: 3.19.0 >Reporter: Jeremy Ross >Priority: Major > Fix For: 3.21.0, 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18829) camel-yaml-dsl - generate-yaml-schema - Support `additionalProperties: false`
[ https://issues.apache.org/jira/browse/CAMEL-18829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18829: Fix Version/s: 4.0 > camel-yaml-dsl - generate-yaml-schema - Support `additionalProperties: false` > - > > Key: CAMEL-18829 > URL: https://issues.apache.org/jira/browse/CAMEL-18829 > Project: Camel > Issue Type: Task > Components: camel-yaml-dsl >Reporter: Tomohisa Igarashi >Assignee: Tomohisa Igarashi >Priority: Major > Fix For: 3.21.0, 4.0 > > > JSON schema requires `additionalProperties: false` to be specified to > prohibit additional properties those are not explicitly defined in > `properties` > https://json-schema.org/understanding-json-schema/reference/object.html#additional-properties > And it doesn't propagate to the children, i.e. `additionalProperties: false` > needs to be specified on each object definition. > Since camel-yaml-dsl/generate-yaml-schema mojo doesn't add this property at > this moment, the generated schema doesn't really restrict properties. We want > to add an option 'additionalProperties" on generate-yaml-schema mojo, and if > it's false, add `additionalProperties: false` on each objects in generated > schema so that it declares explicit restriction. The option should be `true` > by default so that it doesn't add anything in order to preserve current > behavior. > An example of having `additionalProperties` to be `false` > https://github.com/igarashitm/example-generate-yaml-schema/blob/main/pom.xml#L71 > And generated YAML schema from it > https://github.com/igarashitm/example-generate-yaml-schema/commit/85441fdcc6c641a2ef02aea7149a66a0429b3c92#diff-b1d8ab8b59f212acab62fab8cab033f98736c4bd9e92cc34fcf9b53457dbc1d0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18674) camel-jbang - Run in background
[ https://issues.apache.org/jira/browse/CAMEL-18674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18674: Fix Version/s: 4.0 > camel-jbang - Run in background > --- > > Key: CAMEL-18674 > URL: https://issues.apache.org/jira/browse/CAMEL-18674 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.21.0, 4.0 > > > So you can run the integration in the background > camel run foo.yaml --background > As if you run via > camel run foo.yaml & > then the logging will still happen on system out, which should be off when > running in background. We should log to file instead and have camel log > command to show the logs instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18752) camel-micrometer - Include description in prometheus export
[
https://issues.apache.org/jira/browse/CAMEL-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18752:
Fix Version/s: 4.0
> camel-micrometer - Include description in prometheus export
> ---
>
> Key: CAMEL-18752
> URL: https://issues.apache.org/jira/browse/CAMEL-18752
> Project: Camel
> Issue Type: Improvement
> Components: camel-micrometer
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.21.0, 4.0
>
>
> Even when we have description in camel-micrometer, then I do not see them in
> prometheus exporter (via camel-quarkus).
> A sample output is here, where the HELP only have human description for JVM
> metrics (not from Camel)
> {code}
> # HELP CamelExchangesTotal_total
> # TYPE CamelExchangesTotal_total counter
> CamelExchangesTotal_total{camelContext="ChaosMonkey",routeId="route2",serviceName="MicrometerRoutePolicyService",}
> 19.0
> CamelExchangesTotal_total{camelContext="ChaosMonkey",routeId="route1",serviceName="MicrometerRoutePolicyService",}
> 15.0
> # HELP process_start_time_seconds Start time of the process since unix epoch.
> # TYPE process_start_time_seconds gauge
> process_start_time_seconds 1.66928575989E9
> # HELP CamelRoutesRunning_routes
> # TYPE CamelRoutesRunning_routes gauge
> CamelRoutesRunning_routes{camelContext="ChaosMonkey",eventType="RouteEvent",serviceName="MicrometerEventNotifierService",}
> 2.0
> # HELP jvm_buffer_count_buffers An estimate of the number of buffers in the
> pool
> # TYPE jvm_buffer_count_buffers gauge
> jvm_buffer_count_buffers{id="mapped",} 0.0
> jvm_buffer_count_buffers{id="direct",} 18.0
> # HELP jvm_info_total JVM version info
> # TYPE jvm_info_total counter
> jvm_info_total{runtime="OpenJDK Runtime Environment",vendor="Azul Systems,
> Inc.",version="11.0.13+8-LTS",} 1.0
> # HELP process_uptime_seconds The uptime of the Java virtual machine
> # TYPE process_uptime_seconds gauge
> process_uptime_seconds 75.098
> # HELP system_load_average_1m The sum of the number of runnable entities
> queued to available processors and the number of runnable entities running on
> the available processors averaged over a period of time
> # TYPE system_load_average_1m gauge
> system_load_average_1m 2.45947265625
> # HELP process_files_open_files The open file descriptor count
> # TYPE process_files_open_files gauge
> process_files_open_files 384.0
> # HELP jvm_threads_daemon_threads The current number of live daemon threads
> # TYPE jvm_threads_daemon_threads gauge
> jvm_threads_daemon_threads 18.0
> # HELP CamelExchangesSucceeded_total
> # TYPE CamelExchangesSucceeded_total counter
> CamelExchangesSucceeded_total{camelContext="ChaosMonkey",routeId="route2",serviceName="MicrometerRoutePolicyService",}
> 19.0
> CamelExchangesSucceeded_total{camelContext="ChaosMonkey",routeId="route1",serviceName="MicrometerRoutePolicyService",}
> 15.0
> # HELP jvm_threads_peak_threads The peak live thread count since the Java
> virtual machine started or peak was reset
> # TYPE jvm_threads_peak_threads gauge
> jvm_threads_peak_threads 94.0
> {code}
> I am not sure if we need to do something more special in camel-micrometer.
> But it would be good to dive into the prometheus exporter from quarkus to
> track in the code how this works, so we can find out how.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18834) camel-core - StringQuoteHelper should remove quotes for single element
[ https://issues.apache.org/jira/browse/CAMEL-18834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18834: Fix Version/s: 4.0 > camel-core - StringQuoteHelper should remove quotes for single element > -- > > Key: CAMEL-18834 > URL: https://issues.apache.org/jira/browse/CAMEL-18834 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.20.0 >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.20.1, 3.21.0, 4.0 > > > Reported via > https://github.com/apache/camel/pull/8936 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18830) camel-ehcache - Align to JAXB from camel
[ https://issues.apache.org/jira/browse/CAMEL-18830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18830: Fix Version/s: 4.0 > camel-ehcache - Align to JAXB from camel > > > Key: CAMEL-18830 > URL: https://issues.apache.org/jira/browse/CAMEL-18830 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-ehcache >Affects Versions: 3.20.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.21.0, 4.0 > > > https://github.com/ehcache/ehcache3/issues/2881 > > org.glassfish.jaxb > jaxb-runtime > [2.2,3) > runtime > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18832) camel-spring-boot - Health Check output should include data in full exposure level
[ https://issues.apache.org/jira/browse/CAMEL-18832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18832: Fix Version/s: 4.0 > camel-spring-boot - Health Check output should include data in full exposure > level > -- > > Key: CAMEL-18832 > URL: https://issues.apache.org/jira/browse/CAMEL-18832 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.21.0, 4.0 > > > We have such information with quarkus and we should have that with SB as > well. We may add some verbose=true option or something to enable this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18845) camel-core - Performance overhead for async processing event emitting
[ https://issues.apache.org/jira/browse/CAMEL-18845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18845: Fix Version/s: 4.0 > camel-core - Performance overhead for async processing event emitting > - > > Key: CAMEL-18845 > URL: https://issues.apache.org/jira/browse/CAMEL-18845 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 3.20.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.1, 3.21.0, 4.0 > > > Due to CAMEL-18661 then we emit a special async processing event, that should > not be in use normally, but only for camel-tracing/camel-opentelemtry -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18852) camel-atom/camel-rss - Deprecate basic auth
[ https://issues.apache.org/jira/browse/CAMEL-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18852: Fix Version/s: 4.0 > camel-atom/camel-rss - Deprecate basic auth > --- > > Key: CAMEL-18852 > URL: https://issues.apache.org/jira/browse/CAMEL-18852 > Project: Camel > Issue Type: Improvement > Components: camel-atom, camel-rss >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.21.0, 4.0 > > > If you set username/password then basic auth is in use which is not a secured > protocol. Lets deprecate this to indicate its not recommended to be in-use. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18842) camel-as2 failed to serve signed requests when compression is done before signing
[ https://issues.apache.org/jira/browse/CAMEL-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18842: Fix Version/s: 4.0 > camel-as2 failed to serve signed requests when compression is done before > signing > - > > Key: CAMEL-18842 > URL: https://issues.apache.org/jira/browse/CAMEL-18842 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Reporter: Yasser Zamani >Assignee: Yasser Zamani >Priority: Major > Labels: pull-request-available > Fix For: 3.18.5, 3.20.1, 3.21.0, 4.0 > > Original Estimate: 4h > Remaining Estimate: 4h > > Both compression before and after signature are allowed according to the RFC: > [https://datatracker.ietf.org/doc/html/rfc5402/#section-3] > but currently Camel-AS2 server is only able to serve those requests which > compression is done after signature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18839) upgrade to kafka 3.3.x
[ https://issues.apache.org/jira/browse/CAMEL-18839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18839: Fix Version/s: 4.0 > upgrade to kafka 3.3.x > -- > > Key: CAMEL-18839 > URL: https://issues.apache.org/jira/browse/CAMEL-18839 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.21.0, 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18846) camel-main - Performance overhead due to emitting events not needed
[ https://issues.apache.org/jira/browse/CAMEL-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18846: Fix Version/s: 4.0 > camel-main - Performance overhead due to emitting events not needed > --- > > Key: CAMEL-18846 > URL: https://issues.apache.org/jira/browse/CAMEL-18846 > Project: Camel > Issue Type: Improvement > Components: camel-main >Affects Versions: 3.20.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.1, 3.21.0, 4.0 > > Attachments: after.png, before.png > > > The option camel.main.routesReloadRestartDuration=true adds an overhead due > to need of event notifier for exchanges. > We should change the default value as this is only in need during development > via camel-jbang and hot-reloading of routes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18840) camel-http - HTTP broken followRedirection
[
https://issues.apache.org/jira/browse/CAMEL-18840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18840:
Fix Version/s: 4.0
> camel-http - HTTP broken followRedirection
> ---
>
> Key: CAMEL-18840
> URL: https://issues.apache.org/jira/browse/CAMEL-18840
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.20.0
>Reporter: Valeriy Ak
>Assignee: Claus Ibsen
>Priority: Minor
> Labels: camel-http
> Fix For: 3.20.1, 3.21.0, 4.0
>
>
> Look like in 3.20.0 broken functionallity for disable follow redirections
> (HTTP 300-399 statuses) by set automatic-retries-disabled. Now need also set
> *RedirectHandlingDisabled*
>
> Here simple example:
> {code:java}
> import org.apache.camel.CamelContext;
> import org.apache.camel.Exchange;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.http.HttpComponent;
> import org.apache.camel.impl.DefaultCamelContext;
> import static org.apache.camel.builder.endpoint.StaticEndpointBuilders.http;
> class Scratch {
> public static void main(String[] args) throws Exception {
> //1
> CamelContext context1 = createContext(8080);
> var httpComponent1 = context1.getComponent("http",
> HttpComponent.class);
> httpComponent1.setFollowRedirects(false);
> context1.start();
> var response1 =
> context1.createProducerTemplate().requestBody("direct:http", "");
> //Redirect to Apache Camel Page without any errors
> System.out.println(response1);
> //2
> CamelContext context2 = createContext(8081);
> var httpComponent2 = context2.getComponent("http",
> HttpComponent.class);
> httpComponent2.setFollowRedirects(false);
> httpComponent2.setAutomaticRetriesDisabled(true);
> context2.start();
> var response2 =
> context2.createProducerTemplate().requestBody("direct:http", "");
> //Redirect to Apache Camel Page without any errors
> System.out.println(response2);
> //3
> CamelContext context3 = createContext(8082);
> var httpComponent3 = context3.getComponent("http",
> HttpComponent.class);
> httpComponent3.setFollowRedirects(false);
> httpComponent3.setAutomaticRetriesDisabled(true);
> httpComponent3.setRedirectHandlingDisabled(true);
> context3.start();
> var response3 =
> context3.createProducerTemplate().requestBody("direct:http", "");
> //work as expected - error throws
> System.out.println(response3);
> }
> private static CamelContext createContext(int port) throws Exception {
> CamelContext context = new DefaultCamelContext();
> context.addRoutes(new RouteBuilder() {
> @Override
> public void configure() {
>
> restConfiguration().component("jetty").host("localhost").port(port);
> rest().get("test303").to("direct:addLocation");
> from("direct:addLocation")
> .setHeader("Location",
> constant("https://camel.apache.org;))
> .setHeader(Exchange.HTTP_RESPONSE_CODE,
> constant(303));
> from("direct:http")
> .setHeader(Exchange.HTTP_METHOD, constant("GET"))
> .to(http("localhost:" + port + "/test303")
> .bridgeEndpoint(true)
> .throwExceptionOnFailure(true)
> .advanced()
> .okStatusCodeRange("200-299"))
> .convertBodyTo(String.class);
> }
> });
> return context;
> }
> } {code}
>
> * In version 3.11.1 exaption throws on 2 step with
> setAutomaticRetriesDisabled (for run it - need remove setFollowRedirects)
> * In version 3.20.0 exaption throws {*}only on 3 step{*}.
>
> Please fix it or add description of this new behavior to your documentaions.
> Also I don't understan how to use option
> *camel.component.http.follow-redirects* because seems it does not works as
> expected "Whether to the HTTP request should follow redirects."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18847) camel-console - We need a camel-console-support JAR
[ https://issues.apache.org/jira/browse/CAMEL-18847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18847: Fix Version/s: 4.0 > camel-console - We need a camel-console-support JAR > --- > > Key: CAMEL-18847 > URL: https://issues.apache.org/jira/browse/CAMEL-18847 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 3.20.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.1, 3.21.0, 4.0 > > > We need to move the base classes into a new camel-console-support that > components should use instead of camel-console. > This is to avoid enabling console by default if you use a component that has > console supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18849) camel-core-model - Route properties should be in top of route
[ https://issues.apache.org/jira/browse/CAMEL-18849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18849: Fix Version/s: 4.0 > camel-core-model - Route properties should be in top of route > - > > Key: CAMEL-18849 > URL: https://issues.apache.org/jira/browse/CAMEL-18849 > Project: Camel > Issue Type: Improvement > Components: camel-core-model >Affects Versions: 3.20.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.1, 3.21.0, 4.0 > > > They are in the bottom now > http://camel.apache.org/schema/spring;> > > > > > > > > But we should have route properties in the top. > Route properties are seldom in use so no problem changing this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18841) camel-kafka: producer idempotence is not enabled by default
[ https://issues.apache.org/jira/browse/CAMEL-18841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18841: Fix Version/s: 4.0 > camel-kafka: producer idempotence is not enabled by default > --- > > Key: CAMEL-18841 > URL: https://issues.apache.org/jira/browse/CAMEL-18841 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 3.18.4 >Reporter: Espen Andreassen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.1, 3.21.0, 4.0 > > > Kafka enables idempotence on the producer by default but camel-kafka does not > (see the first bullet point > [here|https://kafka.apache.org/32/documentation.html#upgrade_320_notable]). > As far as I can tell, aligning the following props would fix this: > ||camel-kafka prop name||Kafka value||camel-kafka value|| > |*retries*|[MAX_INT|https://kafka.apache.org/32/documentation.html#producerconfigs_retries]|[0|https://camel.apache.org/components/3.18.x/kafka-component.html#_component_option_retries]| > |*enableIdempotence* > |[true|https://kafka.apache.org/32/documentation.html#producerconfigs_enable.idempotence]|[false|https://camel.apache.org/components/3.18.x/kafka-component.html#_component_option_enableIdempotence]| > |*requestRequiredAcks* > |[all|https://kafka.apache.org/32/documentation.html#producerconfigs_acks]|[1|https://camel.apache.org/components/3.18.x/kafka-component.html#_endpoint_query_option_requestRequiredAcks]| > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18844) Possible memory leak in org.apache.camel.impl.console.EventConsole
[
https://issues.apache.org/jira/browse/CAMEL-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18844:
Fix Version/s: 4.0
> Possible memory leak in org.apache.camel.impl.console.EventConsole
> --
>
> Key: CAMEL-18844
> URL: https://issues.apache.org/jira/browse/CAMEL-18844
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 3.20.0
>Reporter: Rafał Gała
>Assignee: Claus Ibsen
>Priority: Critical
> Fix For: 3.20.1, 3.21.0, 4.0
>
> Attachments: camel-console-3.20.1-SNAPSHOT.jar
>
>
> Today I have upgraded from 3.18.4 to 3.20.0 and did tests under heavy load as
> usual. After processing of approximately 3 millions of exchanges JVM's heap
> usage reached 4GB and it ran out of memory. I analyzed a dump in Eclipse MAT
> and it showed the following:
> {noformat}
> One instance of org.apache.camel.spring.boot.SpringBootCamelContext loaded by
> org.apache.catalina.loader.ParallelWebappClassLoader @ 0x700b5adb0 occupies 3
> 276 629 016 (97,38%) bytes. The memory is accumulated in one instance of
> java.lang.Object[], loaded by , which occupies 3 276 529
> 992 (97,38%)
> bytes.Keywordsorg.apache.camel.spring.boot.SpringBootCamelContextorg.apache.catalina.loader.ParallelWebappClassLoader
> @ 0x700b5adb0java.lang.Object[]{noformat}
> I discovered that the *java.util.ArrayDeque* instance in
> *org.apache.camel.impl.console.EventConsole* instance (most probably the
> exchangeEvents one) contains references to over 12 millions of various
> org.apache.camel.impl.event.* objects, like {*}ExchangeCreatedEvent{*},
> *ExchangeSentEvent* etc.
> I will investigate this further, but it looks like the poll method on
> ArrayDeque does not do something as expected or is used in a wrong way:)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18843) camel-spring-boot - Upgrade to 2.7.7
[ https://issues.apache.org/jira/browse/CAMEL-18843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18843: Fix Version/s: 4.0 > camel-spring-boot - Upgrade to 2.7.7 > > > Key: CAMEL-18843 > URL: https://issues.apache.org/jira/browse/CAMEL-18843 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.5, 3.20.1, 3.21.0, 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18850) camel-core-model - @XmlAttributes should be String or Enum type only
[ https://issues.apache.org/jira/browse/CAMEL-18850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18850: Fix Version/s: 4.0 > camel-core-model - @XmlAttributes should be String or Enum type only > > > Key: CAMEL-18850 > URL: https://issues.apache.org/jira/browse/CAMEL-18850 > Project: Camel > Issue Type: Improvement > Components: camel-core-model >Affects Versions: 3.20.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.1, 3.21.0, 4.0 > > > fhir dataformat > and a few rest definition uses Boolean type instead of String (String allows > property placeholder values in XML DSL) *DONE* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18848) camel-core-model - Rest DSL allowedValues should use definition model for value
[ https://issues.apache.org/jira/browse/CAMEL-18848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18848: Fix Version/s: 4.0 > camel-core-model - Rest DSL allowedValues should use definition model for > value > --- > > Key: CAMEL-18848 > URL: https://issues.apache.org/jira/browse/CAMEL-18848 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-core-model >Affects Versions: 3.20.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.1, 3.21.0, 4.0 > > > This is the only model that is special. We should make it similar and have a > definition class to represent the allowedValue so we can make all DSL parsers > easier to generate for XML and YAML etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18863) camel-pulsar - Support chunking to enable sending a large message
[ https://issues.apache.org/jira/browse/CAMEL-18863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18863: Fix Version/s: 4.0 > camel-pulsar - Support chunking to enable sending a large message > - > > Key: CAMEL-18863 > URL: https://issues.apache.org/jira/browse/CAMEL-18863 > Project: Camel > Issue Type: Improvement > Components: camel-pulsar >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Minor > Fix For: 3.21.0, 4.0 > > > Currently, Pulsar producer can't send a message larger than > [maxMessageSize|https://pulsar.apache.org/docs/2.10.x/concepts-messaging/#messages] > (default: 5MB). > It would be useful to support > [chunking|https://pulsar.apache.org/docs/2.10.x/concepts-messaging/#chunking] > for overcoming this limitation in some cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18868) Aws2-s3: CreateDownloadLink does not work with useDefaultCredentialsProvider
[
https://issues.apache.org/jira/browse/CAMEL-18868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18868:
Fix Version/s: 4.0
> Aws2-s3: CreateDownloadLink does not work with useDefaultCredentialsProvider
>
>
> Key: CAMEL-18868
> URL: https://issues.apache.org/jira/browse/CAMEL-18868
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
>Affects Versions: 3.20.1
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
> Fix For: 3.20.2, 3.21.0, 4.0
>
>
> If component uses default credential provider
> (`useDefaultCredentialsProvider`), operation `createDownloadLink` fails with:
> {quote}Caused by: java.lang.NullPointerException: Access key ID cannot be
> blank.
> at software.amazon.awssdk.utils.Validate.notNull(Validate.java:119)
> at
> software.amazon.awssdk.auth.credentials.AwsBasicCredentials.(AwsBasicCredentials.java:66)
> at
> software.amazon.awssdk.auth.credentials.AwsBasicCredentials.(AwsBasicCredentials.java:58)
> at
> software.amazon.awssdk.auth.credentials.AwsBasicCredentials.create(AwsBasicCredentials.java:78)
> at
> org.apache.camel.component.aws2.s3.AWS2S3Producer.createDownloadLink(AWS2S3Producer.java:590)
> at
> org.apache.camel.component.aws2.s3.AWS2S3Producer.process(AWS2S3Producer.java:122){quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18854) camel-rabbitmq x-queue-type no longer working
[ https://issues.apache.org/jira/browse/CAMEL-18854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18854: Fix Version/s: 4.0 > camel-rabbitmq x-queue-type no longer working > - > > Key: CAMEL-18854 > URL: https://issues.apache.org/jira/browse/CAMEL-18854 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 3.20.0 >Reporter: Hervé Dumont >Priority: Minor > Fix For: 3.20.2, 3.21.0, 4.0 > > > Using rabbitMQ consumer with arg.queue.x-queue-type=quorum is no longer > working with > 3.20 , it was working with 3.18. > Whatever value is set to x-queue-type, connection is done with x-queue-type > set to null. > Regression has been introduced by > [Added support for rabbitmq x-queue-type by eduanb · Pull Request #8725 · > apache/camel (github.com)|https://github.com/apache/camel/pull/8725] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18864) java-joor-dsl - Drop support of class files
[ https://issues.apache.org/jira/browse/CAMEL-18864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18864: Fix Version/s: 4.0 > java-joor-dsl - Drop support of class files > --- > > Key: CAMEL-18864 > URL: https://issues.apache.org/jira/browse/CAMEL-18864 > Project: Camel > Issue Type: Task >Reporter: Nicolas Filotto >Assignee: Nicolas Filotto >Priority: Minor > Fix For: 3.21.0, 4.0 > > > I think we can remove the .class also in camel core for java-joor dsl as it > is not really needed anymore. I think (I am getting older so it is maybe no > longer there) there is an option in camel-main to configure a "compile > directory" so removing would also need to remove that. > source: > https://github.com/apache/camel-quarkus/pull/4359#issuecomment-1372498183 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18857) camel-core - Auto assigned route ids for kamelets/templates should use tempate name as prefix
[ https://issues.apache.org/jira/browse/CAMEL-18857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18857: Fix Version/s: 4.0 > camel-core - Auto assigned route ids for kamelets/templates should use > tempate name as prefix > - > > Key: CAMEL-18857 > URL: https://issues.apache.org/jira/browse/CAMEL-18857 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.21.0, 4.0 > > > This make its easier to spot these routes are from a kamelet/template and not > an end user route. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18856) camel-main - Unable to declare java.util.List bean
[
https://issues.apache.org/jira/browse/CAMEL-18856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18856:
Fix Version/s: 4.0
> camel-main - Unable to declare java.util.List bean
> --
>
> Key: CAMEL-18856
> URL: https://issues.apache.org/jira/browse/CAMEL-18856
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 3.18.1, 3.20.0
> Environment: jdk11
>Reporter: Christian Schubert-Huff
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.20.2, 3.21.0, 4.0
>
>
> I have been unsuccessful in declaring a java.util.List bean. According to
> camel-main documentation, a List bean should be declared using numeric keys
> in square brackets:
> {noformat}
> camel.beans.myprojects[0] = Camel
> camel.beans.myprojects[1] = Kafka
> camel.beans.myprojects[2] = Quarkus
> {noformat}
> This does, however, not actually declare a java.util.List, but a
> java.util.LinkedHashMap, instead.
> Again, reproduction is easy:
> {code:java}
> @Test
> public void testBindBeansList() {
> Main main = new Main();
> main.configure().addRoutesBuilder(new MyRouteBuilder());
> // defining a list bean
> main.addProperty("camel.beans.myprojects[0]", "Camel");
> main.addProperty("camel.beans.myprojects[1]", "Kafka");
> main.addProperty("camel.beans.myprojects[2]", "Quarkus");
> main.start();
> CamelContext camelContext = main.getCamelContext();
> assertNotNull(camelContext);
> Object bean = camelContext.getRegistry().lookupByName("myprojects");
> assertNotNull(bean);
> assertInstanceOf(java.util.List.class, bean);
> java.util.List list = (java.util.List) bean;
> assertEquals(3, list.size());
> assertEquals("Camel", list.get(0));
> assertEquals("Kafka", list.get(1));
> assertEquals("Quarkus", list.get(2));
> main.stop();
> } {code}
> There is a workaround, which is to use java.util.List#of, which is also more
> concise, but only possible if using Java 9 or above:
> {noformat}
> camel.beans.myprojects = #class:java.util.List#of("Camel", "Kafka",
> "Quarkus"){noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18860) java-joor-dsl - Adapt the code for native compilation
[ https://issues.apache.org/jira/browse/CAMEL-18860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18860: Fix Version/s: 4.0 > java-joor-dsl - Adapt the code for native compilation > - > > Key: CAMEL-18860 > URL: https://issues.apache.org/jira/browse/CAMEL-18860 > Project: Camel > Issue Type: Task >Reporter: Nicolas Filotto >Assignee: Nicolas Filotto >Priority: Minor > Fix For: 3.21.0, 4.0 > > > To ease the native compilation of routes written using the Java DSL, we need > to adapt the code to be able to reuse some parts of the existing code. > See https://github.com/apache/camel-quarkus/issues/4358 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18865) camel-main - Setters not invoked on bean that implements Map
[
https://issues.apache.org/jira/browse/CAMEL-18865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18865:
Fix Version/s: 4.0
> camel-main - Setters not invoked on bean that implements Map
>
>
> Key: CAMEL-18865
> URL: https://issues.apache.org/jira/browse/CAMEL-18865
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 3.20.0
> Environment: jdk11, camel-main, camel-jms, IBM-MQ 9.2
> (https://mvnrepository.com/artifact/com.ibm.mq/com.ibm.mq.allclient)
>Reporter: Christian Schubert-Huff
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.20.2, 3.21.0, 4.0
>
>
> We are having trouble configuring camel-jms with IBM-MQ as runtime
> implementation, using camel-main.
> Doing so requires the declaration of a connection factory, which, in our
> case, is
> [com.ibm.mq.jms.MQConnectionFactory|https://www.ibm.com/docs/api/v1/content/SSFKSJ_9.2.0/com.ibm.mq.javadoc.doc/WMQJMSClasses/com/ibm/mq/jms/MQConnectionFactory.html].
> Unfortunately, this class implements both {{javax.jms.ConnectionFactory}}
> and {{{}java.util.Map{}}}. Also, the
> setters of that class have side effects, that are non-trivial to reproduce.
> What was really troubling us was that, contrary to intuition, defining a bean
> like this:
> {code:java}
> camel.beans.mqConnectionFactory = #class:com.ibm.mq.jms.MQConnectionFactory
> camel.beans.mqConnectionFactory.hostName = mqhost
> {code}
> does not actually invoke the setHostName method on the factory. Instead,
> value "mqhost" is put under key "hostName" into the map.
> Reproduction can be achieved with a quick custom class, like this:
> {code:java}
> package org.apache.camel.main;
> import java.util.HashMap;
> public class MyFooFactory extends HashMap {
> private String hostName;
> public String getHostName() {
> return hostName;
> }
> public void setHostName(String hostName) {
> this.hostName = hostName;
> }
> }
> {code}
> and a unit test, which checks for the hostName:
> {code:java}
> @Test
> public void testBindBeansDottedHybridMap() {
> Main main = new Main();
> main.configure().addRoutesBuilder(new MyRouteBuilder());
> // defining a factory bean
> main.addProperty("camel.beans.myfactory",
> "#class:org.apache.camel.main.MyFooFactory");
> main.addProperty("camel.beans.myfactory.hostName", "localhost");
> main.start();
> CamelContext camelContext = main.getCamelContext();
> assertNotNull(camelContext);
> Object bean = camelContext.getRegistry().lookupByName("myfactory");
> assertNotNull(bean);
> assertInstanceOf(MyFooFactory.class, bean);
> MyFooFactory factory = (MyFooFactory) bean;
> assertEquals("localhost", factory.getHostName());
> main.stop();
> }
> {code}
> For a custom bean that is under our own control, I would consider
> implementing java.util.Map and having additional custom getters and setters
> with side-effects to be invalid, but the IBM-MQ JMS client is out of our
> control - and required for our use case.
> If the dotted annotation is used, it may be preferable to check for a
> suitable setter first, and only if that is missing, to check if the bean
> implements java.util.Map.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18872) camel-core-model - Rest DSL param example not available in XML and YAML DSL
[ https://issues.apache.org/jira/browse/CAMEL-18872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18872: Fix Version/s: 4.0 > camel-core-model - Rest DSL param example not available in XML and YAML DSL > --- > > Key: CAMEL-18872 > URL: https://issues.apache.org/jira/browse/CAMEL-18872 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.20.1 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.20.2, 3.21.0, 4.0 > > > A model change in 3.20.1 mistakenly removed examples from rest-dsl for param. > Adding this back. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18875) camel-jms - Logging less noisy when temporary reply queue is refreshed
[ https://issues.apache.org/jira/browse/CAMEL-18875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18875: Fix Version/s: 4.0 > camel-jms - Logging less noisy when temporary reply queue is refreshed > -- > > Key: CAMEL-18875 > URL: https://issues.apache.org/jira/browse/CAMEL-18875 > Project: Camel > Issue Type: Improvement > Components: camel-jms >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.21.0, 4.0 > > > Reported in user forum -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18877) camel-caffeine - Key should be string type
[ https://issues.apache.org/jira/browse/CAMEL-18877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18877. -- Resolution: Fixed > camel-caffeine - Key should be string type > -- > > Key: CAMEL-18877 > URL: https://issues.apache.org/jira/browse/CAMEL-18877 > Project: Camel > Issue Type: Improvement > Components: camel-caffeine >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.21.0, 4.0 > > > The key is Object type which is too generic, and its better to use a String > type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18877) camel-caffeine - Key should be string type
[ https://issues.apache.org/jira/browse/CAMEL-18877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18877: - Fix Version/s: 4.0 > camel-caffeine - Key should be string type > -- > > Key: CAMEL-18877 > URL: https://issues.apache.org/jira/browse/CAMEL-18877 > Project: Camel > Issue Type: Improvement > Components: camel-caffeine >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.21.0, 4.0 > > > The key is Object type which is too generic, and its better to use a String > type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18874) camel-file - When possible, pass the exchange to the exception handler
[
https://issues.apache.org/jira/browse/CAMEL-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675585#comment-17675585
]
Moshe Elisha edited comment on CAMEL-18874 at 1/11/23 2:02 PM:
---
[~davsclaus] what do you recommend regarding backward compatibility?
I see that at least in the Camel project, only
SalesforceConsumer#handleException is overriding (but I'm not sure why).
If I can assume no one else in the world is overriding (or ignore them), I can
do something like the below.
Even with the below approach, backward compatibility might break as we will now
invoke "handleException(message, exchange, t)" instead of
"handleException(message, t)".
{{protected void handleException(Throwable t) {}}
{{ handleException(null, null, t);}}
{{}}}
{{protected void handleException(String message, Throwable t) {}}
{{ handleException(message, null, t);}}
{{}}}
{{protected void handleException(String message, Exchange exchange, Throwable
t) {}}
{{ Throwable newt = (t == null) ? new IllegalArgumentException("Handling
[null] exception") : t;}}
{{{}// This "if" is to maximize backward compatibility
otherw{}}}{{{}ise calling {}}}{{handleException(message, exchange, newt) would
have been much nicer.}}
{{ if (message == null && exchange == null) { }}
{{ getExceptionHandler().handleException(newt);}}
{{ } else if (exchange == null) {}}
{{ getExceptionHandler().handleException(message, newt);}}
{{ } else {}}
{{ getExceptionHandler().handleException(message, exchange, newt);}}
{{ }}}
{{}}}
was (Author: elishamoshe):
[~davsclaus] what do you recommend regarding backward compatibility?
I see that at least in the Camel project, only
SalesforceConsumer#handleException is overriding (but I'm not sure why).
If I can assume no one else in the world is overriding (or ignore them), I can
do something like the below.
Even with the below approach, backward compatibility might break as we will now
invoke "handleException(message, exchange, t)" instead of
"handleException(message, t)".
{{protected void handleException(Throwable t) {}}
{{ handleException(null, null, t);}}
{{}}}
{{protected void handleException(String message, Throwable t) {}}
{{ handleException(message, null, t);}}
{{}}}
{{protected void handleException(String message, Exchange exchange, Throwable
t) {}}
{{ Throwable newt = (t == null) ? new IllegalArgumentException("Handling
[null] exception") : t;}}
{{{}// This "if" is to maximize backward compatibility
otherw{}}}{{{}ise calling {}}}{{{}handleException(message, exchange, newt)
would have been much nicer.{}}}{{{}{}}}
{{ if (message == null && exchange == null) { }}
{{ getExceptionHandler().handleException(newt);}}
{{ } else if (exchange == null) {}}
{{ getExceptionHandler().handleException(message, newt);}}
{{ } else {}}
{{ getExceptionHandler().handleException(message, exchange, newt);}}
{{ }}}
{{}}}
> camel-file - When possible, pass the exchange to the exception handler
> --
>
> Key: CAMEL-18874
> URL: https://issues.apache.org/jira/browse/CAMEL-18874
> Project: Camel
> Issue Type: Improvement
> Components: camel-file, camel-ftp, camel-sftp
>Affects Versions: 3.19.0
>Reporter: Moshe Elisha
>Priority: Major
> Fix For: 3.21.0
>
>
> Several places use the
> {{org.apache.camel.spi.ExceptionHandler#handleException(java.lang.String,
> java.lang.Throwable)}}
>
> instead of
>
> {{org.apache.camel.spi.ExceptionHandler#handleException(java.lang.String,
> org.apache.camel.Exchange, java.lang.Throwable)}}
>
> even when the exchange is available in scope.
> One example for that is
> org.apache.camel.component.file.GenericFileConsumer#processExchange
>
> The exchange is sometimes needed for additional information. For example, if
> a download of a file from an SFTP server fails, the exchange will hold the
> file details for logging purposes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18874) camel-file - When possible, pass the exchange to the exception handler
[
https://issues.apache.org/jira/browse/CAMEL-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675585#comment-17675585
]
Moshe Elisha commented on CAMEL-18874:
--
[~davsclaus] what do you recommend regarding backward compatibility?
I see that at least in the Camel project, only
SalesforceConsumer#handleException is overriding (but I'm not sure why).
If I can assume no one else in the world is overriding (or ignore them), I can
do something like the below.
Even with the below approach, backward compatibility might break as we will now
invoke "handleException(message, exchange, t)" instead of
"handleException(message, t)".
{{protected void handleException(Throwable t) {}}
{{ handleException(null, null, t);}}
{{}}}
{{protected void handleException(String message, Throwable t) {}}
{{ handleException(message, null, t);}}
{{}}}
{{protected void handleException(String message, Exchange exchange, Throwable
t) {}}
{{ Throwable newt = (t == null) ? new IllegalArgumentException("Handling
[null] exception") : t;}}
{{{}// This "if" is to maximize backward compatibility
otherw{}}}{{{}ise calling {}}}{{{}handleException(message, exchange, newt)
would have been much nicer.{}}}{{{}{}}}
{{ if (message == null && exchange == null) { }}
{{ getExceptionHandler().handleException(newt);}}
{{ } else if (exchange == null) {}}
{{ getExceptionHandler().handleException(message, newt);}}
{{ } else {}}
{{ getExceptionHandler().handleException(message, exchange, newt);}}
{{ }}}
{{}}}
> camel-file - When possible, pass the exchange to the exception handler
> --
>
> Key: CAMEL-18874
> URL: https://issues.apache.org/jira/browse/CAMEL-18874
> Project: Camel
> Issue Type: Improvement
> Components: camel-file, camel-ftp, camel-sftp
>Affects Versions: 3.19.0
>Reporter: Moshe Elisha
>Priority: Major
> Fix For: 3.21.0
>
>
> Several places use the
> {{org.apache.camel.spi.ExceptionHandler#handleException(java.lang.String,
> java.lang.Throwable)}}
>
> instead of
>
> {{org.apache.camel.spi.ExceptionHandler#handleException(java.lang.String,
> org.apache.camel.Exchange, java.lang.Throwable)}}
>
> even when the exchange is available in scope.
> One example for that is
> org.apache.camel.component.file.GenericFileConsumer#processExchange
>
> The exchange is sometimes needed for additional information. For example, if
> a download of a file from an SFTP server fails, the exchange will hold the
> file details for logging purposes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
Claus Ibsen created CAMEL-18880: --- Summary: camel-jbang - upgrade maven-resolver-api to 1.9.2 Key: CAMEL-18880 URL: https://issues.apache.org/jira/browse/CAMEL-18880 Project: Camel Issue Type: Dependency upgrade Components: camel-jbang Reporter: Claus Ibsen Fix For: 3.21.0, 4.0 We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code should be changed a bit. It may be easier to do this on camel-3.x branch as main is for v4 and its more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-18880: --- Assignee: Grzegorz Grzybek > camel-jbang - upgrade maven-resolver-api to 1.9.2 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18877) camel-caffeine - Key should be string type
[ https://issues.apache.org/jira/browse/CAMEL-18877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675573#comment-17675573 ] Andrea Cosentino commented on CAMEL-18877: -- This will require the removal of keyType parameter > camel-caffeine - Key should be string type > -- > > Key: CAMEL-18877 > URL: https://issues.apache.org/jira/browse/CAMEL-18877 > Project: Camel > Issue Type: Improvement > Components: camel-caffeine >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.21.0 > > > The key is Object type which is too generic, and its better to use a String > type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18496) Remove deprecated components
[ https://issues.apache.org/jira/browse/CAMEL-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17672245#comment-17672245 ] Otavio Rodolfo Piske edited comment on CAMEL-18496 at 1/11/23 9:00 AM: --- [~acosentino] oh, nice one! was (Author: orpiske): [~acosentino] oh, nice one! BTW, let me close this, as all of the listed ones have been removed. > Remove deprecated components > > > Key: CAMEL-18496 > URL: https://issues.apache.org/jira/browse/CAMEL-18496 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.21.0 > > > * camel-ahc: CAMEL-17667 > * camel-ahc-ws: CAMEL-17667 > * camel-dozer: CAMEL-18455 > * camel-cmis: https://issues.apache.org/jira/browse/CAMEL-18495 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18496) Remove deprecated components
[ https://issues.apache.org/jira/browse/CAMEL-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17672245#comment-17672245 ] Otavio Rodolfo Piske commented on CAMEL-18496: -- [~acosentino] oh, nice one! BTW, let me close this, as all of the listed ones have been removed. > Remove deprecated components > > > Key: CAMEL-18496 > URL: https://issues.apache.org/jira/browse/CAMEL-18496 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.21.0 > > > * camel-ahc: CAMEL-17667 > * camel-ahc-ws: CAMEL-17667 > * camel-dozer: CAMEL-18455 > * camel-cmis: https://issues.apache.org/jira/browse/CAMEL-18495 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18496) Remove deprecated components
[ https://issues.apache.org/jira/browse/CAMEL-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17671911#comment-17671911 ] Andrea Cosentino commented on CAMEL-18496: -- Since we are switching to Camel 4 I'm going to open an issue to remove also Camel Zipkin. > Remove deprecated components > > > Key: CAMEL-18496 > URL: https://issues.apache.org/jira/browse/CAMEL-18496 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.21.0 > > > * camel-ahc: CAMEL-17667 > * camel-ahc-ws: CAMEL-17667 > * camel-dozer: CAMEL-18455 > * camel-cmis: https://issues.apache.org/jira/browse/CAMEL-18495 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18879) Remove Camel-Zipkin after deprecation
Andrea Cosentino created CAMEL-18879: Summary: Remove Camel-Zipkin after deprecation Key: CAMEL-18879 URL: https://issues.apache.org/jira/browse/CAMEL-18879 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0 I think we should remove it for Camel 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
