[jira] [Commented] (CAMEL-21302) camel-opentelemetry context leak with direct async producer
[
https://issues.apache.org/jira/browse/CAMEL-21302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892074#comment-17892074
]
John Poth commented on CAMEL-21302:
---
Yeah those are just warnings. We do check if there are any leaks at the end of
each tests.
> camel-opentelemetry context leak with direct async producer
> ---
>
> Key: CAMEL-21302
> URL: https://issues.apache.org/jira/browse/CAMEL-21302
> Project: Camel
> Issue Type: Bug
> Components: camel-opentelemetry
>Reporter: John Poth
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 4.4.5, 4.8.2, 4.9.0
>
>
> There seems to be a Otel context leak when using a CXF producer in async
> mode. This causes different requests to have the same _traceId._ As a
> workaround, setting _synchronous=true_ on the CXF producer resolves the
> issue. Here's a reproducer:
> {code:java}
> @Override
> protected RoutesBuilder createRouteBuilder() {
> return new RouteBuilder() {
> @Override
> public void configure() {
> from("direct:start").routeId("myRoute")
> .to("direct:send")
> .end();
> from("direct:send")
> .log("message")
> .to("cxfrs:http://localhost:"; + port1
> + "/rest/helloservice/sayHello?synchronous=false");
> // setting to 'true' resolves the issue
> restConfiguration()
> .port(port1);
> rest("/rest/helloservice")
> .post("/sayHello").routeId("rest-GET-say-hi")
> .to("direct:sayHi");
> from("direct:sayHi")
> .routeId("mock-GET-say-hi")
> .log("example")
> .to("mock:end");
> }};
> {code}
>
> I've added the complete unit here:
> https://github.com/apache/camel/blob/7d83a62b8e442dc9ac6fd79b153192add940301e/components/camel-opentelemetry/src/test/java/org/apache/camel/opentelemetry/AsyncCxfTest.java
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21330) Camel-AWS-Secrets-Manager: Support Properties Function with Localstack
[ https://issues.apache.org/jira/browse/CAMEL-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21330: - Fix Version/s: 4.9.0 (was: 4.x) > Camel-AWS-Secrets-Manager: Support Properties Function with Localstack > -- > > Key: CAMEL-21330 > URL: https://issues.apache.org/jira/browse/CAMEL-21330 > Project: Camel > Issue Type: New Feature >Reporter: Lukas Lowinger >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > > To make Localstack work we need to set correct *endpointOverride* which is > done in the [common aws > client|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/client/impl/SecretsManagerClientStandardImpl.java#L90] > used in Camel. The problem is > [PropertiesFunction|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/SecretsManagerPropertiesFunction.java#L138] > doesn't provide such option. > Just for reference, here is > [code|https://github.com/apache/camel-quarkus/blob/main/integration-tests-support/aws2/src/test/java/org/apache/camel/quarkus/test/support/aws2/Aws2TestEnvContext.java#L185] > which sets it in Camel Quarkus project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21326) camel-jbang - Kubernetes run --verbose
[ https://issues.apache.org/jira/browse/CAMEL-21326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved CAMEL-21326. Resolution: Fixed Done > camel-jbang - Kubernetes run --verbose > -- > > Key: CAMEL-21326 > URL: https://issues.apache.org/jira/browse/CAMEL-21326 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Thomas Diesler >Priority: Minor > Fix For: 4.9.0 > > > When you run with kubernetes then the run command may take some time to > export, build and run and whatelse happens. On a slow box it may take 2 mins > to build and deploy and image due to downloading everything scratch from the > internet. > We should have a --verbose flag that details more what happens. > And then use that to see if any of that information should also be shown by > default without --verbose -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21374) camel-jbang - Export pipe with local kamelets seems to fail
[
https://issues.apache.org/jira/browse/CAMEL-21374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21374:
Fix Version/s: 4.8.2
4.9.0
> camel-jbang - Export pipe with local kamelets seems to fail
> ---
>
> Key: CAMEL-21374
> URL: https://issues.apache.org/jira/browse/CAMEL-21374
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1, 4.9.0
> Environment: I've set up the environment as follows:
> {code:java}
> camel version
> JBang version: 0.119.0
> Camel JBang version: 4.8.1 {code}
> And the *CamelJBang.java* in JBang's cache folder is defined with:
> {code:java}
> //JAVA 17+
> //REPOS
> central=https://repository.apache.org/content/repositories/orgapachecamel-1759/,https://repo1.maven.org/maven2,apache-snapshot=https://repository.apache.org/content/groups/snapshots/
> //DEPS org.apache.camel:camel-bom:${camel.jbang.version:4.8.1}@pom
> //DEPS org.apache.camel:camel-jbang-core:${camel.jbang.version:4.8.1}
> //DEPS
> org.apache.camel.kamelets:camel-kamelets:${camel-kamelets.version:4.8.0}
> {code}
> With the setup above, running the Pipe with the command in the description
> works well.
> However, the following command fails:
> {code:java}
> camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
> --gav=org.demo:mydemo:1.0.0 {code}
> The error thrown is:
> {code:java}
> Caused by: java.io.FileNotFoundException: Resource not found:
> classpath:kamelets,github:apache:camel-kamelets/kamelets/mytimer.kamelet.yaml
> {code}
> Find attached the source files used in the samples above
>Reporter: Bruno Meseguer
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: pipeexport.tar.gz
>
>
> Running a Pipe using local kamelets seems to work well using the command:
> {code:java}
> camel run * --local-kamelet-dir=./mykamelets/{code}
> Then, the export command seems not able to find the kamelets when running the
> following command:
> {code:java}
> camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
> --gav=org.demo:mydemo:1.0.0
> {code}
> Find attached the source files used to reproduce the problem.
>
> Read +{color:#0747a6}*Environment*{color}+ details (top) to read how to
> reproduce the problem.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21372) Camel JBang Export/Run are not working based on external camel-version setting
[
https://issues.apache.org/jira/browse/CAMEL-21372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21372:
Summary: Camel JBang Export/Run are not working based on external
camel-version setting (was: Camel JBang Export/Run are not working based on
camel-version setting)
> Camel JBang Export/Run are not working based on external camel-version setting
> --
>
> Key: CAMEL-21372
> URL: https://issues.apache.org/jira/browse/CAMEL-21372
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Salvatore Mongiardo
>Priority: Minor
> Attachments: jbang-export-issue.log
>
>
> The export/run command doesn't work when a "custom" _camel-version_ is set:
> camel config set
> deps=org.apache.camel.springboot:camel-timer-starter,camel:management,camel:cli-connector
> camel config set runtime=spring-boot
> camel config set gav=com.foo:acme:1.0-SNAPSHOT
> *camel config set camel-version=4.8.x-y*
> camel config set additional-properties=openshift-maven-plugin-version=1.17.0.y
> camel config set camel-spring-boot-version=4.8.0.y
> camel init test.yaml --directory=app
> Executing:
> {code:java}
> camel export app/test.yaml
> {code}
> This
> [exception|https://issues.redhat.com/secure/attachment/13285203/jbang-export-issue.log]
> is raised.
> The same happens with:
> {code:java}
> camel run app/test.yaml
> {code}
> If we unset the {_}camel-version{_}:
> *camel config unset camel-version*
> then
> {code:java}
> camel export app/test.yaml
> {code}
> works fine.
> I guess the issue could be the way how the method
> [Run.runCustomCamelVersion|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/Run.java#L838]
> is called, basically loosing every previous relationship with the
> [spec|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/CamelCommand.java#L40C5-L40C40]
> object
> h3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21361) fabric8 kubernetes-client fails to connect to openshift
[
https://issues.apache.org/jira/browse/CAMEL-21361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21361:
Affects Version/s: 4.8.0
> fabric8 kubernetes-client fails to connect to openshift
> ---
>
> Key: CAMEL-21361
> URL: https://issues.apache.org/jira/browse/CAMEL-21361
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0, 4.9.0
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs \
>--gav=examples:timer-log:1.0.0 \
>--image-registry image-registry.openshift-image-registry.svc:5000 \
>--trait container.imagePullPolicy=IfNotPresent \
>--cluster-type openshift \
>--runtime=quarkus
> {code}
> This happens with the latest
> [io.fabric8:kubernetes-client-6.13.4|https://github.com/apache/camel/blob/main/parent/pom.xml#L316]
> https://mvnrepository.com/artifact/io.fabric8/kubernetes-client/6.13.4
> {code}
> Run: kubectl get pod -l app.kubernetes.io/name=timer-log
> Exception in thread "main" java.util.ServiceConfigurationError:
> io.fabric8.kubernetes.api.model.KubernetesResource:
> io.fabric8.kubernetes.api.model.LimitRange not a subtype
> at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:593)
> at
> java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1244)
> at
> java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273)
> at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309)
> at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393)
> at java.base/java.util.Iterator.forEachRemaining(Iterator.java:132)
> at
> java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1845)
> at
> java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
> at
> java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:276)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:992)
> 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.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
> at
> io.fabric8.kubernetes.internal.KubernetesDeserializer$Mapping.registerClassesFromClassLoaders(KubernetesDeserializer.java:215)
> at
> io.fabric8.kubernetes.internal.KubernetesDeserializer.(KubernetesDeserializer.java:90)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization.getKubernetesDeserializer(KubernetesSerialization.java:153)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization.access$000(KubernetesSerialization.java:66)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization$1.deserializerInstance(KubernetesSerialization.java:105)
> at
> com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.deserializerInstance(DefaultDeserializationContext.java:245)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache.findDeserializerFromAnnotation(DeserializerCache.java:487)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer(DeserializerCache.java:382)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:317)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:284)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache.findValueDeserializer(DeserializerCache.java:174)
> at
> com.fasterxml.jackson.databind.DeserializationContext.findNonContextualValueDeserializer(DeserializationContext.java:659)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserial
[jira] [Updated] (CAMEL-21361) fabric8 kubernetes-client fails to connect to openshift
[
https://issues.apache.org/jira/browse/CAMEL-21361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21361:
Affects Version/s: (was: 4.9.0)
> fabric8 kubernetes-client fails to connect to openshift
> ---
>
> Key: CAMEL-21361
> URL: https://issues.apache.org/jira/browse/CAMEL-21361
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs \
>--gav=examples:timer-log:1.0.0 \
>--image-registry image-registry.openshift-image-registry.svc:5000 \
>--trait container.imagePullPolicy=IfNotPresent \
>--cluster-type openshift \
>--runtime=quarkus
> {code}
> This happens with the latest
> [io.fabric8:kubernetes-client-6.13.4|https://github.com/apache/camel/blob/main/parent/pom.xml#L316]
> https://mvnrepository.com/artifact/io.fabric8/kubernetes-client/6.13.4
> {code}
> Run: kubectl get pod -l app.kubernetes.io/name=timer-log
> Exception in thread "main" java.util.ServiceConfigurationError:
> io.fabric8.kubernetes.api.model.KubernetesResource:
> io.fabric8.kubernetes.api.model.LimitRange not a subtype
> at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:593)
> at
> java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1244)
> at
> java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273)
> at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309)
> at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393)
> at java.base/java.util.Iterator.forEachRemaining(Iterator.java:132)
> at
> java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1845)
> at
> java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
> at
> java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:276)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:992)
> 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.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
> at
> io.fabric8.kubernetes.internal.KubernetesDeserializer$Mapping.registerClassesFromClassLoaders(KubernetesDeserializer.java:215)
> at
> io.fabric8.kubernetes.internal.KubernetesDeserializer.(KubernetesDeserializer.java:90)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization.getKubernetesDeserializer(KubernetesSerialization.java:153)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization.access$000(KubernetesSerialization.java:66)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization$1.deserializerInstance(KubernetesSerialization.java:105)
> at
> com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.deserializerInstance(DefaultDeserializationContext.java:245)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache.findDeserializerFromAnnotation(DeserializerCache.java:487)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer(DeserializerCache.java:382)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:317)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:284)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache.findValueDeserializer(DeserializerCache.java:174)
> at
> com.fasterxml.jackson.databind.DeserializationContext.findNonContextualValueDeserializer(DeserializationContext.java:659)
> at
> com.fasterxml.jackson.databind.deser.BeanDese
[jira] [Updated] (CAMEL-21361) fabric8 kubernetes-client fails to connect to openshift
[
https://issues.apache.org/jira/browse/CAMEL-21361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21361:
Fix Version/s: 4.8.2
> fabric8 kubernetes-client fails to connect to openshift
> ---
>
> Key: CAMEL-21361
> URL: https://issues.apache.org/jira/browse/CAMEL-21361
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs \
>--gav=examples:timer-log:1.0.0 \
>--image-registry image-registry.openshift-image-registry.svc:5000 \
>--trait container.imagePullPolicy=IfNotPresent \
>--cluster-type openshift \
>--runtime=quarkus
> {code}
> This happens with the latest
> [io.fabric8:kubernetes-client-6.13.4|https://github.com/apache/camel/blob/main/parent/pom.xml#L316]
> https://mvnrepository.com/artifact/io.fabric8/kubernetes-client/6.13.4
> {code}
> Run: kubectl get pod -l app.kubernetes.io/name=timer-log
> Exception in thread "main" java.util.ServiceConfigurationError:
> io.fabric8.kubernetes.api.model.KubernetesResource:
> io.fabric8.kubernetes.api.model.LimitRange not a subtype
> at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:593)
> at
> java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1244)
> at
> java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273)
> at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309)
> at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393)
> at java.base/java.util.Iterator.forEachRemaining(Iterator.java:132)
> at
> java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1845)
> at
> java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
> at
> java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:276)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:992)
> 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.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
> at
> io.fabric8.kubernetes.internal.KubernetesDeserializer$Mapping.registerClassesFromClassLoaders(KubernetesDeserializer.java:215)
> at
> io.fabric8.kubernetes.internal.KubernetesDeserializer.(KubernetesDeserializer.java:90)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization.getKubernetesDeserializer(KubernetesSerialization.java:153)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization.access$000(KubernetesSerialization.java:66)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization$1.deserializerInstance(KubernetesSerialization.java:105)
> at
> com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.deserializerInstance(DefaultDeserializationContext.java:245)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache.findDeserializerFromAnnotation(DeserializerCache.java:487)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer(DeserializerCache.java:382)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:317)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:284)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache.findValueDeserializer(DeserializerCache.java:174)
> at
> com.fasterxml.jackson.databind.DeserializationContext.findNonContextualValueDeserializer(DeserializationContext.java:659)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializerBase.re
[jira] [Created] (CAMEL-21374) camel-jbang - Export pipe with local kamelets seems to fail
Bruno Meseguer created CAMEL-21374:
--
Summary: camel-jbang - Export pipe with local kamelets seems to
fail
Key: CAMEL-21374
URL: https://issues.apache.org/jira/browse/CAMEL-21374
Project: Camel
Issue Type: Bug
Components: camel-jbang
Affects Versions: 4.8.1, 4.9.0
Environment: I've set up the environment as follows:
{code:java}
camel version
JBang version: 0.119.0
Camel JBang version: 4.8.1 {code}
And the *CamelJBang.java* in JBang's cache folder is defined with:
{code:java}
//JAVA 17+
//REPOS
central=https://repository.apache.org/content/repositories/orgapachecamel-1759/,https://repo1.maven.org/maven2,apache-snapshot=https://repository.apache.org/content/groups/snapshots/
//DEPS org.apache.camel:camel-bom:${camel.jbang.version:4.8.1}@pom
//DEPS org.apache.camel:camel-jbang-core:${camel.jbang.version:4.8.1}
//DEPS org.apache.camel.kamelets:camel-kamelets:${camel-kamelets.version:4.8.0}
{code}
With the setup above, running the Pipe with the command in the description
works well.
However, the following command fails:
{code:java}
camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
--gav=org.demo:mydemo:1.0.0 {code}
The error thrown is:
{code:java}
Caused by: java.io.FileNotFoundException: Resource not found:
classpath:kamelets,github:apache:camel-kamelets/kamelets/mytimer.kamelet.yaml
{code}
Find attached the source files used in the samples above
Reporter: Bruno Meseguer
Attachments: pipeexport.tar.gz
Running a Pipe using local kamelets seems to work well using the command:
{code:java}
camel run * --local-kamelet-dir=./mykamelets/{code}
Then, the export command seems not able to find the kamelets when running the
following command:
{code:java}
camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
--gav=org.demo:mydemo:1.0.0
{code}
Find attached the source files used to reproduce the problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21013) camel-jbang - Run and deploy to OpenShift
[ https://issues.apache.org/jira/browse/CAMEL-21013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved CAMEL-21013. Resolution: Fixed Done > camel-jbang - Run and deploy to OpenShift > - > > Key: CAMEL-21013 > URL: https://issues.apache.org/jira/browse/CAMEL-21013 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21375) Camel-AWS-Secrets-Manager: Support Properties Function with Localstack in Spring Boot
Andrea Cosentino created CAMEL-21375: Summary: Camel-AWS-Secrets-Manager: Support Properties Function with Localstack in Spring Boot Key: CAMEL-21375 URL: https://issues.apache.org/jira/browse/CAMEL-21375 Project: Camel Issue Type: Improvement Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in the DIRECT_ROUTE2 there is:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
When the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in DIRECT_ROUTE2 has this:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
> {code}
>
> and in the DIRECT_ROUTE2 there is:
> {code:java}
>
> .doTry()
> .unmarshal().zipFile()
> {code}
> When the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get
[jira] [Resolved] (CAMEL-21330) Camel-AWS-Secrets-Manager: Support Properties Function with Localstack
[ https://issues.apache.org/jira/browse/CAMEL-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21330. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Support Properties Function with Localstack > -- > > Key: CAMEL-21330 > URL: https://issues.apache.org/jira/browse/CAMEL-21330 > Project: Camel > Issue Type: New Feature >Reporter: Lukas Lowinger >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > > To make Localstack work we need to set correct *endpointOverride* which is > done in the [common aws > client|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/client/impl/SecretsManagerClientStandardImpl.java#L90] > used in Camel. The problem is > [PropertiesFunction|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/SecretsManagerPropertiesFunction.java#L138] > doesn't provide such option. > Just for reference, here is > [code|https://github.com/apache/camel-quarkus/blob/main/integration-tests-support/aws2/src/test/java/org/apache/camel/quarkus/test/support/aws2/Aws2TestEnvContext.java#L185] > which sets it in Camel Quarkus project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in the DIRECT_ROUTE2 there is:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
When the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
This error does not happen on Camel 4.4.0.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in the DIRECT_ROUTE2 there is:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
When the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
> {code}
>
> and in the DIRECT_ROUTE2 there is:
> {code:java}
>
> .doTry()
> .unmarshal().zipFile()
> {code}
> When the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I th
[jira] [Assigned] (CAMEL-21374) camel-jbang - Export pipe with local kamelets seems to fail
[
https://issues.apache.org/jira/browse/CAMEL-21374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-21374:
---
Assignee: Claus Ibsen
> camel-jbang - Export pipe with local kamelets seems to fail
> ---
>
> Key: CAMEL-21374
> URL: https://issues.apache.org/jira/browse/CAMEL-21374
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1, 4.9.0
> Environment: I've set up the environment as follows:
> {code:java}
> camel version
> JBang version: 0.119.0
> Camel JBang version: 4.8.1 {code}
> And the *CamelJBang.java* in JBang's cache folder is defined with:
> {code:java}
> //JAVA 17+
> //REPOS
> central=https://repository.apache.org/content/repositories/orgapachecamel-1759/,https://repo1.maven.org/maven2,apache-snapshot=https://repository.apache.org/content/groups/snapshots/
> //DEPS org.apache.camel:camel-bom:${camel.jbang.version:4.8.1}@pom
> //DEPS org.apache.camel:camel-jbang-core:${camel.jbang.version:4.8.1}
> //DEPS
> org.apache.camel.kamelets:camel-kamelets:${camel-kamelets.version:4.8.0}
> {code}
> With the setup above, running the Pipe with the command in the description
> works well.
> However, the following command fails:
> {code:java}
> camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
> --gav=org.demo:mydemo:1.0.0 {code}
> The error thrown is:
> {code:java}
> Caused by: java.io.FileNotFoundException: Resource not found:
> classpath:kamelets,github:apache:camel-kamelets/kamelets/mytimer.kamelet.yaml
> {code}
> Find attached the source files used in the samples above
>Reporter: Bruno Meseguer
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: pipeexport.tar.gz
>
>
> Running a Pipe using local kamelets seems to work well using the command:
> {code:java}
> camel run * --local-kamelet-dir=./mykamelets/{code}
> Then, the export command seems not able to find the kamelets when running the
> following command:
> {code:java}
> camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
> --gav=org.demo:mydemo:1.0.0
> {code}
> Find attached the source files used to reproduce the problem.
>
> Read +{color:#0747a6}*Environment*{color}+ details (top) to read how to
> reproduce the problem.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
Grzegorz Rozanski created CAMEL-21376:
-
Summary: UseOriginalAggregationStrategy - null pointer
Key: CAMEL-21376
URL: https://issues.apache.org/jira/browse/CAMEL-21376
Project: Camel
Issue Type: Bug
Components: came-core
Affects Versions: 4.8.0
Reporter: Grzegorz Rozanski
Attachments: camel-null-pointer.log
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
and in DIRECT_ROUTE2 there's this code:
[...]
.doTry()
.unmarshal().zipFile()
[...]
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
[...]
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
*oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);*
}
}
[...]
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else {
*oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);*
}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
and in DIRECT_ROUTE2 there's this code:
[...]
.doTry()
.unmarshal().zipFile()
[...]
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
[...]
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
}
[...]
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else \{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
and in DIRECT_ROUTE2 there's this code:
[...]
.doTry()
.unmarshal().zipFile()
[...]
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
[...]
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
*oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);*
}
}
[...]
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else {
*oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);*
}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
>
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
>
> and in DIRECT_ROUTE2 there's this code:
> [...]
> .doTry()
> .unmarshal().zipFile()
> [...]
>
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> [...]
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> }
>
> [...]
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> } else \{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
>
> When I create my own aggregation strategy based on
> UseOriginalAggregationStrategy and modify this `else` part everything works
> properly:
>
> } else if (oldExchange != null)
> { oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
>
>
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
and in DIRECT_ROUTE2 there's this code:
[...]
.doTry()
.unmarshal().zipFile()
[...]
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{{{code:java}}}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
}
{code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else \{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
and in DIRECT_ROUTE2 there's this code:
[...]
.doTry()
.unmarshal().zipFile()
[...]
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
[...]
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
}
[...]
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else \{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
>
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
>
> and in DIRECT_ROUTE2 there's this code:
> [...]
> .doTry()
> .unmarshal().zipFile()
> [...]
>
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
>
> {{{code:java}}}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> }
> {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> } else \{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
>
> When I create my own aggregation strategy based on
> UseOriginalAggregationStrategy and modify this `else` part everything works
> properly:
>
> } else if (oldExchange != null)
> { oldExchange.setProperty(Exchange.EXCEPTION_
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
\{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in DIRECT_ROUTE2 there's this code:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else
{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
and in DIRECT_ROUTE2 there's this code:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else { *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> \{code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
> {code}
> and in DIRECT_ROUTE2 there's this code:
> {code:java}
> .doTry()
> .unmarshal().zipFile()
> {code}
>
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> } else
> { *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
>
> When I create my own aggregation strategy based on
> UseOriginalAggregationStrategy and modify thi
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
and in DIRECT_ROUTE2 there's this code:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else { *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
and in DIRECT_ROUTE2 there's this code:
[...]
.doTry()
.unmarshal().zipFile()
[...]
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{{{code:java}}}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
}
{code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else \{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
>
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
>
> and in DIRECT_ROUTE2 there's this code:
> {code:java}
> .doTry()
> .unmarshal().zipFile()
> {code}
>
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> } else { *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
>
> When I create my own aggregation strategy based on
> UseOriginalAggregationStrategy and modify this `else` part everything works
> properly:
>
> } else if (oldExch
[jira] [Updated] (CAMEL-21374) camel-jbang - Export pipe with local kamelets seems to fail
[
https://issues.apache.org/jira/browse/CAMEL-21374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Meseguer updated CAMEL-21374:
---
Description:
Running a Pipe using local kamelets seems to work well using the command:
{code:java}
camel run * --local-kamelet-dir=./mykamelets/{code}
Then, the export command seems not able to find the kamelets when running the
following command:
{code:java}
camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
--gav=org.demo:mydemo:1.0.0
{code}
Find attached the source files used to reproduce the problem.
Read +{color:#0747a6}*Environment*{color}+ details (top) to read how to
reproduce the problem.
was:
Running a Pipe using local kamelets seems to work well using the command:
{code:java}
camel run * --local-kamelet-dir=./mykamelets/{code}
Then, the export command seems not able to find the kamelets when running the
following command:
{code:java}
camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
--gav=org.demo:mydemo:1.0.0
{code}
Find attached the source files used to reproduce the problem.
> camel-jbang - Export pipe with local kamelets seems to fail
> ---
>
> Key: CAMEL-21374
> URL: https://issues.apache.org/jira/browse/CAMEL-21374
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1, 4.9.0
> Environment: I've set up the environment as follows:
> {code:java}
> camel version
> JBang version: 0.119.0
> Camel JBang version: 4.8.1 {code}
> And the *CamelJBang.java* in JBang's cache folder is defined with:
> {code:java}
> //JAVA 17+
> //REPOS
> central=https://repository.apache.org/content/repositories/orgapachecamel-1759/,https://repo1.maven.org/maven2,apache-snapshot=https://repository.apache.org/content/groups/snapshots/
> //DEPS org.apache.camel:camel-bom:${camel.jbang.version:4.8.1}@pom
> //DEPS org.apache.camel:camel-jbang-core:${camel.jbang.version:4.8.1}
> //DEPS
> org.apache.camel.kamelets:camel-kamelets:${camel-kamelets.version:4.8.0}
> {code}
> With the setup above, running the Pipe with the command in the description
> works well.
> However, the following command fails:
> {code:java}
> camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
> --gav=org.demo:mydemo:1.0.0 {code}
> The error thrown is:
> {code:java}
> Caused by: java.io.FileNotFoundException: Resource not found:
> classpath:kamelets,github:apache:camel-kamelets/kamelets/mytimer.kamelet.yaml
> {code}
> Find attached the source files used in the samples above
>Reporter: Bruno Meseguer
>Priority: Minor
> Attachments: pipeexport.tar.gz
>
>
> Running a Pipe using local kamelets seems to work well using the command:
> {code:java}
> camel run * --local-kamelet-dir=./mykamelets/{code}
> Then, the export command seems not able to find the kamelets when running the
> following command:
> {code:java}
> camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
> --gav=org.demo:mydemo:1.0.0
> {code}
> Find attached the source files used to reproduce the problem.
>
> Read +{color:#0747a6}*Environment*{color}+ details (top) to read how to
> reproduce the problem.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21361) fabric8 kubernetes-client fails to connect to openshift
[
https://issues.apache.org/jira/browse/CAMEL-21361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21361.
-
Resolution: Fixed
> fabric8 kubernetes-client fails to connect to openshift
> ---
>
> Key: CAMEL-21361
> URL: https://issues.apache.org/jira/browse/CAMEL-21361
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs \
>--gav=examples:timer-log:1.0.0 \
>--image-registry image-registry.openshift-image-registry.svc:5000 \
>--trait container.imagePullPolicy=IfNotPresent \
>--cluster-type openshift \
>--runtime=quarkus
> {code}
> This happens with the latest
> [io.fabric8:kubernetes-client-6.13.4|https://github.com/apache/camel/blob/main/parent/pom.xml#L316]
> https://mvnrepository.com/artifact/io.fabric8/kubernetes-client/6.13.4
> {code}
> Run: kubectl get pod -l app.kubernetes.io/name=timer-log
> Exception in thread "main" java.util.ServiceConfigurationError:
> io.fabric8.kubernetes.api.model.KubernetesResource:
> io.fabric8.kubernetes.api.model.LimitRange not a subtype
> at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:593)
> at
> java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1244)
> at
> java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273)
> at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309)
> at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393)
> at java.base/java.util.Iterator.forEachRemaining(Iterator.java:132)
> at
> java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1845)
> at
> java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
> at
> java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:276)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:992)
> 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.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
> at
> io.fabric8.kubernetes.internal.KubernetesDeserializer$Mapping.registerClassesFromClassLoaders(KubernetesDeserializer.java:215)
> at
> io.fabric8.kubernetes.internal.KubernetesDeserializer.(KubernetesDeserializer.java:90)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization.getKubernetesDeserializer(KubernetesSerialization.java:153)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization.access$000(KubernetesSerialization.java:66)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization$1.deserializerInstance(KubernetesSerialization.java:105)
> at
> com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.deserializerInstance(DefaultDeserializationContext.java:245)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache.findDeserializerFromAnnotation(DeserializerCache.java:487)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer(DeserializerCache.java:382)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:317)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:284)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache.findValueDeserializer(DeserializerCache.java:174)
> at
> com.fasterxml.jackson.databind.DeserializationContext.findNonContextualValueDeserializer(DeserializationContext.java:659)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializerBase.res
[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=17892092#comment-17892092 ] Claus Ibsen commented on CAMEL-21352: - SAP has their own custom smb component. They may have some options/features that would be good to get in the ASF component https://help.sap.com/docs/integration-suite/sap-integration-suite/configure-smb-reciever-adapter > 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] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
\{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in DIRECT_ROUTE2 has this:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else
{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
\{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in DIRECT_ROUTE2 there's this code:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else
{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> \{code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
> {code}
> and in DIRECT_ROUTE2 has this:
> {code:java}
> .doTry()
> .unmarshal().zipFile()
> {code}
>
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> } else
> { *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
>
> When I create my ow
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
\{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
{code:java}
and in DIRECT_ROUTE2 has this:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else
{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
\{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in DIRECT_ROUTE2 has this:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else
{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> \{code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
> {code}
> {code:java}
> and in DIRECT_ROUTE2 has this:
> {code:java}
> .doTry()
> .unmarshal().zipFile()
> {code}
>
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> } else
> { *oldExchange.setProperty(Exchange.EXCEP
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2) and in DIRECT_ROUTE2 has this: \{code:java} .doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else
{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
\{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
{code:java}
and in DIRECT_ROUTE2 has this:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else
{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2) and in DIRECT_ROUTE2 has this: \{code:java} .doTry()
> .unmarshal().zipFile()
> {code}
>
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> } else
> { *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
>
> When
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2) and in DIRECT_ROUTE2 has this: \{code:java} .doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2) and in DIRECT_ROUTE2 has this: \{code:java} .doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT,
exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2) and in DIRECT_ROUTE2 has this: \{code:java} .doTry()
> .unmarshal().zipFile()
> {code}
>
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in lin
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2) and in DIRECT_ROUTE2 has this: \{code:java} .doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT,
exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2) and in DIRECT_ROUTE2 has this: \{code:java} .doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
} else
{ *oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);* }
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
} else if (oldExchange != null)
{ oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); }
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2) and in DIRECT_ROUTE2 has this: \{code:java} .doTry()
> .unmarshal().zipFile()
> {code}
>
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> {code:java}
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in DIRECT_ROUTE2 has this:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2) and in DIRECT_ROUTE2 has this: \{code:java} .doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
> {code}
>
> and in DIRECT_ROUTE2 has this:
> {code:java}
> .doTry()
> .unmarshal().zipFile()
> {code}
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerExceptio
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21376:
Fix Version/s: 4.8.2
4.9.0
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2) and in DIRECT_ROUTE2 has this: \{code:java} .doTry()
> .unmarshal().zipFile()
> {code}
>
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> {code:java}
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> {code}
> When I create my own aggregation strategy based on
> UseOriginalAggregationStrategy and modify this `else` part everything works
> properly:
>
> {code:java}
> } else if (oldExchange != null) {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> {code}
>
> I see that similar null check already exists in checkCaughtException method.
>
> The full stack trace can be found as attachment to this ticket.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Rozanski updated CAMEL-21376:
--
Description:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in DIRECT_ROUTE2 has this:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
was:
I found a case when NullPointerException occurs in
UseOriginalAggregationStrategy's aggregate method.
I have this route configuration:
{code:java}
.multicast(AggregationStrategies.useOriginal()).parallelProcessing()
.to(DIRECT_ROUTE1)
.to(DIRECT_ROUTE2)
{code}
and in DIRECT_ROUTE2 has this:
{code:java}
.doTry()
.unmarshal().zipFile()
{code}
when the zip file is invalid there's exception handling in
UseOriginalAggregationStrategy::aggregate method:
{code:java}
exception = checkCaughtException(oldExchange, newExchange);
if (exception != null) {
if (original != null) {
original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception); //NULL
POINTER oldExchange is null
}
} {code}
I checked javadoc about this aggregate method it says that:
Params:
oldExchange - the oldest exchange (is null on first aggregation as we only have
the new exchange)
and I think this is what happens in my case when I get NullPointerException in
line 78 (oldExchange is null):
{code:java}
} else {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
When I create my own aggregation strategy based on
UseOriginalAggregationStrategy and modify this `else` part everything works
properly:
{code:java}
} else if (oldExchange != null) {
oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
}
{code}
I see that similar null check already exists in checkCaughtException method.
The full stack trace can be found as attachment to this ticket.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
> {code}
>
> and in DIRECT_ROUTE2 has this:
> {code:java}
> .doTry()
> .unmarshal().zipFile()
> {code}
> when the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointe
[jira] [Resolved] (CAMEL-21375) Camel-AWS-Secrets-Manager: Support Properties Function with Localstack in Spring Boot
[ https://issues.apache.org/jira/browse/CAMEL-21375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21375. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Support Properties Function with Localstack in > Spring Boot > - > > Key: CAMEL-21375 > URL: https://issues.apache.org/jira/browse/CAMEL-21375 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21373) Camel-AWS-Secrets-Manager: Delete operation add an header for forcing the deletion
[ https://issues.apache.org/jira/browse/CAMEL-21373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21373. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Delete operation add an header for forcing the > deletion > -- > > Key: CAMEL-21373 > URL: https://issues.apache.org/jira/browse/CAMEL-21373 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21374) camel-jbang - Export pipe with local kamelets seems to fail
[
https://issues.apache.org/jira/browse/CAMEL-21374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21374.
-
Resolution: Fixed
> camel-jbang - Export pipe with local kamelets seems to fail
> ---
>
> Key: CAMEL-21374
> URL: https://issues.apache.org/jira/browse/CAMEL-21374
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1, 4.9.0
> Environment: I've set up the environment as follows:
> {code:java}
> camel version
> JBang version: 0.119.0
> Camel JBang version: 4.8.1 {code}
> And the *CamelJBang.java* in JBang's cache folder is defined with:
> {code:java}
> //JAVA 17+
> //REPOS
> central=https://repository.apache.org/content/repositories/orgapachecamel-1759/,https://repo1.maven.org/maven2,apache-snapshot=https://repository.apache.org/content/groups/snapshots/
> //DEPS org.apache.camel:camel-bom:${camel.jbang.version:4.8.1}@pom
> //DEPS org.apache.camel:camel-jbang-core:${camel.jbang.version:4.8.1}
> //DEPS
> org.apache.camel.kamelets:camel-kamelets:${camel-kamelets.version:4.8.0}
> {code}
> With the setup above, running the Pipe with the command in the description
> works well.
> However, the following command fails:
> {code:java}
> camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
> --gav=org.demo:mydemo:1.0.0 {code}
> The error thrown is:
> {code:java}
> Caused by: java.io.FileNotFoundException: Resource not found:
> classpath:kamelets,github:apache:camel-kamelets/kamelets/mytimer.kamelet.yaml
> {code}
> Find attached the source files used in the samples above
>Reporter: Bruno Meseguer
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: pipeexport.tar.gz
>
>
> Running a Pipe using local kamelets seems to work well using the command:
> {code:java}
> camel run * --local-kamelet-dir=./mykamelets/{code}
> Then, the export command seems not able to find the kamelets when running the
> following command:
> {code:java}
> camel export * --local-kamelet-dir=./mykamelets/ --runtime=quarkus
> --gav=org.demo:mydemo:1.0.0
> {code}
> Find attached the source files used to reproduce the problem.
>
> Read +{color:#0747a6}*Environment*{color}+ details (top) to read how to
> reproduce the problem.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892126#comment-17892126
]
Claus Ibsen commented on CAMEL-21376:
-
But ideally that UseOriginalAggregationStrategy should check for != null as
well, you are welcome to send a PR on main branch
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
> {code}
>
> and in the DIRECT_ROUTE2 there is:
> {code:java}
>
> .doTry()
> .unmarshal().zipFile()
> {code}
> When the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> {code:java}
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> {code}
> When I create my own aggregation strategy based on
> UseOriginalAggregationStrategy and modify this `else` part everything works
> properly:
>
> {code:java}
> } else if (oldExchange != null) {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> {code}
>
> I see that similar null check already exists in checkCaughtException method.
>
> The full stack trace can be found as attachment to this ticket.
> This error does not happen on Camel 4.4.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892125#comment-17892125
]
Claus Ibsen commented on CAMEL-21376:
-
try with 4.8.1, we have fixed camel-zipfile.
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
> {code}
>
> and in the DIRECT_ROUTE2 there is:
> {code:java}
>
> .doTry()
> .unmarshal().zipFile()
> {code}
> When the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> {code:java}
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> {code}
> When I create my own aggregation strategy based on
> UseOriginalAggregationStrategy and modify this `else` part everything works
> properly:
>
> {code:java}
> } else if (oldExchange != null) {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> {code}
>
> I see that similar null check already exists in checkCaughtException method.
>
> The full stack trace can be found as attachment to this ticket.
> This error does not happen on Camel 4.4.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21372) Camel JBang Export/Run are not working based on external camel-version setting
[
https://issues.apache.org/jira/browse/CAMEL-21372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-21372:
---
Assignee: Claus Ibsen
> Camel JBang Export/Run are not working based on external camel-version setting
> --
>
> Key: CAMEL-21372
> URL: https://issues.apache.org/jira/browse/CAMEL-21372
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Salvatore Mongiardo
>Assignee: Claus Ibsen
>Priority: Minor
> Attachments: jbang-export-issue.log
>
>
> The export/run command doesn't work when a "custom" _camel-version_ is set:
> camel config set
> deps=org.apache.camel.springboot:camel-timer-starter,camel:management,camel:cli-connector
> camel config set runtime=spring-boot
> camel config set gav=com.foo:acme:1.0-SNAPSHOT
> *camel config set camel-version=4.8.x-y*
> camel config set additional-properties=openshift-maven-plugin-version=1.17.0.y
> camel config set camel-spring-boot-version=4.8.0.y
> camel init test.yaml --directory=app
> Executing:
> {code:java}
> camel export app/test.yaml
> {code}
> This
> [exception|https://issues.redhat.com/secure/attachment/13285203/jbang-export-issue.log]
> is raised.
> The same happens with:
> {code:java}
> camel run app/test.yaml
> {code}
> If we unset the {_}camel-version{_}:
> *camel config unset camel-version*
> then
> {code:java}
> camel export app/test.yaml
> {code}
> works fine.
> I guess the issue could be the way how the method
> [Run.runCustomCamelVersion|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/Run.java#L838]
> is called, basically loosing every previous relationship with the
> [spec|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/CamelCommand.java#L40C5-L40C40]
> object
> h3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21372) Camel JBang Export/Run are not working based on external camel-version setting
[
https://issues.apache.org/jira/browse/CAMEL-21372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21372:
Fix Version/s: 4.8.2
4.9.0
> Camel JBang Export/Run are not working based on external camel-version setting
> --
>
> Key: CAMEL-21372
> URL: https://issues.apache.org/jira/browse/CAMEL-21372
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Salvatore Mongiardo
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: jbang-export-issue.log
>
>
> The export/run command doesn't work when a "custom" _camel-version_ is set:
> camel config set
> deps=org.apache.camel.springboot:camel-timer-starter,camel:management,camel:cli-connector
> camel config set runtime=spring-boot
> camel config set gav=com.foo:acme:1.0-SNAPSHOT
> *camel config set camel-version=4.8.x-y*
> camel config set additional-properties=openshift-maven-plugin-version=1.17.0.y
> camel config set camel-spring-boot-version=4.8.0.y
> camel init test.yaml --directory=app
> Executing:
> {code:java}
> camel export app/test.yaml
> {code}
> This
> [exception|https://issues.redhat.com/secure/attachment/13285203/jbang-export-issue.log]
> is raised.
> The same happens with:
> {code:java}
> camel run app/test.yaml
> {code}
> If we unset the {_}camel-version{_}:
> *camel config unset camel-version*
> then
> {code:java}
> camel export app/test.yaml
> {code}
> works fine.
> I guess the issue could be the way how the method
> [Run.runCustomCamelVersion|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/Run.java#L838]
> is called, basically loosing every previous relationship with the
> [spec|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/CamelCommand.java#L40C5-L40C40]
> object
> h3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21377) camel-jbang - Add default values to --help
Claus Ibsen created CAMEL-21377: --- Summary: camel-jbang - Add default values to --help Key: CAMEL-21377 URL: https://issues.apache.org/jira/browse/CAMEL-21377 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Fix For: 4.x You cannot automatic have picolli output the default values for each option. We need to add this via some special token in the description text for each option. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21378) Enable camel-opentelemetry-starter by default
[ https://issues.apache.org/jira/browse/CAMEL-21378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-21378: -- Priority: Minor (was: Major) > Enable camel-opentelemetry-starter by default > -- > > Key: CAMEL-21378 > URL: https://issues.apache.org/jira/browse/CAMEL-21378 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot-starters >Affects Versions: 4.8.0 >Reporter: John Poth >Priority: Minor > Fix For: 4.9.0 > > > When camel-opentelemetry-starter is on the classpath, camel-opentelemetry > should be setup by default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21372) Camel JBang Export/Run are not working based on external camel-version setting
[
https://issues.apache.org/jira/browse/CAMEL-21372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892148#comment-17892148
]
Salvatore Mongiardo commented on CAMEL-21372:
-
I'm sorry. I forgot to mention it in the description. That's the specific case
tested:
{code:java}
dependencies =
org.apache.camel.springboot:camel-timer-starter,camel:management,camel:cli-connector
runtime = spring-boot
gav = com.foo:acme:1.0-SNAPSHOT
build-properties = openshift-maven-plugin-version=1.17.0.x-y
camel-spring-boot-version = 4.8.0.x-
repos =
https://maven.repository.[custom-ga.zz]/ga,https://[another-maven-dev-repo]/
camel-version = 4.8.0.x-w
{code}
> Camel JBang Export/Run are not working based on external camel-version setting
> --
>
> Key: CAMEL-21372
> URL: https://issues.apache.org/jira/browse/CAMEL-21372
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Salvatore Mongiardo
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: jbang-export-issue.log
>
>
> The export/run command doesn't work when a "custom" _camel-version_ is set:
> camel config set
> deps=org.apache.camel.springboot:camel-timer-starter,camel:management,camel:cli-connector
> camel config set runtime=spring-boot
> camel config set gav=com.foo:acme:1.0-SNAPSHOT
> *camel config set camel-version=4.8.x-y*
> camel config set additional-properties=openshift-maven-plugin-version=1.17.0.y
> camel config set camel-spring-boot-version=4.8.0.y
> camel init test.yaml --directory=app
> Executing:
> {code:java}
> camel export app/test.yaml
> {code}
> This
> [exception|https://issues.redhat.com/secure/attachment/13285203/jbang-export-issue.log]
> is raised.
> The same happens with:
> {code:java}
> camel run app/test.yaml
> {code}
> If we unset the {_}camel-version{_}:
> *camel config unset camel-version*
> then
> {code:java}
> camel export app/test.yaml
> {code}
> works fine.
> I guess the issue could be the way how the method
> [Run.runCustomCamelVersion|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/Run.java#L838]
> is called, basically loosing every previous relationship with the
> [spec|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/CamelCommand.java#L40C5-L40C40]
> object
> h3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21372) Camel JBang Export/Run are not working based on external camel-version setting
[
https://issues.apache.org/jira/browse/CAMEL-21372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892142#comment-17892142
]
Claus Ibsen commented on CAMEL-21372:
-
You would need to set url to a maven repo that has your custom camel distro.
ASF Camel only loads from maven central and ASF snapshot
camel config set repos=
> Camel JBang Export/Run are not working based on external camel-version setting
> --
>
> Key: CAMEL-21372
> URL: https://issues.apache.org/jira/browse/CAMEL-21372
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Salvatore Mongiardo
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: jbang-export-issue.log
>
>
> The export/run command doesn't work when a "custom" _camel-version_ is set:
> camel config set
> deps=org.apache.camel.springboot:camel-timer-starter,camel:management,camel:cli-connector
> camel config set runtime=spring-boot
> camel config set gav=com.foo:acme:1.0-SNAPSHOT
> *camel config set camel-version=4.8.x-y*
> camel config set additional-properties=openshift-maven-plugin-version=1.17.0.y
> camel config set camel-spring-boot-version=4.8.0.y
> camel init test.yaml --directory=app
> Executing:
> {code:java}
> camel export app/test.yaml
> {code}
> This
> [exception|https://issues.redhat.com/secure/attachment/13285203/jbang-export-issue.log]
> is raised.
> The same happens with:
> {code:java}
> camel run app/test.yaml
> {code}
> If we unset the {_}camel-version{_}:
> *camel config unset camel-version*
> then
> {code:java}
> camel export app/test.yaml
> {code}
> works fine.
> I guess the issue could be the way how the method
> [Run.runCustomCamelVersion|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/Run.java#L838]
> is called, basically loosing every previous relationship with the
> [spec|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/CamelCommand.java#L40C5-L40C40]
> object
> h3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21378) Enable camel-opentelemetry-starter by default
[ https://issues.apache.org/jira/browse/CAMEL-21378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-21378: - Assignee: John Poth > Enable camel-opentelemetry-starter by default > -- > > Key: CAMEL-21378 > URL: https://issues.apache.org/jira/browse/CAMEL-21378 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot-starters >Affects Versions: 4.8.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 4.9.0 > > > When camel-opentelemetry-starter is on the classpath, camel-opentelemetry > should be setup by default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21378) Enable camel-opentelemetry-starter by default
[ https://issues.apache.org/jira/browse/CAMEL-21378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21378: Issue Type: Improvement (was: Bug) > Enable camel-opentelemetry-starter by default > -- > > Key: CAMEL-21378 > URL: https://issues.apache.org/jira/browse/CAMEL-21378 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot-starters >Affects Versions: 4.8.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 4.9.0 > > > When camel-opentelemetry-starter is on the classpath, camel-opentelemetry > should be setup by default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21378) Enable camel-opentelemetry-starter by default
John Poth created CAMEL-21378: - Summary: Enable camel-opentelemetry-starter by default Key: CAMEL-21378 URL: https://issues.apache.org/jira/browse/CAMEL-21378 Project: Camel Issue Type: Bug Components: camel-spring-boot-starters Affects Versions: 4.8.0 Reporter: John Poth Fix For: 4.9.0 When camel-opentelemetry-starter is on the classpath, camel-opentelemetry should be setup by default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21372) Camel JBang Export/Run are not working based on external camel-version setting
[
https://issues.apache.org/jira/browse/CAMEL-21372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21372.
-
Resolution: Fixed
> Camel JBang Export/Run are not working based on external camel-version setting
> --
>
> Key: CAMEL-21372
> URL: https://issues.apache.org/jira/browse/CAMEL-21372
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Salvatore Mongiardo
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: jbang-export-issue.log
>
>
> The export/run command doesn't work when a "custom" _camel-version_ is set:
> camel config set
> deps=org.apache.camel.springboot:camel-timer-starter,camel:management,camel:cli-connector
> camel config set runtime=spring-boot
> camel config set gav=com.foo:acme:1.0-SNAPSHOT
> *camel config set camel-version=4.8.x-y*
> camel config set additional-properties=openshift-maven-plugin-version=1.17.0.y
> camel config set camel-spring-boot-version=4.8.0.y
> camel init test.yaml --directory=app
> Executing:
> {code:java}
> camel export app/test.yaml
> {code}
> This
> [exception|https://issues.redhat.com/secure/attachment/13285203/jbang-export-issue.log]
> is raised.
> The same happens with:
> {code:java}
> camel run app/test.yaml
> {code}
> If we unset the {_}camel-version{_}:
> *camel config unset camel-version*
> then
> {code:java}
> camel export app/test.yaml
> {code}
> works fine.
> I guess the issue could be the way how the method
> [Run.runCustomCamelVersion|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/Run.java#L838]
> is called, basically loosing every previous relationship with the
> [spec|https://github.com/apache/camel/blob/camel-4.8.0/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/CamelCommand.java#L40C5-L40C40]
> object
> h3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21380) camel-salesforce: pub/sub: add ability to opt out of proxy
Jeremy Ross created CAMEL-21380: --- Summary: camel-salesforce: pub/sub: add ability to opt out of proxy Key: CAMEL-21380 URL: https://issues.apache.org/jira/browse/CAMEL-21380 Project: Camel Issue Type: Bug Components: camel-salesforce Affects Versions: 4.8.0 Reporter: Jeremy Ross Assignee: Jeremy Ross Fix For: 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21380) camel-salesforce: pub/sub: add ability to opt out of proxy
[ https://issues.apache.org/jira/browse/CAMEL-21380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Ross updated CAMEL-21380: Description: By default the underlying grpc implementation automatically uses any detected proxy server. Need the ability to override this and not use a proxy. > camel-salesforce: pub/sub: add ability to opt out of proxy > --- > > Key: CAMEL-21380 > URL: https://issues.apache.org/jira/browse/CAMEL-21380 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 4.8.0 >Reporter: Jeremy Ross >Assignee: Jeremy Ross >Priority: Major > Fix For: 4.9.0 > > > By default the underlying grpc implementation automatically uses any detected > proxy server. Need the ability to override this and not use a proxy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21379) camel-salesforce: introduce delay in pub/sub reconnect attempts
Jeremy Ross created CAMEL-21379: --- Summary: camel-salesforce: introduce delay in pub/sub reconnect attempts Key: CAMEL-21379 URL: https://issues.apache.org/jira/browse/CAMEL-21379 Project: Camel Issue Type: Bug Components: camel-salesforce Affects Versions: 4.8.0 Reporter: Jeremy Ross Assignee: Jeremy Ross Fix For: 4.9.0 Currently enters a tight, infinite loop of reconnect attempts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21379) camel-salesforce: introduce delay in pub/sub reconnect attempts
[ https://issues.apache.org/jira/browse/CAMEL-21379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Ross resolved CAMEL-21379. - Resolution: Fixed > camel-salesforce: introduce delay in pub/sub reconnect attempts > --- > > Key: CAMEL-21379 > URL: https://issues.apache.org/jira/browse/CAMEL-21379 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 4.8.0 >Reporter: Jeremy Ross >Assignee: Jeremy Ross >Priority: Minor > Fix For: 4.8.2, 4.9.0 > > > Currently enters a tight, infinite loop of reconnect attempts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21378) Enable camel-opentelemetry-starter by default
[ https://issues.apache.org/jira/browse/CAMEL-21378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892270#comment-17892270 ] Claus Ibsen commented on CAMEL-21378: - Ah yeah, and you can still disable it if you really need via the camel.xxx.enabled = false option without having to remove the dependency. > Enable camel-opentelemetry-starter by default > -- > > Key: CAMEL-21378 > URL: https://issues.apache.org/jira/browse/CAMEL-21378 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot-starters >Affects Versions: 4.8.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 4.9.0 > > > When camel-opentelemetry-starter is on the classpath, camel-opentelemetry > should be setup by default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21302) camel-opentelemetry context leak with direct async producer
[
https://issues.apache.org/jira/browse/CAMEL-21302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892271#comment-17892271
]
Claus Ibsen commented on CAMEL-21302:
-
Freeman, you can backport to older branches.
> camel-opentelemetry context leak with direct async producer
> ---
>
> Key: CAMEL-21302
> URL: https://issues.apache.org/jira/browse/CAMEL-21302
> Project: Camel
> Issue Type: Bug
> Components: camel-opentelemetry
>Reporter: John Poth
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 4.4.5, 4.8.2, 4.9.0
>
>
> There seems to be a Otel context leak when using a CXF producer in async
> mode. This causes different requests to have the same _traceId._ As a
> workaround, setting _synchronous=true_ on the CXF producer resolves the
> issue. Here's a reproducer:
> {code:java}
> @Override
> protected RoutesBuilder createRouteBuilder() {
> return new RouteBuilder() {
> @Override
> public void configure() {
> from("direct:start").routeId("myRoute")
> .to("direct:send")
> .end();
> from("direct:send")
> .log("message")
> .to("cxfrs:http://localhost:"; + port1
> + "/rest/helloservice/sayHello?synchronous=false");
> // setting to 'true' resolves the issue
> restConfiguration()
> .port(port1);
> rest("/rest/helloservice")
> .post("/sayHello").routeId("rest-GET-say-hi")
> .to("direct:sayHi");
> from("direct:sayHi")
> .routeId("mock-GET-say-hi")
> .log("example")
> .to("mock:end");
> }};
> {code}
>
> I've added the complete unit here:
> https://github.com/apache/camel/blob/7d83a62b8e442dc9ac6fd79b153192add940301e/components/camel-opentelemetry/src/test/java/org/apache/camel/opentelemetry/AsyncCxfTest.java
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21369) camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress and Route traits
[ https://issues.apache.org/jira/browse/CAMEL-21369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21369: Fix Version/s: 4.9.0 > camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress and > Route traits > - > > Key: CAMEL-21369 > URL: https://issues.apache.org/jira/browse/CAMEL-21369 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.x >Reporter: Gaelle Fournier >Priority: Major > Fix For: 4.9.0 > > > In Kubernetes plugin, Ingress and Route trait (service exposure) are only > available through the generated kubernetes/openshift manifest. > To leverage quarkus cloud readyness we should add for quarkus runtime cases > the use of: > * for ingress: > https://quarkus.io/guides/deploying-to-kubernetes#exposing-your-application-in-kubernetes > > * for openshift: > https://quarkus.io/guides/deploying-to-openshift#exposing_routes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21380) camel-salesforce: pub/sub: add ability to opt out of proxy
[ https://issues.apache.org/jira/browse/CAMEL-21380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Ross resolved CAMEL-21380. - Resolution: Fixed > camel-salesforce: pub/sub: add ability to opt out of proxy > --- > > Key: CAMEL-21380 > URL: https://issues.apache.org/jira/browse/CAMEL-21380 > Project: Camel > Issue Type: Improvement > Components: camel-salesforce >Affects Versions: 4.8.0 >Reporter: Jeremy Ross >Assignee: Jeremy Ross >Priority: Major > Fix For: 4.9.0 > > > By default the underlying grpc implementation automatically uses any detected > proxy server. Need the ability to override this and not use a proxy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21380) camel-salesforce: pub/sub: add ability to opt out of proxy
[ https://issues.apache.org/jira/browse/CAMEL-21380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21380: Issue Type: Improvement (was: Bug) > camel-salesforce: pub/sub: add ability to opt out of proxy > --- > > Key: CAMEL-21380 > URL: https://issues.apache.org/jira/browse/CAMEL-21380 > Project: Camel > Issue Type: Improvement > Components: camel-salesforce >Affects Versions: 4.8.0 >Reporter: Jeremy Ross >Assignee: Jeremy Ross >Priority: Major > Fix For: 4.9.0 > > > By default the underlying grpc implementation automatically uses any detected > proxy server. Need the ability to override this and not use a proxy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21379) camel-salesforce: introduce delay in pub/sub reconnect attempts
[ https://issues.apache.org/jira/browse/CAMEL-21379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21379: Fix Version/s: 4.8.2 > camel-salesforce: introduce delay in pub/sub reconnect attempts > --- > > Key: CAMEL-21379 > URL: https://issues.apache.org/jira/browse/CAMEL-21379 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 4.8.0 >Reporter: Jeremy Ross >Assignee: Jeremy Ross >Priority: Minor > Fix For: 4.8.2, 4.9.0 > > > Currently enters a tight, infinite loop of reconnect attempts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
