[jira] [Commented] (CAMEL-18005) add tests in camel-paho-starter
[ https://issues.apache.org/jira/browse/CAMEL-18005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527744#comment-17527744 ] Freeman Yue Fang commented on CAMEL-18005: -- PR is https://github.com/apache/camel-spring-boot/pull/543 > add tests in camel-paho-starter > --- > > Key: CAMEL-18005 > URL: https://issues.apache.org/jira/browse/CAMEL-18005 > Project: Camel > Issue Type: Test > Components: camel-paho, camel-spring-boot-starters, tests >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.17.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18010) camel-jbang - Resolved downloaded JARs should consider jbang CP
Claus Ibsen created CAMEL-18010: --- Summary: camel-jbang - Resolved downloaded JARs should consider jbang CP Key: CAMEL-18010 URL: https://issues.apache.org/jira/browse/CAMEL-18010 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.17.0 When running from jbang then some JARs are pre-loaded on CP. We should deal with this to know that its a JAR that is needed at runtime (hence downloaded). This makes it possible to better resolve the correct set of JARs for package fat-jar and other goals. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18008) camel-jbang deploy/undeploy command
[
https://issues.apache.org/jira/browse/CAMEL-18008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marat Gubaidullin updated CAMEL-18008:
--
Description:
Deploy integration application to minikube
{code:sh}
jbang camel@apache/camel deploy --namespace default --name demo --version 1.0
--image timer/jbang:latest --minikube --replicas 1
{code}
Undeploy integration application to minikube
{code:sh}
jbang camel@apache/camel undeploy --namespace default --name demo --minikube
{code}
was:
Deploy integration application to minikube
{code:java}
jbang camel@apache/camel deploy --namespace default --name demo --version 1.0
--image timer/jbang:latest --minikube --replicas 1
{code}
Undeploy integration application to minikube
{code:java}
jbang camel@apache/camel undeploy --namespace default --name demo --minikube
{code}
> camel-jbang deploy/undeploy command
> ---
>
> Key: CAMEL-18008
> URL: https://issues.apache.org/jira/browse/CAMEL-18008
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Reporter: Marat Gubaidullin
>Assignee: Marat Gubaidullin
>Priority: Major
> Fix For: 3.17.0
>
>
> Deploy integration application to minikube
> {code:sh}
> jbang camel@apache/camel deploy --namespace default --name demo --version 1.0
> --image timer/jbang:latest --minikube --replicas 1
> {code}
> Undeploy integration application to minikube
> {code:sh}
> jbang camel@apache/camel undeploy --namespace default --name demo --minikube
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18008) camel-jbang deploy/undeploy command
[
https://issues.apache.org/jira/browse/CAMEL-18008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marat Gubaidullin updated CAMEL-18008:
--
Description:
Deploy integration application to minikube
{code:java}
jbang camel@apache/camel deploy --namespace default --name demo --version 1.0
--image timer/jbang:latest --minikube --replicas 1
{code}
Undeploy integration application to minikube
{code:java}
jbang camel@apache/camel undeploy --namespace default --name demo --minikube
{code}
> camel-jbang deploy/undeploy command
> ---
>
> Key: CAMEL-18008
> URL: https://issues.apache.org/jira/browse/CAMEL-18008
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Reporter: Marat Gubaidullin
>Assignee: Marat Gubaidullin
>Priority: Major
> Fix For: 3.17.0
>
>
> Deploy integration application to minikube
> {code:java}
> jbang camel@apache/camel deploy --namespace default --name demo --version 1.0
> --image timer/jbang:latest --minikube --replicas 1
> {code}
> Undeploy integration application to minikube
> {code:java}
> jbang camel@apache/camel undeploy --namespace default --name demo --minikube
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18006) camel-jbang package image command
[
https://issues.apache.org/jira/browse/CAMEL-18006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marat Gubaidullin updated CAMEL-18006:
--
Description:
Create image from *jar* with {*}tag{*}:
{code:java}
jbang camel@apache/camel build image --jar runner.jar --tag camel/demo
{code}
Create image from *jar* with *tag* from specified *base image *:
{code:java}
jbang camel@apache/camel build image --jar runner.jar --tag camel/demo --from
registry.access.redhat.com/ubi8/openjdk-11-runtime:1.11
{code}
if you want to deploy later to minikube, execute the following command before
{*}build{*}:
{code:java}
eval $(minikube -p minikube docker-env
{code}
Push image from *jar* with *tag* to {*}registry{*}:
{code:java}
jbang camel@apache/camel build image --jar runner.jar --tag camel/demo
--registry registry.access.redhat.com/camel/jbang-demo --username demo
--password demo
{code}
was:
Create image from *jar* with {*}tag{*}:
{code:java}
jbang camel@apache/camel build image --jar runner.jar --tag camel/demo
{code}
Create image from *jar* with *tag* from specified *base image *:
{code:java}
jbang camel@apache/camel build image --jar runner.jar --tag camel/demo --from
registry.access.redhat.com/ubi8/openjdk-11-runtime:1.11
{code}
Push image from *jar* with *tag* to {*}registry{*}:
{code:java}
jbang camel@apache/camel build image --jar runner.jar --tag camel/demo
--registry registry.access.redhat.com/camel/jbang-demo --username demo
--password demo
{code}
> camel-jbang package image command
> -
>
> Key: CAMEL-18006
> URL: https://issues.apache.org/jira/browse/CAMEL-18006
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Reporter: Marat Gubaidullin
>Assignee: Marat Gubaidullin
>Priority: Major
> Fix For: 3.17.0
>
>
> Create image from *jar* with {*}tag{*}:
> {code:java}
> jbang camel@apache/camel build image --jar runner.jar --tag camel/demo
> {code}
> Create image from *jar* with *tag* from specified *base image *:
> {code:java}
> jbang camel@apache/camel build image --jar runner.jar --tag camel/demo --from
> registry.access.redhat.com/ubi8/openjdk-11-runtime:1.11
> {code}
> if you want to deploy later to minikube, execute the following command before
> {*}build{*}:
> {code:java}
> eval $(minikube -p minikube docker-env
> {code}
> Push image from *jar* with *tag* to {*}registry{*}:
> {code:java}
> jbang camel@apache/camel build image --jar runner.jar --tag camel/demo
> --registry registry.access.redhat.com/camel/jbang-demo --username demo
> --password demo
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (CAMEL-17998) camel-jbang - fat-jar command
[ https://issues.apache.org/jira/browse/CAMEL-17998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17526005#comment-17526005 ] Claus Ibsen edited comment on CAMEL-17998 at 4/25/22 5:25 PM: -- TODO: fat-jar classloader to load inside the jar *DONE* TODO: package target/camel-app as single .jar output *DONE* TODO: MANIFEST.MF with main class entry so fat-jar can be run with java -jar *DONE* was (Author: davsclaus): TODO: fat-jar classloader to load inside the jar TODO: package target/camel-app as single .jar output TODO: MANIFEST.MF with main class entry so fat-jar can be run with java -jar > camel-jbang - fat-jar command > - > > Key: CAMEL-17998 > URL: https://issues.apache.org/jira/browse/CAMEL-17998 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.17.0 > > > A goal to build the app as a fat-jar -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-17998) camel-jbang - fat-jar command
[ https://issues.apache.org/jira/browse/CAMEL-17998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527663#comment-17527663 ] Claus Ibsen commented on CAMEL-17998: - TODO: fat-jar to work with java-joor-dsl that does runtime compilation > camel-jbang - fat-jar command > - > > Key: CAMEL-17998 > URL: https://issues.apache.org/jira/browse/CAMEL-17998 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.17.0 > > > A goal to build the app as a fat-jar -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-17861) Streaming in Azure (Blob-Storage) component not working
[ https://issues.apache.org/jira/browse/CAMEL-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527638#comment-17527638 ] Christian Müller commented on CAMEL-17861: -- [~davsclaus] fyi https://github.com/apache/camel/pull/7493 > Streaming in Azure (Blob-Storage) component not working > -- > > Key: CAMEL-17861 > URL: https://issues.apache.org/jira/browse/CAMEL-17861 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 3.14.1 >Reporter: Christian Müller >Priority: Major > Fix For: 3.x > > > As described in the email conversation below we are having memory problems > with the current implementation of the azure (blob storage component). > Concretely the component does not stream properly! > _But looking at this stacktrace and the corresponding sourcecode it’s obvious > that the whole stream is read to memory to check the total payload size > (seems necessary for the azure client)_ > As we transfer mass data with the azure component we consider this a major > bug as we cannot use the azure-component as long as it does not stream > properly. > Thx and Regards Christian > Email History (camel user mailing list): > *Response from Claus Ibsen:* > What are the sources of those streams? > I wonder if we could enrich from the message some sort of total size header > into the camel blob producer, so it can tell the blob client the expected > length, so it does not read the stream itself to find out. > Also if you have the opportunity you are welcome to test with latest Camel > 3.9.0 release, if its still a problem. > > And you are welcome to create a JIRA as it would be great to have streaming > work well with azure, especially for blob as its supposed to be also big > blobs of data ;) > *initial question from Lukas Angerer:* > We are transferring lots of data to the azure-storage with the > azure-storage-blob component (version 3.7.0) > The Route itself is only working with streams to keep the memory overhead > low, streamcaching is enabled. > But looking at this stacktrace and the corresponding sourcecode it’s obvious > that the whole stream is read to memory to check the total payload size > (seems necessary for the azure client) > > Caused by: java.lang.OutOfMemoryError: Java heap space > at > org.apache.commons.io.output.AbstractByteArrayOutputStream.toByteArrayImpl(AbstractByteArrayOutputStream.java:366) > at > org.apache.commons.io.output.ByteArrayOutputStream.toByteArray(ByteArrayOutputStream.java:163) > at org.apache.commons.io.IOUtils.toByteArray(IOUtils.java:2241) > at > org.apache.camel.component.azure.storage.blob.BlobUtils.getInputStreamLength(BlobUtils.java:37) > at > org.apache.camel.component.azure.storage.blob.BlobStreamAndLength.createBlobStreamAndLengthFromExchangeBody(BlobStreamAndLength.java:50) > at > org.apache.camel.component.azure.storage.blob.operations.BlobOperations.uploadBlockBlob(BlobOperations.java:181) > at > org.apache.camel.component.azure.storage.blob.BlobProducer.process(BlobProducer.java:86) > at > org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:66) > at > org.apache.camel.processor.SendDynamicProcessor.lambda$process$0(SendDynamicProcessor.java:195) > I was wondering if there is a better way to do this. Maybe a shortcut for the > cached stream that just checks the size of the cache? > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18006) camel-jbang package image command
[
https://issues.apache.org/jira/browse/CAMEL-18006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marat Gubaidullin updated CAMEL-18006:
--
Description:
Create image from *jar* with {*}tag{*}:
{code:java}
jbang camel@apache/camel build image --jar runner.jar --tag camel/demo
{code}
Create image from *jar* with *tag* from specified *base image *:
{code:java}
jbang camel@apache/camel build image --jar runner.jar --tag camel/demo --from
registry.access.redhat.com/ubi8/openjdk-11-runtime:1.11
{code}
Push image from *jar* with *tag* to {*}registry{*}:
{code:java}
jbang camel@apache/camel build image --jar runner.jar --tag camel/demo
--registry registry.access.redhat.com/camel/jbang-demo --username demo
--password demo
{code}
was:
Create image from *jar* with *tag*:
{code:java}
jbang camel@apache/camel package image --jar runner.jar --tag camel/demo
{code}
Create image from *jar* with *tag* from specified *base image *:
{code:java}
jbang camel@apache/camel package image --jar runner.jar --tag camel/demo --from
registry.access.redhat.com/ubi8/openjdk-11-runtime:1.11
{code}
Push image from *jar* with *tag* to *registry*:
{code:java}
jbang camel@apache/camel package image --jar runner.jar --tag camel/demo
--registry registry.access.redhat.com/camel/jbang-demo --username demo
--password demo
{code}
> camel-jbang package image command
> -
>
> Key: CAMEL-18006
> URL: https://issues.apache.org/jira/browse/CAMEL-18006
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Reporter: Marat Gubaidullin
>Assignee: Marat Gubaidullin
>Priority: Major
> Fix For: 3.17.0
>
>
> Create image from *jar* with {*}tag{*}:
> {code:java}
> jbang camel@apache/camel build image --jar runner.jar --tag camel/demo
> {code}
> Create image from *jar* with *tag* from specified *base image *:
> {code:java}
> jbang camel@apache/camel build image --jar runner.jar --tag camel/demo --from
> registry.access.redhat.com/ubi8/openjdk-11-runtime:1.11
> {code}
> Push image from *jar* with *tag* to {*}registry{*}:
> {code:java}
> jbang camel@apache/camel build image --jar runner.jar --tag camel/demo
> --registry registry.access.redhat.com/camel/jbang-demo --username demo
> --password demo
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (CAMEL-18009) add tests in camel-mail-starter
Freeman Yue Fang created CAMEL-18009: Summary: add tests in camel-mail-starter Key: CAMEL-18009 URL: https://issues.apache.org/jira/browse/CAMEL-18009 Project: Camel Issue Type: Test Components: camel-mail, camel-spring-boot-starters, tests Reporter: Freeman Yue Fang Assignee: Freeman Yue Fang Fix For: 3.17.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527449#comment-17527449 ] Jean-Baptiste Onofré commented on CAMEL-15288: -- [~lichtin] yes, definitely. My bad, I have to switch back to Camel work. I will move forward asap. I will keep you posted. > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527436#comment-17527436 ] Martin Lichtin commented on CAMEL-15288: Can this one be considered at some point? It is a performance hit to constantly lookup OSGi services. > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-17861) Streaming in Azure (Blob-Storage) component not working
[ https://issues.apache.org/jira/browse/CAMEL-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527391#comment-17527391 ] Claus Ibsen commented on CAMEL-17861: - Yes a PR is much welcome > Streaming in Azure (Blob-Storage) component not working > -- > > Key: CAMEL-17861 > URL: https://issues.apache.org/jira/browse/CAMEL-17861 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 3.14.1 >Reporter: Christian Müller >Priority: Major > Fix For: 3.x > > > As described in the email conversation below we are having memory problems > with the current implementation of the azure (blob storage component). > Concretely the component does not stream properly! > _But looking at this stacktrace and the corresponding sourcecode it’s obvious > that the whole stream is read to memory to check the total payload size > (seems necessary for the azure client)_ > As we transfer mass data with the azure component we consider this a major > bug as we cannot use the azure-component as long as it does not stream > properly. > Thx and Regards Christian > Email History (camel user mailing list): > *Response from Claus Ibsen:* > What are the sources of those streams? > I wonder if we could enrich from the message some sort of total size header > into the camel blob producer, so it can tell the blob client the expected > length, so it does not read the stream itself to find out. > Also if you have the opportunity you are welcome to test with latest Camel > 3.9.0 release, if its still a problem. > > And you are welcome to create a JIRA as it would be great to have streaming > work well with azure, especially for blob as its supposed to be also big > blobs of data ;) > *initial question from Lukas Angerer:* > We are transferring lots of data to the azure-storage with the > azure-storage-blob component (version 3.7.0) > The Route itself is only working with streams to keep the memory overhead > low, streamcaching is enabled. > But looking at this stacktrace and the corresponding sourcecode it’s obvious > that the whole stream is read to memory to check the total payload size > (seems necessary for the azure client) > > Caused by: java.lang.OutOfMemoryError: Java heap space > at > org.apache.commons.io.output.AbstractByteArrayOutputStream.toByteArrayImpl(AbstractByteArrayOutputStream.java:366) > at > org.apache.commons.io.output.ByteArrayOutputStream.toByteArray(ByteArrayOutputStream.java:163) > at org.apache.commons.io.IOUtils.toByteArray(IOUtils.java:2241) > at > org.apache.camel.component.azure.storage.blob.BlobUtils.getInputStreamLength(BlobUtils.java:37) > at > org.apache.camel.component.azure.storage.blob.BlobStreamAndLength.createBlobStreamAndLengthFromExchangeBody(BlobStreamAndLength.java:50) > at > org.apache.camel.component.azure.storage.blob.operations.BlobOperations.uploadBlockBlob(BlobOperations.java:181) > at > org.apache.camel.component.azure.storage.blob.BlobProducer.process(BlobProducer.java:86) > at > org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:66) > at > org.apache.camel.processor.SendDynamicProcessor.lambda$process$0(SendDynamicProcessor.java:195) > I was wondering if there is a better way to do this. Maybe a shortcut for the > cached stream that just checks the size of the cache? > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (CAMEL-16365) Support ecdsa-sha2-* and ssh-ed25519 algorithms in camel-ssh
[
https://issues.apache.org/jira/browse/CAMEL-16365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313772#comment-17313772
]
Grzegorz Grzybek edited comment on CAMEL-16365 at 4/25/22 5:59 AM:
---
Fixed
[here|https://github.com/apache/camel/commit/e4f91db7c0fe631c1190556cf34815322d1dad89]
in https://github.com/apache/camel/commits/main branch.
was (Author: gzres):
Fixed
[here|https://github.com/apache/camel/commit/e4f91db7c0fe631c1190556cf34815322d1dad89]
in https://github.com/apache/camel/commits/master branch.
> Support ecdsa-sha2-* and ssh-ed25519 algorithms in camel-ssh
>
>
> Key: CAMEL-16365
> URL: https://issues.apache.org/jira/browse/CAMEL-16365
> Project: Camel
> Issue Type: Improvement
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.10.0
>
>
> Currently camel-ssh supports only {{ssh-rsa}} and {{ssh-dss}} algorithms.
> [See
> here|https://github.com/apache/camel/blob/camel-3.8.0/components/camel-ssh/src/main/java/org/apache/camel/component/ssh/SSHPublicKeyHolder.java#L155-L161].
> Apache SSHD supports EC keys through BouncyCastle without problems and EdDSA
> using net.i2p.crypto/eddsa library.
> However Camel itself can't validate such server keys.
> I have locally working version of camel-ssh which validates all these
> additional algorithms supported by OpenSSH:
> * ecdsa-sha2-nistp256
> * ecdsa-sha2-nistp384
> * ecdsa-sha2-nistp521
> * ssh-ed25519
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
