Re: Can we use custom socket connection in RabbitMQ camel component
what type of proxy are you using? are you able to make connection to RabbitMQ using Proxy using Java outside of Camel program? have you reviewed https://www.rabbitmq.com/networking.html#proxy-protocol ચિરાગ/चिराग/Chirag -- Sent from My Gmail Account On Thu, Nov 10, 2022 at 4:55 AM N Venkatesh wrote: > > Classification: Confidential > Hi Team, > > Can you please help us for below request. > > Regards, > Venkatesh > > From: N Venkatesh > Sent: Wednesday, November 9, 2022 11:22 AM > To: users@camel.apache.org > Cc: Iliyas Shaik ; Santosh Kumar Mohapatra > ; Chetan Kumar Chauhan > ; Chavan Rohit Shankar > > Subject: Can we use custom socket connection in RabbitMQ camel component > > Classification: Confidential > Hi Team, > > We are trying to connect RabbitMQ server connection through existing camel > component using customized socket connection. Here we want to supply proxy > host and proxy port via customized socket connection object. > > Can you please tell us, RabbitMQ camel component will support customized > socket connection . > > We tried below approach using java code: > > SocketConfigurator socketConfigurator = > SocketConfigurators.defaultConfigurator(); >socketConfigurator.configure(customSocket); > > > endpoint.getConnectionFactory().setSocketConfigurator(socketConfigurator); > > > Note: > endpoint : it is a existing RabbitMQ camel component endpoint > (https://camel.apache.org/components/3.18.x/rabbitmq-component.html) > customSocket : it is a customized java socket object from java.net.Socket > package. > > Regards, > Venkatesh > ::DISCLAIMER:: > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses > in transmission. The e mail and its contents (with or without referred > errors) shall therefore not attach any liability on the originator or HCL or > its affiliates. Views or opinions, if any, presented in this email are solely > those of the author and may not necessarily reflect the views or opinions of > HCL or its affiliates. Any form of reproduction, dissemination, copying, > disclosure, modification, distribution and / or publication of this message > without the prior written consent of authorized representative of HCL is > strictly prohibited. If you have received this email in error please delete > it and notify the sender immediately. Before opening any email and/or > attachments, please check them for viruses and other defects. >
Re: [VOTE] Release Apache Camel K 1.10.3 and Camel K Runtime 1.15.2
+1 Thanks Andrea! On Fri, Nov 11, 2022 at 6:31 PM Andrea Cosentino wrote: > Hello, > > This is a combined vote to release Apache Camel K 1.10.3 and Camel K > Runtime > 1.15.2. > > We are upgrading to Camel 3.18.3 and Camel-Kamelets 0.9.3, this means > Camel-Quarkus will be updated to 2.13.1. > > Runtime source files: > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.15.2/ > Runtime staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1495 > Runtime Tag: > > https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.15.2 > > Camel K release files: > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.10.3/ > Camel K Tag: > > https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.10.3 > > Staging container image repository: > https://hub.docker.com/r/camelk/camel-k/tags > > It's possible to install all staging artifacts with a single command: > > kamel install --operator-image=camelk/camel-k:1.10.3 --maven-repository= > https://repository.apache.org/content/repositories/orgapachecamel-1495 > --olm=false > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binary as Apache Camel K 1.10.3 and > Apache Camel K Runtime > 1.15.2 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Tadayoshi Sato
Re: [VOTE] Release Apache Camel K 1.10.3 and Camel K Runtime 1.15.2
+1 > Andrea Cosentino hat am 11.11.2022 10:31 CET geschrieben: > > > Hello, > > This is a combined vote to release Apache Camel K 1.10.3 and Camel K Runtime > 1.15.2. > > We are upgrading to Camel 3.18.3 and Camel-Kamelets 0.9.3, this means > Camel-Quarkus will be updated to 2.13.1. > > Runtime source files: > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.15.2/ > Runtime staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1495 > Runtime Tag: > https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.15.2 > > Camel K release files: > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.10.3/ > Camel K Tag: > https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.10.3 > > Staging container image repository: > https://hub.docker.com/r/camelk/camel-k/tags > > It's possible to install all staging artifacts with a single command: > > kamel install --operator-image=camelk/camel-k:1.10.3 --maven-repository= > https://repository.apache.org/content/repositories/orgapachecamel-1495 > --olm=false > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binary as Apache Camel K 1.10.3 and > Apache Camel K Runtime > 1.15.2 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino
[VOTE] Release Apache Camel K 1.10.3 and Camel K Runtime 1.15.2
Hello, This is a combined vote to release Apache Camel K 1.10.3 and Camel K Runtime 1.15.2. We are upgrading to Camel 3.18.3 and Camel-Kamelets 0.9.3, this means Camel-Quarkus will be updated to 2.13.1. Runtime source files: https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.15.2/ Runtime staging repository: https://repository.apache.org/content/repositories/orgapachecamel-1495 Runtime Tag: https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.15.2 Camel K release files: https://dist.apache.org/repos/dist/dev/camel/camel-k/1.10.3/ Camel K Tag: https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.10.3 Staging container image repository: https://hub.docker.com/r/camelk/camel-k/tags It's possible to install all staging artifacts with a single command: kamel install --operator-image=camelk/camel-k:1.10.3 --maven-repository= https://repository.apache.org/content/repositories/orgapachecamel-1495 --olm=false Please test this release candidate and cast your vote. [ ] +1 Release the binary as Apache Camel K 1.10.3 and Apache Camel K Runtime 1.15.2 [ ] -1 Veto the release (provide specific comments) The vote is open for at least 72 hours. Here's my +1. Thanks, Andrea Cosentino
RE: Re: Offset in OffsetRepositoy doesn't get increase after manual commit
Hi Otavio, Clays,
Thank you very much for your hands. I tried 3.18.3. It didn't increase the
offset.
Best regards,
Yuttana
On 2022/11/10 06:36:08 Otavio Rodolfo Piske wrote:
> Hi, before I go ahead and investigate this further ... Could you possibly
> try with Camel 3.18.3? We have made a bunch of fixes for Kafka in 3.18.3.
>
> Kind regards
>
> On Wed, Nov 9, 2022 at 3:56 PM Claus Ibsen wrote:
>
> > Hi
> >
> > I am not sure, there are some improvements and refactorings going on in
> > camel-kafka and offset management.
> > I think Otavio would be better to help look into this.
> >
> > On Wed, Nov 9, 2022 at 11:36 AM Sangchoei, Yuttana
> > wrote:
> >
> > > Hi All,
> > >
> > > I'm upgrading Camel from 3.16 to 3.17 and found a problem that
> > > OffsetRepository didn't get update after manual commit.
> > > It is a Spring boot project and MemoryStateRepository as follows.
> > >
> > > @Bean
> > > public MemoryStateRepository offsetRepo() {
> > > MemoryStateRepository stateRepository = new
> > > MemoryStateRepository();
> > > stateRepository.setState(topic + "/0", "");
> > > return stateRepository;
> > > }
> > >
> > > Here is the method I use when commit:
> > >
> > > private void commitOffsetToKafka(Exchange exchange) {
> > > KafkaManualCommit manual =
> > > exchange.getIn().getHeader(KafkaConstants.MANUAL_COMMIT,
> > > KafkaManualCommit.class);
> > > manual.commit();
> > > }
> > >
> > > Here is my Kafka endpoint
> > >
> > > kafka:integration_test _topic?brokers=127.0.0.1:41478
> > >
> > &autoCommitEnable=false&allowManualCommit=true&seekTo=beginning&maxPollRecords=2&groupId=ANE&autoOffsetReset=earliest&offsetRepository=#offsetRepo&kafkaManualCommitFactory=#class:org.apache.camel.component.kafka.consumer.DefaultKafkaManualCommitFactory
> > >
> > > It is working fine in 3.16. When DefaultkafkaManualSyncCommit.commit() is
> > > invoked. The offsetRepository.setState() get invoked so the offset
> > > increased.
> > > However, in 3.17, DefaultkafkaManualSyncCommit.commit() doesn't have a
> > > reference to offsetRepository so the offset in offsetRepository won't get
> > > increased.
> > >
> > > Is this a bug or there is a different way to get the offset after
> > > committing. Could you please suggest what I should do to test if the
> > offset
> > > get increased after manual commit?
> > >
> > > Best regards,
> > > Yuttana Sangchoei
> > >
> > > This e-mail and any attachments to it (the "Communication") is, unless
> > > otherwise stated, confidential, may contain copyright material and is for
> > > the use only of the intended recipient. If you receive the Communication
> > in
> > > error, please notify the sender immediately by return e-mail, delete the
> > > Communication and the return e-mail, and do not read, copy, retransmit or
> > > otherwise deal with it. Any views expressed in the Communication are
> > those
> > > of the individual sender only, unless expressly stated to be those of
> > > Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or
> > any
> > > of its related entities including ANZ Bank New Zealand Limited (together
> > > "ANZ"). ANZ does not accept liability in connection with the integrity of
> > > or errors in the Communication, computer virus, data corruption,
> > > interference or delay arising from or in respect of the Communication.
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>
Get Outlook for Android
This e-mail and any attachments to it (the "Communication") is, unless
otherwise stated, confidential, may contain copyright material and is for the
use only of the intended recipient. If you receive the Communication in error,
please notify the sender immediately by return e-mail, delete the Communication
and the return e-mail, and do not read, copy, retransmit or otherwise deal with
it. Any views expressed in the Communication are those of the individual sender
only, unless expressly stated to be those of Australia and New Zealand Banking
Group Limited ABN 11 005 357 522, or any of its related entities including ANZ
Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in
connection with the integrity of or errors in the Communication, computer
virus, data corruption, interference or delay arising from or in respect of the
Communication.
RE: Re: Offset in OffsetRepositoy doesn't get increase after manual commit
Hi Otavio, Claus,
Thank you very much for your hands. I tried 3.18.3. It didn’t increase the
offset.
Best regards,
Yuttana
On 2022/11/10 06:36:08 Otavio Rodolfo Piske wrote:
> Hi, before I go ahead and investigate this further ... Could you possibly
> try with Camel 3.18.3? We have made a bunch of fixes for Kafka in 3.18.3.
>
> Kind regards
>
> On Wed, Nov 9, 2022 at 3:56 PM Claus Ibsen wrote:
>
> > Hi
> >
> > I am not sure, there are some improvements and refactorings going on in
> > camel-kafka and offset management.
> > I think Otavio would be better to help look into this.
> >
> > On Wed, Nov 9, 2022 at 11:36 AM Sangchoei, Yuttana
> > wrote:
> >
> > > Hi All,
> > >
> > > I'm upgrading Camel from 3.16 to 3.17 and found a problem that
> > > OffsetRepository didn't get update after manual commit.
> > > It is a Spring boot project and MemoryStateRepository as follows.
> > >
> > > @Bean
> > > public MemoryStateRepository offsetRepo() {
> > > MemoryStateRepository stateRepository = new
> > > MemoryStateRepository();
> > > stateRepository.setState(topic + "/0", "");
> > > return stateRepository;
> > > }
> > >
> > > Here is the method I use when commit:
> > >
> > > private void commitOffsetToKafka(Exchange exchange) {
> > > KafkaManualCommit manual =
> > > exchange.getIn().getHeader(KafkaConstants.MANUAL_COMMIT,
> > > KafkaManualCommit.class);
> > > manual.commit();
> > > }
> > >
> > > Here is my Kafka endpoint
> > >
> > > kafka:integration_test _topic?brokers=127.0.0.1:41478
> > >
> > &autoCommitEnable=false&allowManualCommit=true&seekTo=beginning&maxPollRecords=2&groupId=ANE&autoOffsetReset=earliest&offsetRepository=#offsetRepo&kafkaManualCommitFactory=#class:org.apache.camel.component.kafka.consumer.DefaultKafkaManualCommitFactory
> > >
> > > It is working fine in 3.16. When DefaultkafkaManualSyncCommit.commit() is
> > > invoked. The offsetRepository.setState() get invoked so the offset
> > > increased.
> > > However, in 3.17, DefaultkafkaManualSyncCommit.commit() doesn't have a
> > > reference to offsetRepository so the offset in offsetRepository won't get
> > > increased.
> > >
> > > Is this a bug or there is a different way to get the offset after
> > > committing. Could you please suggest what I should do to test if the
> > offset
> > > get increased after manual commit?
> > >
> > > Best regards,
> > > Yuttana Sangchoei
> > >
> > > This e-mail and any attachments to it (the "Communication") is, unless
> > > otherwise stated, confidential, may contain copyright material and is for
> > > the use only of the intended recipient. If you receive the Communication
> > in
> > > error, please notify the sender immediately by return e-mail, delete the
> > > Communication and the return e-mail, and do not read, copy, retransmit or
> > > otherwise deal with it. Any views expressed in the Communication are
> > those
> > > of the individual sender only, unless expressly stated to be those of
> > > Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or
> > any
> > > of its related entities including ANZ Bank New Zealand Limited (together
> > > "ANZ"). ANZ does not accept liability in connection with the integrity of
> > > or errors in the Communication, computer virus, data corruption,
> > > interference or delay arising from or in respect of the Communication.
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>
RE: Re: Offset in OffsetRepositoy doesn't get increase after manual commit
Hi Otavio, Claus,
Thank you very much for your hands. I tried upgrading to 3.18.3. I didn't
increase the offset.
Best regards,
Yuttana
On 2022/11/10 06:36:08 Otavio Rodolfo Piske wrote:
> Hi, before I go ahead and investigate this further ... Could you
> possibly try with Camel 3.18.3? We have made a bunch of fixes for Kafka in
> 3.18.3.
>
> Kind regards
>
> On Wed, Nov 9, 2022 at 3:56 PM Claus Ibsen wrote:
>
> > Hi
> >
> > I am not sure, there are some improvements and refactorings going on
> > in camel-kafka and offset management.
> > I think Otavio would be better to help look into this.
> >
> > On Wed, Nov 9, 2022 at 11:36 AM Sangchoei, Yuttana
> > wrote:
> >
> > > Hi All,
> > >
> > > I'm upgrading Camel from 3.16 to 3.17 and found a problem that
> > > OffsetRepository didn't get update after manual commit.
> > > It is a Spring boot project and MemoryStateRepository as follows.
> > >
> > > @Bean
> > > public MemoryStateRepository offsetRepo() {
> > > MemoryStateRepository stateRepository = new
> > > MemoryStateRepository();
> > > stateRepository.setState(topic + "/0", "");
> > > return stateRepository;
> > > }
> > >
> > > Here is the method I use when commit:
> > >
> > > private void commitOffsetToKafka(Exchange exchange) {
> > > KafkaManualCommit manual =
> > > exchange.getIn().getHeader(KafkaConstants.MANUAL_COMMIT,
> > > KafkaManualCommit.class);
> > > manual.commit();
> > > }
> > >
> > > Here is my Kafka endpoint
> > >
> > > kafka:integration_test _topic?brokers=127.0.0.1:41478
> > >
> > &autoCommitEnable=false&allowManualCommit=true&seekTo=beginning&maxP
> > ollRecords=2&groupId=ANE&autoOffsetReset=earliest&offsetRepository=#
> > offsetRepo&kafkaManualCommitFactory=#class:org.apache.camel.componen
> > t.kafka.consumer.DefaultKafkaManualCommitFactory
> > >
> > > It is working fine in 3.16. When
> > > DefaultkafkaManualSyncCommit.commit() is invoked. The
> > > offsetRepository.setState() get invoked so the offset increased.
> > > However, in 3.17, DefaultkafkaManualSyncCommit.commit() doesn't
> > > have a reference to offsetRepository so the offset in
> > > offsetRepository won't get increased.
> > >
> > > Is this a bug or there is a different way to get the offset after
> > > committing. Could you please suggest what I should do to test if
> > > the
> > offset
> > > get increased after manual commit?
> > >
> > > Best regards,
> > > Yuttana Sangchoei
> > >
> > > This e-mail and any attachments to it (the "Communication") is,
> > > unless otherwise stated, confidential, may contain copyright
> > > material and is for the use only of the intended recipient. If you
> > > receive the Communication
> > in
> > > error, please notify the sender immediately by return e-mail,
> > > delete the Communication and the return e-mail, and do not read,
> > > copy, retransmit or otherwise deal with it. Any views expressed in
> > > the Communication are
> > those
> > > of the individual sender only, unless expressly stated to be those
> > > of Australia and New Zealand Banking Group Limited ABN 11 005 357
> > > 522, or
> > any
> > > of its related entities including ANZ Bank New Zealand Limited
> > > (together "ANZ"). ANZ does not accept liability in connection with
> > > the integrity of or errors in the Communication, computer virus,
> > > data corruption, interference or delay arising from or in respect of the
> > > Communication.
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>
This e-mail and any attachments to it (the "Communication") is, unless
otherwise stated, confidential, may contain copyright material and is for the
use only of the intended recipient. If you receive the Communication in error,
please notify the sender immediately by return e-mail, delete the Communication
and the return e-mail, and do not read, copy, retransmit or otherwise deal with
it. Any views expressed in the Communication are those of the individual sender
only, unless expressly stated to be those of Australia and New Zealand Banking
Group Limited ABN 11 005 357 522, or any of its related entities including ANZ
Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in
connection with the integrity of or errors in the Communication, computer
virus, data corruption, interference or delay arising from or in respect of the
Communication.
