[jira] [Resolved] (CAMEL-21435) Commons-pool2: When Camel Netty configured with producerPoolMaxTotal=1 and retry, the application hangs
[
https://issues.apache.org/jira/browse/CAMEL-21435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21435.
-
Fix Version/s: 4.9.0
Assignee: Claus Ibsen
Resolution: Information Provided
Added a note for the docs about the danger of setting this value too low.
> Commons-pool2: When Camel Netty configured with producerPoolMaxTotal=1 and
> retry, the application hangs
> ---
>
> Key: CAMEL-21435
> URL: https://issues.apache.org/jira/browse/CAMEL-21435
> Project: Camel
> Issue Type: Bug
> Components: camel-netty
>Reporter: Dmitrii Kriukov
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.9.0
>
>
> Retry on the onException() clause seems to be impossible for
> producerPoolMaxTotal=1 (leads to call of
> GenericObjectPoolConfig.setMaxTotal())
> This causes infinite hanging in case of network IO exceptions.
> Netty attempts to utilize a new connection when the old one is still
> unreleased.
> It boils down to method
> org.apache.commons.pool2.impl.GenericObjectPool::borrowObject(Duration
> borrowMaxWaitDuration) throws Exception {}
> When producerPoolBlockWhenExhausted = true (the default value), the
> application hangs.
> When producerPoolBlockWhenExhausted = false, I get an exception
> 2024-11-11 13:41:44 ERROR [com.opt.obp.ser.ada.cam.Logger] (Camel Thread #2 -
> NettyClientTCPWorker) <> Exception occurred:
> java.util.NoSuchElementException: Pool exhausted
> So, either way it's impossible to serve
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21439) camel-etcd3: all tests are broken
[
https://issues.apache.org/jira/browse/CAMEL-21439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897868#comment-17897868
]
Otavio Rodolfo Piske commented on CAMEL-21439:
--
+1. Let's deprecate this one. Later I'll create the ticket and mark the code as
deprecated so we can remove it after the next LTS.
> camel-etcd3: all tests are broken
> -
>
> Key: CAMEL-21439
> URL: https://issues.apache.org/jira/browse/CAMEL-21439
> Project: Camel
> Issue Type: Test
> Components: camel-etcd3
>Affects Versions: 4.9.0
>Reporter: Otavio Rodolfo Piske
>Priority: Minor
>
> Something has broken etcd3 very badly and tests are not working at all. This
> could indicate a serious problem with the component.
> Running the tests causes these messages to be printed:
> {noformat}
> Nov 11, 2024 10:29:41 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:42 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:44 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:47 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:51 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:59 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:30:09 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:30:25 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> {noformat}
> And the logs:
> {code:java}
> 2024-11-12 10:01:46,517 [ault-executor-0] WARN AbstractNameResolver
> - Error while getting list of servers
> java.lang.IllegalStateException: Not called from the SynchronizationContext
> at
> com.google.common.base.Preconditions.checkState(Preconditions.java:513)
> ~[guava-33.3.1-jre.jar:?]
> at
> io.grpc.SynchronizationContext.throwIfNotInThisSynchronizationContext(SynchronizationContext.java:134)
> ~[grpc-api-1.68.1.jar:1.68.1]
> at
> io.grpc.internal.ManagedChannelImpl$NameResolverListener.onResult2(ManagedChannelImpl.java:1686)
> ~[grpc-core-1.68.1.jar:1.68.1]
> at
> io.grpc.internal.RetryingNameResolver$RetryingListener.onResult2(RetryingNameResolver.java:107)
> ~[grpc-core-1.68.1.jar:1.68.1]
> at io.grpc.NameResolver$Listener2.onAddresses(NameResolver.java:228)
> ~[grpc-api-1.68.1.jar:1.68.1]
> at
> io.etcd.jetcd.resolver.AbstractNameResolver.doResolve(AbstractNameResolver.java:124)
> ~[jetcd-core-0.8.3.jar:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21439) camel-etcd3: all tests are broken
[
https://issues.apache.org/jira/browse/CAMEL-21439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske reassigned CAMEL-21439:
Assignee: Otavio Rodolfo Piske
> camel-etcd3: all tests are broken
> -
>
> Key: CAMEL-21439
> URL: https://issues.apache.org/jira/browse/CAMEL-21439
> Project: Camel
> Issue Type: Test
> Components: camel-etcd3
>Affects Versions: 4.9.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Minor
>
> Something has broken etcd3 very badly and tests are not working at all. This
> could indicate a serious problem with the component.
> Running the tests causes these messages to be printed:
> {noformat}
> Nov 11, 2024 10:29:41 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:42 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:44 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:47 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:51 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:59 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:30:09 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:30:25 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> {noformat}
> And the logs:
> {code:java}
> 2024-11-12 10:01:46,517 [ault-executor-0] WARN AbstractNameResolver
> - Error while getting list of servers
> java.lang.IllegalStateException: Not called from the SynchronizationContext
> at
> com.google.common.base.Preconditions.checkState(Preconditions.java:513)
> ~[guava-33.3.1-jre.jar:?]
> at
> io.grpc.SynchronizationContext.throwIfNotInThisSynchronizationContext(SynchronizationContext.java:134)
> ~[grpc-api-1.68.1.jar:1.68.1]
> at
> io.grpc.internal.ManagedChannelImpl$NameResolverListener.onResult2(ManagedChannelImpl.java:1686)
> ~[grpc-core-1.68.1.jar:1.68.1]
> at
> io.grpc.internal.RetryingNameResolver$RetryingListener.onResult2(RetryingNameResolver.java:107)
> ~[grpc-core-1.68.1.jar:1.68.1]
> at io.grpc.NameResolver$Listener2.onAddresses(NameResolver.java:228)
> ~[grpc-api-1.68.1.jar:1.68.1]
> at
> io.etcd.jetcd.resolver.AbstractNameResolver.doResolve(AbstractNameResolver.java:124)
> ~[jetcd-core-0.8.3.jar:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21446) configmap/secret - default takes precedence
[
https://issues.apache.org/jira/browse/CAMEL-21446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Jalaksa updated CAMEL-21446:
--
Description:
Created a simple integration using Karavan
{code:java}
- rest:
id: rest-d471
post:
- id: post-126a
path: /injectionTest
to: direct:injectionTest
- route:
id: route-a292
from:
id: from-b12a
uri: direct
parameters:
name: injectionTest
steps:
- to:
id: to-bab9
uri: kubernetes-config-maps
parameters:
namespace: default
masterUrl: kubernetes.default.svc:443
operation: listConfigMaps
- marshal:
id: marshal-55e5
json:
id: json-b0d1
- log:
id: log-d04e
message: >-
Printing test configmap without default
{{configmap:secondmap/test}}
- log:
id: log-3396
message: Printing test secret without default
{{secret:secondsecret/test}}
- log:
id: log-f123
message: >-
Printing test configmap with default
{{configmap:secondmap/test:default}}
- log:
id: log-f123
message: >-
Printing test secret with default
{{configmap:secondsecret/test:default}} {code}
Output in my testing minikube container:
{code:java}
2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
: Printing test configmap without default working
2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
: Printing test secret without default mysecretvalue
2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
: Printing test configmap with default default
2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
: Printing test secret with default default {code}
So when using the default in property placeholders it will take precedence even
if given key is present.
was:
Created a simple integration using Karavan
{code:java}
- rest:
id: rest-d471
post:
- id: post-126a
path: /injectionTest
to: direct:injectionTest
- route:
id: route-a292
from:
id: from-b12a
uri: direct
parameters:
name: injectionTest
steps:
- to:
id: to-bab9
uri: kubernetes-config-maps
parameters:
namespace: default
masterUrl: kubernetes.default.svc:443
operation: listConfigMaps
- marshal:
id: marshal-55e5
json:
id: json-b0d1
- log:
id: log-d04e
message: >-
Printing test configmap without default
{{configmap:secondmap/test}}
- log:
id: log-3396
message: Printing test secret without default
{{secret:secondsecret/test}}
- log:
id: log-f123
message: >-
Printing test configmap with default
{{configmap:secondmap/test:default}}
- log:
id: log-f123
message: >-
Printing test secret with default
{{configmap:secondsecret/test:default}} {code}
Output in my testing minikube container:
{code:java}
2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
: Printing test configmap without default working
2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
: Printing test secret without default mysecretvalue
2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
: Printing test configmap with default default
2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
: Printing test secret with default default {code}
> configmap/secret - default takes precedence
> ---
>
> Key: CAMEL-21446
> URL: https://issues.apache.org/jira/browse/CAMEL-21446
> Project: Camel
> Issue Type: Bug
> Components: camel-kubernetes
>Affects Versions: 4.8.1
>Reporter: Filip Jalaksa
>Priority: Minor
>
> Created a simple integration using Karavan
> {code:java}
> - rest:
> id: rest-d471
> post:
> - id: post-126a
> path: /injectionTest
> to: direct:injectionTest
> - route:
> id: route-a292
> from:
> id: from-b12a
> uri: direct
> parameters:
> name: injectionTest
> steps:
> - to:
> id: to-bab9
> uri: kubernetes-config-maps
> parameters:
> namesp
[jira] [Updated] (CAMEL-21445) camel-core - Vault with secret refresh should be disabled as default
[ https://issues.apache.org/jira/browse/CAMEL-21445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21445: - Fix Version/s: 4.8.2 > camel-core - Vault with secret refresh should be disabled as default > > > Key: CAMEL-21445 > URL: https://issues.apache.org/jira/browse/CAMEL-21445 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-main >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > See chat > [https://camel.zulipchat.com/#narrow/channel/352237-camel-jbang/topic/export.20with.20vault] > > Change the default to false in the camel-main vault configuration. > Add note about this change in the 4.9 upgrade guide > To enable you just set > camel.vault.kubernetes.refreshEnabled=true > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21447) camel-spring-boot - Upgrade to 3.4.0
Claus Ibsen created CAMEL-21447: --- Summary: camel-spring-boot - Upgrade to 3.4.0 Key: CAMEL-21447 URL: https://issues.apache.org/jira/browse/CAMEL-21447 Project: Camel Issue Type: Dependency upgrade Components: camel-spring-boot Reporter: Claus Ibsen Fix For: 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21446) configmap/secret - default takes precedence
Filip Jalaksa created CAMEL-21446:
-
Summary: configmap/secret - default takes precedence
Key: CAMEL-21446
URL: https://issues.apache.org/jira/browse/CAMEL-21446
Project: Camel
Issue Type: Bug
Components: camel-kubernetes
Affects Versions: 4.8.1
Reporter: Filip Jalaksa
Created a simple integration using Karavan
- rest:
id: rest-d471
post:
- id: post-126a
path: /injectionTest
to: direct:injectionTest
- route:
id: route-a292
from:
id: from-b12a
uri: direct
parameters:
name: injectionTest
steps:
- to:
id: to-bab9
uri: kubernetes-config-maps
parameters:
namespace: default
masterUrl: kubernetes.default.svc:443
operation: listConfigMaps
- marshal:
id: marshal-55e5
json:
id: json-b0d1
- log:
id: log-d04e
message: >-
Printing test configmap without default
\{{configmap:secondmap/test}}
- log:
id: log-3396
message: Printing test secret without default
\{{secret:secondsecret/test}}
- log:
id: log-f123
message: >-
Printing test configmap with default
\{{configmap:secondmap/test:default}}
- log:
id: log-f123
message: >-
Printing test secret with default
\{{configmap:secondsecret/test:default}}
When using the default value in the property placeholders, default is returned
even if the key is present.
Output in my testing minikube container:
{code:java}
2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
: Printing test configmap without default working
2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
: Printing test secret without default mysecretvalue
2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
: Printing test configmap with default default
2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
: Printing test secret with default default {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21439) camel-etcd3: all tests are broken
[
https://issues.apache.org/jira/browse/CAMEL-21439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897822#comment-17897822
]
Otavio Rodolfo Piske commented on CAMEL-21439:
--
[~davsclaus] is it widely used? I don't remember seeing much activity on this
one, so we could consider deprecating it, indeed.
> camel-etcd3: all tests are broken
> -
>
> Key: CAMEL-21439
> URL: https://issues.apache.org/jira/browse/CAMEL-21439
> Project: Camel
> Issue Type: Test
> Components: camel-etcd3
>Affects Versions: 4.9.0
>Reporter: Otavio Rodolfo Piske
>Priority: Minor
>
> Something has broken etcd3 very badly and tests are not working at all. This
> could indicate a serious problem with the component.
> Running the tests causes these messages to be printed:
> {noformat}
> Nov 11, 2024 10:29:41 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:42 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:44 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:47 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:51 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:59 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:30:09 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:30:25 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> {noformat}
> And the logs:
> {code:java}
> 2024-11-12 10:01:46,517 [ault-executor-0] WARN AbstractNameResolver
> - Error while getting list of servers
> java.lang.IllegalStateException: Not called from the SynchronizationContext
> at
> com.google.common.base.Preconditions.checkState(Preconditions.java:513)
> ~[guava-33.3.1-jre.jar:?]
> at
> io.grpc.SynchronizationContext.throwIfNotInThisSynchronizationContext(SynchronizationContext.java:134)
> ~[grpc-api-1.68.1.jar:1.68.1]
> at
> io.grpc.internal.ManagedChannelImpl$NameResolverListener.onResult2(ManagedChannelImpl.java:1686)
> ~[grpc-core-1.68.1.jar:1.68.1]
> at
> io.grpc.internal.RetryingNameResolver$RetryingListener.onResult2(RetryingNameResolver.java:107)
> ~[grpc-core-1.68.1.jar:1.68.1]
> at io.grpc.NameResolver$Listener2.onAddresses(NameResolver.java:228)
> ~[grpc-api-1.68.1.jar:1.68.1]
> at
> io.etcd.jetcd.resolver.AbstractNameResolver.doResolve(AbstractNameResolver.java:124)
> ~[jetcd-core-0.8.3.jar:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21446) configmap/secret - default takes precedence
[
https://issues.apache.org/jira/browse/CAMEL-21446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-21446:
Assignee: Marco Carletti
> configmap/secret - default takes precedence
> ---
>
> Key: CAMEL-21446
> URL: https://issues.apache.org/jira/browse/CAMEL-21446
> Project: Camel
> Issue Type: Bug
> Components: camel-kubernetes
>Affects Versions: 4.8.1
>Reporter: Filip Jalaksa
>Assignee: Marco Carletti
>Priority: Minor
>
> Created a simple integration using Karavan
> {code:java}
> - rest:
> id: rest-d471
> post:
> - id: post-126a
> path: /injectionTest
> to: direct:injectionTest
> - route:
> id: route-a292
> from:
> id: from-b12a
> uri: direct
> parameters:
> name: injectionTest
> steps:
> - to:
> id: to-bab9
> uri: kubernetes-config-maps
> parameters:
> namespace: default
> masterUrl: kubernetes.default.svc:443
> operation: listConfigMaps
> - marshal:
> id: marshal-55e5
> json:
> id: json-b0d1
> - log:
> id: log-d04e
> message: >-
> Printing test configmap without default
> {{configmap:secondmap/test}}
> - log:
> id: log-3396
> message: Printing test secret without default
> {{secret:secondsecret/test}}
> - log:
> id: log-f123
> message: >-
> Printing test configmap with default
> {{configmap:secondmap/test:default}}
> - log:
> id: log-f123
> message: >-
> Printing test secret with default
> {{configmap:secondsecret/test:default}} {code}
> Output in my testing minikube container:
> {code:java}
> 2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
> : Printing test configmap without default working
> 2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
> : Printing test secret without default mysecretvalue
> 2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
> : Printing test configmap with default default
> 2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
> : Printing test secret with default default {code}
> So when using the default in property placeholders it will take precedence
> even if given key is present.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21444) camel-jbang - catalog using since-after can do NPE if version is single digit
[ https://issues.apache.org/jira/browse/CAMEL-21444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21444. - Assignee: Claus Ibsen Resolution: Fixed > camel-jbang - catalog using since-after can do NPE if version is single digit > - > > Key: CAMEL-21444 > URL: https://issues.apache.org/jira/browse/CAMEL-21444 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.1 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.8.2, 4.9.0 > > > camel> catalog other --since-after=4 > java.lang.NullPointerException: Cannot invoke "String.length()" because "t1" > is null > at > org.apache.camel.dsl.jbang.core.common.VersionHelper.compare(VersionHelper.java:107) > at > org.apache.camel.dsl.jbang.core.common.VersionHelper.isGE(VersionHelper.java:55) > at > org.apache.camel.dsl.jbang.core.commands.catalog.CatalogBaseCommand.lambda$doCall$2(CatalogBaseCommand.java:137) > at > java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:178) > at > java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625) > at > java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509) > at > java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) > at > java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921) > at > java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at > java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682) > at > org.apache.camel.dsl.jbang.core.commands.catalog.CatalogBaseCommand.doCall(CatalogBaseCommand.java:138) > at > org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71) > at > org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21445) camel-core - Vault with secret refresh should be disabled as default
[ https://issues.apache.org/jira/browse/CAMEL-21445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21445. -- Resolution: Fixed > camel-core - Vault with secret refresh should be disabled as default > > > Key: CAMEL-21445 > URL: https://issues.apache.org/jira/browse/CAMEL-21445 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-main >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > See chat > [https://camel.zulipchat.com/#narrow/channel/352237-camel-jbang/topic/export.20with.20vault] > > Change the default to false in the camel-main vault configuration. > Add note about this change in the 4.9 upgrade guide > To enable you just set > camel.vault.kubernetes.refreshEnabled=true > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21446) configmap/secret - default takes precedence
[
https://issues.apache.org/jira/browse/CAMEL-21446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21446:
-
Fix Version/s: 4.8.2
4.9.0
> configmap/secret - default takes precedence
> ---
>
> Key: CAMEL-21446
> URL: https://issues.apache.org/jira/browse/CAMEL-21446
> Project: Camel
> Issue Type: Bug
> Components: camel-kubernetes
>Affects Versions: 4.8.1
>Reporter: Filip Jalaksa
>Assignee: Marco Carletti
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
>
> Created a simple integration using Karavan
> {code:java}
> - rest:
> id: rest-d471
> post:
> - id: post-126a
> path: /injectionTest
> to: direct:injectionTest
> - route:
> id: route-a292
> from:
> id: from-b12a
> uri: direct
> parameters:
> name: injectionTest
> steps:
> - to:
> id: to-bab9
> uri: kubernetes-config-maps
> parameters:
> namespace: default
> masterUrl: kubernetes.default.svc:443
> operation: listConfigMaps
> - marshal:
> id: marshal-55e5
> json:
> id: json-b0d1
> - log:
> id: log-d04e
> message: >-
> Printing test configmap without default
> {{configmap:secondmap/test}}
> - log:
> id: log-3396
> message: Printing test secret without default
> {{secret:secondsecret/test}}
> - log:
> id: log-f123
> message: >-
> Printing test configmap with default
> {{configmap:secondmap/test:default}}
> - log:
> id: log-f123
> message: >-
> Printing test secret with default
> {{configmap:secondsecret/test:default}} {code}
> Output in my testing minikube container:
> {code:java}
> 2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
> : Printing test configmap without default working
> 2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
> : Printing test secret without default mysecretvalue
> 2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
> : Printing test configmap with default default
> 2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
> : Printing test secret with default default {code}
> So when using the default in property placeholders it will take precedence
> even if given key is present.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21352) camel-smb - Based on camel-file to have many more features
[
https://issues.apache.org/jira/browse/CAMEL-21352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897925#comment-17897925
]
Otavio Rodolfo Piske commented on CAMEL-21352:
--
We already have it using WrappedFile and the consumer implements the
{color:#00}ScheduledBatchPollingConsumer (also used by
FileConsumer){color}, so *in theory* we have some common ground to work on
this. Maybe we could start by trying to make it extend the
`{color:#00}GenericFileConsumer{color}` and that would cover a lot of what
we need.
> camel-smb - Based on camel-file to have many more features
> --
>
> Key: CAMEL-21352
> URL: https://issues.apache.org/jira/browse/CAMEL-21352
> Project: Camel
> Issue Type: Improvement
> Components: camel-smb
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: Future
>
>
> Maybe we could let camel-smb extend camel-file (like camel-ftp / camel-jsch)
> and then have a lot more file related features out of the box.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21352) camel-smb - Based on camel-file to have many more features
[
https://issues.apache.org/jira/browse/CAMEL-21352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897925#comment-17897925
]
Otavio Rodolfo Piske edited comment on CAMEL-21352 at 11/13/24 1:40 PM:
We already have it using WrappedFile and the consumer implements the
{color:#00}ScheduledBatchPollingConsumer (also used by
FileConsumer){color}, so *in theory,* we have some common ground to work on
this. Maybe we could start by trying to make it extend the
`{color:#00}GenericFileConsumer{color}` and that would cover a lot of what
we need.
was (Author: orpiske):
We already have it using WrappedFile and the consumer implements the
{color:#00}ScheduledBatchPollingConsumer (also used by
FileConsumer){color}, so *in theory* we have some common ground to work on
this. Maybe we could start by trying to make it extend the
`{color:#00}GenericFileConsumer{color}` and that would cover a lot of what
we need.
> camel-smb - Based on camel-file to have many more features
> --
>
> Key: CAMEL-21352
> URL: https://issues.apache.org/jira/browse/CAMEL-21352
> Project: Camel
> Issue Type: Improvement
> Components: camel-smb
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: Future
>
>
> Maybe we could let camel-smb extend camel-file (like camel-ftp / camel-jsch)
> and then have a lot more file related features out of the box.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21445) camel-core - Vault with secret refresh should be disabled as default
Claus Ibsen created CAMEL-21445: --- Summary: camel-core - Vault with secret refresh should be disabled as default Key: CAMEL-21445 URL: https://issues.apache.org/jira/browse/CAMEL-21445 Project: Camel Issue Type: Improvement Components: camel-core, camel-main Reporter: Claus Ibsen Fix For: 4.9.0 See chat [https://camel.zulipchat.com/#narrow/channel/352237-camel-jbang/topic/export.20with.20vault] Change the default to false in the camel-main vault configuration. Add note about this change in the 4.9 upgrade guide To enable you just set camel.vault.kubernetes.refreshEnabled=true -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21436) camel-jbang - Export beans with secret function should work even if k8s is not configured
[
https://issues.apache.org/jira/browse/CAMEL-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21436.
-
Resolution: Fixed
> camel-jbang - Export beans with secret function should work even if k8s is
> not configured
> -
>
> Key: CAMEL-21436
> URL: https://issues.apache.org/jira/browse/CAMEL-21436
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.8.2, 4.9.0
>
>
> A bean such as a database driver
> {code:java}
> - beans:
> - name: DemoDatabase
> type: "#class:org.apache.commons.dbcp2.BasicDataSource"
> properties:
> username: "{{secret:demo/username}}"
> password: "{{secret:demo/password}}"
> url: "{{secret:demo/url}}"
> driverClassName: org.postgresql.Driver
> {code}
>
> Can fail during export because camel-kubernetes fail with
> java.lang.IllegalArgumentException: Secrets must be configured on Kubernetes
> vault configuration
> at
> org.apache.camel.component.kubernetes.secrets.vault.SecretsReloadTriggerTask.doStart(SecretsReloadTriggerTask.java:96)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21445) camel-core - Vault with secret refresh should be disabled as default
[ https://issues.apache.org/jira/browse/CAMEL-21445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21445: Assignee: Andrea Cosentino > camel-core - Vault with secret refresh should be disabled as default > > > Key: CAMEL-21445 > URL: https://issues.apache.org/jira/browse/CAMEL-21445 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-main >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > See chat > [https://camel.zulipchat.com/#narrow/channel/352237-camel-jbang/topic/export.20with.20vault] > > Change the default to false in the camel-main vault configuration. > Add note about this change in the 4.9 upgrade guide > To enable you just set > camel.vault.kubernetes.refreshEnabled=true > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21428) NullPointerException in createTempFileName due to tempName being null in Camel 4.8.0
[
https://issues.apache.org/jira/browse/CAMEL-21428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897870#comment-17897870
]
Claus Ibsen commented on CAMEL-21428:
-
Can you provide more details ?
> NullPointerException in createTempFileName due to tempName being null in
> Camel 4.8.0
>
>
> Key: CAMEL-21428
> URL: https://issues.apache.org/jira/browse/CAMEL-21428
> Project: Camel
> Issue Type: Bug
> Components: camel-file
>Affects Versions: 4.8.1
>Reporter: Oystein Follo
>Priority: Minor
>
> We are experiencing a {{NullPointerException}} within the
> {{createTempFileName}} method. This error occurs when {{tempName}} is
> evaluated as {{{}null{}}}, and later in the code, a call to
> {{tempName.length()}} or {{tempName.lastIndexOf()}} results in an exception.
> This issue can disrupt the file processing flow.
> *Relevant Code Segment:*
> *File: camel-file/components/file/GenericFileProducer.java*
> {code:java}
> public String createTempFileName(Exchange exchange, String fileName) {
> String answer = fileName; String tempName;
> if (exchange.getIn().getHeader(FileConstants.FILE_NAME) == null)
> { exchange.getIn().setHeader(FileConstants.FILE_NAME,
> FileUtil.stripPath(fileName)); tempName =
> endpoint.getTempFileName().evaluate(exchange, String.class);
> exchange.getIn().removeHeader(FileConstants.FILE_NAME); }
> else {
> tempName = endpoint.getTempFileName().evaluate(exchange,
> String.class);
> } int pos = Math.max(answer.lastIndexOf('/'), answer.lastIndexOf("
> "));
> if (pos == -1) {
> answer = tempName;
> } else {
> final String prefix = answer.substring(0, pos + 1);
> StringBuilder sb = new StringBuilder(tempName.length() +
> prefix.length() + 1);
> sb.append(prefix);
> sb.append(tempName);
> answer = sb.toString();
> } if (endpoint.getConfiguration().needToNormalize()) {
> answer = normalizePath(answer);
> } answer = FileUtil.compactPath(answer, getFileSeparator()); return
> answer;
> }
> {code}
> *Issue Location:*
> The issue occurs in the line:
> {code:java}
> StringBuilder sb = new StringBuilder(tempName.length() + prefix.length() + 1);
> {code}
> If {{tempName}} is {{{}null{}}}, calling {{tempName.length()}} or
> {{tempName.lastIndexOf()}} will result in a {{{}NullPointerException{}}}.
> *Steps to Reproduce:*
> # Call {{createTempFileName}} with an {{Exchange}} object where
> {{endpoint.getTempFileName().evaluate(exchange, String.class)}} may return
> {{{}null{}}}.
> # Observe that if {{tempName}} is {{{}null{}}}, a {{NullPointerException}}
> occurs.
> *Expected Behavior:*
> The method should handle the case where {{tempName}} may be {{{}null{}}}. If
> {{tempName}} is {{{}null{}}}, a default value should be used or a check
> should be added to avoid invoking methods on a {{null}} object.
> *Actual Behavior:*
> A {{NullPointerException}} is thrown when {{tempName}} is {{{}null{}}}, which
> may interrupt the file creation or processing flow.
> *Suggested Solution:*
> Add a null check for {{tempName}} after it is assigned. For example:
> {code:java}
> if (tempName == null) {
> tempName = "defaultTempName"; // or handle appropriately for your use case
> }
> {code}
>
> Alternatively, consider handling {{null}} scenarios with a fallback or
> error-handling mechanism to avoid this exception.
> *Impact:*
> This issue disrupts file processing, potentially causing failures in
> downstream applications depending on file operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21435) Commons-pool2: When Camel Netty configured with producerPoolMaxTotal=1 and retry, the application hangs
[
https://issues.apache.org/jira/browse/CAMEL-21435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897869#comment-17897869
]
Claus Ibsen commented on CAMEL-21435:
-
I would suggest you try to run with TRACE logging at
org.apache.camel.component.netty
And then capture the logging activity what happens when you have the IO network
error and how camel-netty is invalidating the pooled object and creating a
fresh new.
This can maybe give hints if there is something that can be improved when the
pool size is 1 vs having space in the pool.
> Commons-pool2: When Camel Netty configured with producerPoolMaxTotal=1 and
> retry, the application hangs
> ---
>
> Key: CAMEL-21435
> URL: https://issues.apache.org/jira/browse/CAMEL-21435
> Project: Camel
> Issue Type: Bug
> Components: camel-netty
>Reporter: Dmitrii Kriukov
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.9.0
>
>
> Retry on the onException() clause seems to be impossible for
> producerPoolMaxTotal=1 (leads to call of
> GenericObjectPoolConfig.setMaxTotal())
> This causes infinite hanging in case of network IO exceptions.
> Netty attempts to utilize a new connection when the old one is still
> unreleased.
> It boils down to method
> org.apache.commons.pool2.impl.GenericObjectPool::borrowObject(Duration
> borrowMaxWaitDuration) throws Exception {}
> When producerPoolBlockWhenExhausted = true (the default value), the
> application hangs.
> When producerPoolBlockWhenExhausted = false, I get an exception
> 2024-11-11 13:41:44 ERROR [com.opt.obp.ser.ada.cam.Logger] (Camel Thread #2 -
> NettyClientTCPWorker) <> Exception occurred:
> java.util.NoSuchElementException: Pool exhausted
> So, either way it's impossible to serve
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21436) camel-jbang - Export beans with secret function should work even if k8s is not configured
[
https://issues.apache.org/jira/browse/CAMEL-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-21436:
---
Assignee: Claus Ibsen
> camel-jbang - Export beans with secret function should work even if k8s is
> not configured
> -
>
> Key: CAMEL-21436
> URL: https://issues.apache.org/jira/browse/CAMEL-21436
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.8.2, 4.9.0
>
>
> A bean such as a database driver
> {code:java}
> - beans:
> - name: DemoDatabase
> type: "#class:org.apache.commons.dbcp2.BasicDataSource"
> properties:
> username: "{{secret:demo/username}}"
> password: "{{secret:demo/password}}"
> url: "{{secret:demo/url}}"
> driverClassName: org.postgresql.Driver
> {code}
>
> Can fail during export because camel-kubernetes fail with
> java.lang.IllegalArgumentException: Secrets must be configured on Kubernetes
> vault configuration
> at
> org.apache.camel.component.kubernetes.secrets.vault.SecretsReloadTriggerTask.doStart(SecretsReloadTriggerTask.java:96)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21439) camel-etcd3: all tests are broken
[
https://issues.apache.org/jira/browse/CAMEL-21439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897858#comment-17897858
]
Claus Ibsen commented on CAMEL-21439:
-
No its not really in use, its preview level for a long time
> camel-etcd3: all tests are broken
> -
>
> Key: CAMEL-21439
> URL: https://issues.apache.org/jira/browse/CAMEL-21439
> Project: Camel
> Issue Type: Test
> Components: camel-etcd3
>Affects Versions: 4.9.0
>Reporter: Otavio Rodolfo Piske
>Priority: Minor
>
> Something has broken etcd3 very badly and tests are not working at all. This
> could indicate a serious problem with the component.
> Running the tests causes these messages to be printed:
> {noformat}
> Nov 11, 2024 10:29:41 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:42 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:44 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:47 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:51 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:59 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:30:09 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:30:25 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> {noformat}
> And the logs:
> {code:java}
> 2024-11-12 10:01:46,517 [ault-executor-0] WARN AbstractNameResolver
> - Error while getting list of servers
> java.lang.IllegalStateException: Not called from the SynchronizationContext
> at
> com.google.common.base.Preconditions.checkState(Preconditions.java:513)
> ~[guava-33.3.1-jre.jar:?]
> at
> io.grpc.SynchronizationContext.throwIfNotInThisSynchronizationContext(SynchronizationContext.java:134)
> ~[grpc-api-1.68.1.jar:1.68.1]
> at
> io.grpc.internal.ManagedChannelImpl$NameResolverListener.onResult2(ManagedChannelImpl.java:1686)
> ~[grpc-core-1.68.1.jar:1.68.1]
> at
> io.grpc.internal.RetryingNameResolver$RetryingListener.onResult2(RetryingNameResolver.java:107)
> ~[grpc-core-1.68.1.jar:1.68.1]
> at io.grpc.NameResolver$Listener2.onAddresses(NameResolver.java:228)
> ~[grpc-api-1.68.1.jar:1.68.1]
> at
> io.etcd.jetcd.resolver.AbstractNameResolver.doResolve(AbstractNameResolver.java:124)
> ~[jetcd-core-0.8.3.jar:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21439) camel-etcd3: all tests are broken
[
https://issues.apache.org/jira/browse/CAMEL-21439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897859#comment-17897859
]
Claus Ibsen commented on CAMEL-21439:
-
Camel is a very big project and from time to time then stuff needs to go for
the project to be maintainable
> camel-etcd3: all tests are broken
> -
>
> Key: CAMEL-21439
> URL: https://issues.apache.org/jira/browse/CAMEL-21439
> Project: Camel
> Issue Type: Test
> Components: camel-etcd3
>Affects Versions: 4.9.0
>Reporter: Otavio Rodolfo Piske
>Priority: Minor
>
> Something has broken etcd3 very badly and tests are not working at all. This
> could indicate a serious problem with the component.
> Running the tests causes these messages to be printed:
> {noformat}
> Nov 11, 2024 10:29:41 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:42 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:44 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:47 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:51 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:29:59 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:30:09 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> Nov 11, 2024 10:30:25 AM
> io.grpc.internal.ManagedChannelImpl$NameResolverListener
> handleErrorInSyncContext
> WARNING: [Channel<1>: (ip:///localhost:36757)] Failed to resolve name.
> status=Status{code=NOT_FOUND, description=null, cause=null}
> {noformat}
> And the logs:
> {code:java}
> 2024-11-12 10:01:46,517 [ault-executor-0] WARN AbstractNameResolver
> - Error while getting list of servers
> java.lang.IllegalStateException: Not called from the SynchronizationContext
> at
> com.google.common.base.Preconditions.checkState(Preconditions.java:513)
> ~[guava-33.3.1-jre.jar:?]
> at
> io.grpc.SynchronizationContext.throwIfNotInThisSynchronizationContext(SynchronizationContext.java:134)
> ~[grpc-api-1.68.1.jar:1.68.1]
> at
> io.grpc.internal.ManagedChannelImpl$NameResolverListener.onResult2(ManagedChannelImpl.java:1686)
> ~[grpc-core-1.68.1.jar:1.68.1]
> at
> io.grpc.internal.RetryingNameResolver$RetryingListener.onResult2(RetryingNameResolver.java:107)
> ~[grpc-core-1.68.1.jar:1.68.1]
> at io.grpc.NameResolver$Listener2.onAddresses(NameResolver.java:228)
> ~[grpc-api-1.68.1.jar:1.68.1]
> at
> io.etcd.jetcd.resolver.AbstractNameResolver.doResolve(AbstractNameResolver.java:124)
> ~[jetcd-core-0.8.3.jar:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21446) configmap/secret - default takes precedence
[
https://issues.apache.org/jira/browse/CAMEL-21446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Jalaksa updated CAMEL-21446:
--
Description:
Created a simple integration using Karavan
{code:java}
- rest:
id: rest-d471
post:
- id: post-126a
path: /injectionTest
to: direct:injectionTest
- route:
id: route-a292
from:
id: from-b12a
uri: direct
parameters:
name: injectionTest
steps:
- to:
id: to-bab9
uri: kubernetes-config-maps
parameters:
namespace: default
masterUrl: kubernetes.default.svc:443
operation: listConfigMaps
- marshal:
id: marshal-55e5
json:
id: json-b0d1
- log:
id: log-d04e
message: >-
Printing test configmap without default
{{configmap:secondmap/test}}
- log:
id: log-3396
message: Printing test secret without default
{{secret:secondsecret/test}}
- log:
id: log-f123
message: >-
Printing test configmap with default
{{configmap:secondmap/test:default}}
- log:
id: log-f123
message: >-
Printing test secret with default
{{configmap:secondsecret/test:default}} {code}
Output in my testing minikube container:
{code:java}
2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
: Printing test configmap without default working
2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
: Printing test secret without default mysecretvalue
2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
: Printing test configmap with default default
2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
: Printing test secret with default default {code}
was:
Created a simple integration using Karavan
- rest:
id: rest-d471
post:
- id: post-126a
path: /injectionTest
to: direct:injectionTest
- route:
id: route-a292
from:
id: from-b12a
uri: direct
parameters:
name: injectionTest
steps:
- to:
id: to-bab9
uri: kubernetes-config-maps
parameters:
namespace: default
masterUrl: kubernetes.default.svc:443
operation: listConfigMaps
- marshal:
id: marshal-55e5
json:
id: json-b0d1
- log:
id: log-d04e
message: >-
Printing test configmap without default
\{{configmap:secondmap/test}}
- log:
id: log-3396
message: Printing test secret without default
\{{secret:secondsecret/test}}
- log:
id: log-f123
message: >-
Printing test configmap with default
\{{configmap:secondmap/test:default}}
- log:
id: log-f123
message: >-
Printing test secret with default
\{{configmap:secondsecret/test:default}}
When using the default value in the property placeholders, default is returned
even if the key is present.
Output in my testing minikube container:
{code:java}
2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
: Printing test configmap without default working
2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
: Printing test secret without default mysecretvalue
2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
: Printing test configmap with default default
2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
: Printing test secret with default default {code}
> configmap/secret - default takes precedence
> ---
>
> Key: CAMEL-21446
> URL: https://issues.apache.org/jira/browse/CAMEL-21446
> Project: Camel
> Issue Type: Bug
> Components: camel-kubernetes
>Affects Versions: 4.8.1
>Reporter: Filip Jalaksa
>Priority: Minor
>
> Created a simple integration using Karavan
> {code:java}
> - rest:
> id: rest-d471
> post:
> - id: post-126a
> path: /injectionTest
> to: direct:injectionTest
> - route:
> id: route-a292
> from:
> id: from-b12a
> uri: direct
> parameters:
> name: injectionTest
> steps:
> - to:
> id: to-bab9
> uri: kubernetes-config-maps
> parameters:
> namespace: defau
[jira] [Commented] (CAMEL-21446) configmap/secret - default takes precedence
[
https://issues.apache.org/jira/browse/CAMEL-21446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897895#comment-17897895
]
Andrea Cosentino commented on CAMEL-21446:
--
[~mcarlett] already has a fix
> configmap/secret - default takes precedence
> ---
>
> Key: CAMEL-21446
> URL: https://issues.apache.org/jira/browse/CAMEL-21446
> Project: Camel
> Issue Type: Bug
> Components: camel-kubernetes
>Affects Versions: 4.8.1
>Reporter: Filip Jalaksa
>Assignee: Marco Carletti
>Priority: Minor
>
> Created a simple integration using Karavan
> {code:java}
> - rest:
> id: rest-d471
> post:
> - id: post-126a
> path: /injectionTest
> to: direct:injectionTest
> - route:
> id: route-a292
> from:
> id: from-b12a
> uri: direct
> parameters:
> name: injectionTest
> steps:
> - to:
> id: to-bab9
> uri: kubernetes-config-maps
> parameters:
> namespace: default
> masterUrl: kubernetes.default.svc:443
> operation: listConfigMaps
> - marshal:
> id: marshal-55e5
> json:
> id: json-b0d1
> - log:
> id: log-d04e
> message: >-
> Printing test configmap without default
> {{configmap:secondmap/test}}
> - log:
> id: log-3396
> message: Printing test secret without default
> {{secret:secondsecret/test}}
> - log:
> id: log-f123
> message: >-
> Printing test configmap with default
> {{configmap:secondmap/test:default}}
> - log:
> id: log-f123
> message: >-
> Printing test secret with default
> {{configmap:secondsecret/test:default}} {code}
> Output in my testing minikube container:
> {code:java}
> 2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
> : Printing test configmap without default working
> 2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
> : Printing test secret without default mysecretvalue
> 2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
> : Printing test configmap with default default
> 2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
> : Printing test secret with default default {code}
> So when using the default in property placeholders it will take precedence
> even if given key is present.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21446) configmap/secret - default takes precedence
[
https://issues.apache.org/jira/browse/CAMEL-21446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21446.
-
Resolution: Fixed
> configmap/secret - default takes precedence
> ---
>
> Key: CAMEL-21446
> URL: https://issues.apache.org/jira/browse/CAMEL-21446
> Project: Camel
> Issue Type: Bug
> Components: camel-kubernetes
>Affects Versions: 4.8.1
>Reporter: Filip Jalaksa
>Assignee: Marco Carletti
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
>
> Created a simple integration using Karavan
> {code:java}
> - rest:
> id: rest-d471
> post:
> - id: post-126a
> path: /injectionTest
> to: direct:injectionTest
> - route:
> id: route-a292
> from:
> id: from-b12a
> uri: direct
> parameters:
> name: injectionTest
> steps:
> - to:
> id: to-bab9
> uri: kubernetes-config-maps
> parameters:
> namespace: default
> masterUrl: kubernetes.default.svc:443
> operation: listConfigMaps
> - marshal:
> id: marshal-55e5
> json:
> id: json-b0d1
> - log:
> id: log-d04e
> message: >-
> Printing test configmap without default
> {{configmap:secondmap/test}}
> - log:
> id: log-3396
> message: Printing test secret without default
> {{secret:secondsecret/test}}
> - log:
> id: log-f123
> message: >-
> Printing test configmap with default
> {{configmap:secondmap/test:default}}
> - log:
> id: log-f123
> message: >-
> Printing test secret with default
> {{configmap:secondsecret/test:default}} {code}
> Output in my testing minikube container:
> {code:java}
> 2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
> : Printing test configmap without default working
> 2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
> : Printing test secret without default mysecretvalue
> 2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
> : Printing test configmap with default default
> 2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
> : Printing test secret with default default {code}
> So when using the default in property placeholders it will take precedence
> even if given key is present.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21448) camel-etcd3: deprecate component etcd3
[ https://issues.apache.org/jira/browse/CAMEL-21448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21448: Fix Version/s: 4.9.0 > camel-etcd3: deprecate component etcd3 > -- > > Key: CAMEL-21448 > URL: https://issues.apache.org/jira/browse/CAMEL-21448 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.9.0 > > > This component seems largely unmaintained and suffering from problems with > testing (CAMEL-21439). As all the tests are disabled and apparently there's > no interest on it, we should deprecate it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21448) camel-etcd3: deprecate component etcd3
Otavio Rodolfo Piske created CAMEL-21448: Summary: camel-etcd3: deprecate component etcd3 Key: CAMEL-21448 URL: https://issues.apache.org/jira/browse/CAMEL-21448 Project: Camel Issue Type: Task Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske This component seems largely unmaintained and suffering from problems with testing (CAMEL-21439). As all the tests are disabled and apparently there's no interest on it, we should deprecate it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21415) [camel-micrometer-prometheus] Make endpoint metrics configurable
[ https://issues.apache.org/jira/browse/CAMEL-21415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21415: Fix Version/s: 4.9.0 (was: 4.10.0) > [camel-micrometer-prometheus] Make endpoint metrics configurable > > > Key: CAMEL-21415 > URL: https://issues.apache.org/jira/browse/CAMEL-21415 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.x >Reporter: Pasquale Congiusti >Assignee: Pasquale Congiusti >Priority: Minor > Fix For: 4.9.0 > > > The configuration for Prometheus endpoint is hardcoded: > https://github.com/apache/camel/blob/c7385e3e0542b8b754691d5015936c040c1cdf8d/components/camel-micrometer-prometheus/src/main/java/org/apache/camel/component/micrometer/prometheus/MicrometerPrometheus.java#L390 > We should add a configuration on the component to let the user configure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21442) camel-jbang - export is no more working when a previous run with an xsl file on the classpath occured
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898141#comment-17898141
]
Claus Ibsen commented on CAMEL-21442:
-
This command looks a bit wrong - as you have both * and *.xsl as the args to
select the files to run. Also local-kamelet-dir is not intended to be current
dir, but some shared dir.
{code:java}
jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run * --dev
--logging-level=info --local-kamelet-dir=. *.xsl {code}
> camel-jbang - export is no more working when a previous run with an xsl file
> on the classpath occured
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
> 'test-with-xsl.camel.yaml'
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run * --dev
> --logging-level=info --local-kamelet-dir=. *.xsl
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
> successfully and then calling mvn quarkus:dev is working fine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21442) camel-jbang - export is no more working when a previous run with an xsl file on the classpath occured
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898142#comment-17898142
]
Claus Ibsen commented on CAMEL-21442:
-
Can you attach the files you use for this, it would be much easier to reproduce
instead of we have to make up a project on our own which does not match what
you attempt to do
> camel-jbang - export is no more working when a previous run with an xsl file
> on the classpath occured
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
> 'test-with-xsl.camel.yaml'
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run * --dev
> --logging-level=info --local-kamelet-dir=. *.xsl
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
> successfully and then calling mvn quarkus:dev is working fine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21402) Enhance Camel's testing capabilities of MockEndpoint with Expressions
[ https://issues.apache.org/jira/browse/CAMEL-21402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21402: Priority: Minor (was: Major) > Enhance Camel's testing capabilities of MockEndpoint with Expressions > - > > Key: CAMEL-21402 > URL: https://issues.apache.org/jira/browse/CAMEL-21402 > Project: Camel > Issue Type: Improvement > Components: camel-mock >Reporter: Dmitrii Kriukov >Assignee: Dmitrii Kriukov >Priority: Minor > Fix For: 4.9.0 > > > My test case was: partially random value in an added header. It's difficult > to test the exact value with existing API, so I was thinking about verifying > against a regex. This option requires usage of Expressions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21418) camel-rest - Client request validation and multiple values in Accept header
[
https://issues.apache.org/jira/browse/CAMEL-21418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898143#comment-17898143
]
Claus Ibsen commented on CAMEL-21418:
-
What runtime do you use to run this such as spring boot or quarkus, and do you
use rest-dsl. In other words can you tell a bit more what you do
> camel-rest - Client request validation and multiple values in Accept header
> ---
>
> Key: CAMEL-21418
> URL: https://issues.apache.org/jira/browse/CAMEL-21418
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.8.1
>Reporter: Olivier Jacquemart
>Priority: Minor
>
> I have a problem regarding a rest route and a client sending multiple values
> in the Accept header. The route has the client request validation enabled.
> {code:java}
> # succeeds
> $ curl -v -H "Accept: application/json" localhost:8080/api/hello
> {"message":"hello world"}
> # fails
> $ curl -v -H "Accept: application/xml, application/json"
> localhost:8080/api/hello
> Response status is https://http.cat/406
> {code}
> After a quick debug, I ended up in the [RestUtil
> |https://github.com/apache/camel/blob/main/core/camel-support/src/main/java/org/apache/camel/support/http/RestUtil.java]
> class that returns false by default. It considers the accept header like
> invalid then and gives the 406.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21410) Replace usage of STRICT_VALIDATOR with UTF_VALIDATOR
[ https://issues.apache.org/jira/browse/CAMEL-21410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21410. - Resolution: Fixed > Replace usage of STRICT_VALIDATOR with UTF_VALIDATOR > > > Key: CAMEL-21410 > URL: https://issues.apache.org/jira/browse/CAMEL-21410 > Project: Camel > Issue Type: Task > Components: camel-jackson >Reporter: Thomas Cunningham >Assignee: Thomas Cunningham >Priority: Major > Fix For: 4.9.0 > > > [~jamesnetherton] pointed out that UTF_VALIDATOR is the default validation > mode for Avro > [https://github.com/apache/avro/blob/release-1.12.0/lang/java/avro/src/main/java/org/apache/avro/Schema.java#L1433-L1435] > > and that STRICT_VALIDATOR was more restrictive. Change our use of > NameValidator to use UTF_VALIDATOR rather than STRICT_VALIDATOR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21415) [camel-micrometer-prometheus] Make endpoint metrics configurable
[ https://issues.apache.org/jira/browse/CAMEL-21415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21415. - Resolution: Fixed > [camel-micrometer-prometheus] Make endpoint metrics configurable > > > Key: CAMEL-21415 > URL: https://issues.apache.org/jira/browse/CAMEL-21415 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.x >Reporter: Pasquale Congiusti >Assignee: Pasquale Congiusti >Priority: Minor > Fix For: 4.9.0 > > > The configuration for Prometheus endpoint is hardcoded: > https://github.com/apache/camel/blob/c7385e3e0542b8b754691d5015936c040c1cdf8d/components/camel-micrometer-prometheus/src/main/java/org/apache/camel/component/micrometer/prometheus/MicrometerPrometheus.java#L390 > We should add a configuration on the component to let the user configure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21410) Replace usage of STRICT_VALIDATOR with UTF_VALIDATOR
[ https://issues.apache.org/jira/browse/CAMEL-21410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21410: Fix Version/s: 4.9.0 > Replace usage of STRICT_VALIDATOR with UTF_VALIDATOR > > > Key: CAMEL-21410 > URL: https://issues.apache.org/jira/browse/CAMEL-21410 > Project: Camel > Issue Type: Task > Components: camel-jackson >Reporter: Thomas Cunningham >Assignee: Thomas Cunningham >Priority: Major > Fix For: 4.9.0 > > > [~jamesnetherton] pointed out that UTF_VALIDATOR is the default validation > mode for Avro > [https://github.com/apache/avro/blob/release-1.12.0/lang/java/avro/src/main/java/org/apache/avro/Schema.java#L1433-L1435] > > and that STRICT_VALIDATOR was more restrictive. Change our use of > NameValidator to use UTF_VALIDATOR rather than STRICT_VALIDATOR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21442) camel-jbang - export is no more working when a previous run with an xsl file on the classpath occured
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-21442:
Description:
it is a regression introduced in Camel 4.8.1, it is working fine with Camel
4.8.0
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
'test-with-xsl.camel.yaml'
* create an empty dummy.xsl file
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=. *.xsl
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
--runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
{noformat}
Reusing existing run data
Exporting as Quarkus project to: .
java.nio.file.NoSuchFileException:
.camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
at
java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
at
java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
at java.base/java.nio.file.Files.copy(Files.java:1304)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
at
org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
at
org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
at
org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
at
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
at
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
at picocli.CommandLine.access$1500(CommandLine.java:148)
at
picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
at
picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
at picocli.CommandLine.execute(CommandLine.java:2174)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
at main.CamelJBang.main(CamelJBang.java:36)
{noformat}
Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
--runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting
successfully and then calling mvn quarkus:dev is working fine
was:
it is a regression introduced in Camel 4.8.1, it is working fine with Camel
4.8.0
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
'test-with-xsl.camel.yaml'
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run * --dev
--logging-level=info --local-kamelet-dir=. *.xsl
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
--runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
{noformat}
Reusing existing run data
Exporting as Quarkus project to: .
java.nio.file.NoSuchFileException:
.camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
at
java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
at
java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
at java.base/java.nio.file.Files.copy(Files.java:1304)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
at
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
at
org.apache.camel.dsl.jbang.core.commands.
[jira] [Commented] (CAMEL-21442) camel-jbang - export is no more working when a previous run with an xsl file on the classpath occured
[
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898163#comment-17898163
]
Aurélien Pupier commented on CAMEL-21442:
-
About kamelet-dir, hitting same kind of problem that the project structure
needs to be reinvented. Usually users are creating kamelet at the same level
than Camel routes. Also the Camel Jbang init is not giving any guidance and by
default creating at the same level. So providing --kamelet-dir to current dir
is the way to have it working by default.
using `jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
*.xsl` is giving the same result. The *.xsl is used to select additional files
to add the classpath, not to select files to run.
Added the project after the 3 steps:
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
'test-with-xsl.camel.yaml'
* create an empty dummy.xsl file
* jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=. *.xsl
> camel-jbang - export is no more working when a previous run with an xsl file
> on the classpath occured
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Aurélien Pupier
>Priority: Minor
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init
> 'test-with-xsl.camel.yaml'
> * create an empty dummy.xsl file
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run
> test-with-xsl.camel.yaml --dev --logging-level=info --local-kamelet-dir=.
> *.xsl
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException:
> .camel-jbang/work/src/main/resources/kamelets/test-with-xsl.camel.yaml
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export
> --runtime=quarkus --gav=com.acme:myproj
