Hi Andrea,
Thanks a lot for the suggestion, it helped fix the issue, I can see the plugin.
Regards,
Gururaj
-Original Message-
From: Andrea Cosentino
Sent: dinsdag 15 maart 2022 10:18
To: users@camel.apache.org
Subject: Re: Camel RabbitMQ sink connector plugin is not getting added in
You don't have to copy the jar, you need to explode the tar.gz provided:
https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-rabbitmq-kafka-connector/0.11.5/camel-rabbitmq-kafka-connector-0.11.5-package.tar.gz
Each of the connectors from camel-kafka-connector, needs to live
À : users@camel.apache.org
Objet : Re: [camel-rabbitmq] - InOut pattern and temporary queues
On Wed, Jun 9, 2021 at 4:40 PM FERRY, Guillaume
wrote:
>
> Hi folks,
>
> Here's a quick follow-up on my work with camel-rabbitmq.
> So far, everything runs quite smoothly, but in some part
;
> Regards,
> Guillaume.
>
> De : FERRY, Guillaume
> Envoyé : mercredi 12 mai 2021 15:33
> À : users@camel.apache.org
> Objet : RE: [camel-rabbitmq] - InOut pattern and temporary queues
>
> Hi Jean-Baptiste,
>
> Thanks for the
Regards,
Guillaume.
De : FERRY, Guillaume
Envoyé : mercredi 12 mai 2021 15:33
À : users@camel.apache.org
Objet : RE: [camel-rabbitmq] - InOut pattern and temporary queues
Hi Jean-Baptiste,
Thanks for the details, I'll let you know if something goes wrong with
temporary queues, so f
eses queues, then !
>
> Best regards,
> Guillaume.
>
> De : ski n
> Envoyé : mardi 11 mai 2021 15:38
> À : users@camel.apache.org
> Objet : Re: [camel-rabbitmq] - InOut pattern and temporary queues
>
> When working with a Request-Reply p
gt; Best regards,
> Guillaume.
>
> De : ski n
> Envoyé : mardi 11 mai 2021 15:38
> À : users@camel.apache.org
> Objet : Re: [camel-rabbitmq] - InOut pattern and temporary queues
>
> When working with a Request-Reply pattern the reply message needs to send
> to a sec
Hi Raymond,
Thanks a lot for this crystal clear answer.
I'll let Camel handle theses queues, then !
Best regards,
Guillaume.
De : ski n
Envoyé : mardi 11 mai 2021 15:38
À : users@camel.apache.org
Objet : Re: [camel-rabbitmq] - InOut pattern and temporary q
When working with a Request-Reply pattern the reply message needs to send
to a second reply queue. The InOut pattern mostly goes like this:
1) Producer send request with correlationid to a queue
2) Consumer receives the message and send a reply to the reply queue
3) Producer matches the reply mess
Hi Phil,
I presume that the camel-rabbitmq component is picking up and using this
ConnectionFactory:
...
So I would see if SSL needs to be configured there, and not on the Camel
endpoint. Try setting the "useSslProtocol" [1] property on the
ConnectionFactory itself? (i.e. set it as a property a
Hi Mahesh,
The error above is related to the initial creation of the Camel route, is
pretty weird though that it can't parse the options although you
correctly spelled them. Which version of Camel do you use?
Also, in regards camel stomp with RabbitMQ, I honestly have no idea if it
is going to wor
with the header expression instead of the body expression and it
still wouldn't populate the header.
From: Valdis Andersons
Sent: 05 November 2019 21:54
To: users@camel.apache.org
Subject: RE: camel-rabbitmq sheduled route acks all messages when shutting down
CAUTION: This email originated fro
Hi All,
Did a bit of digging and the issue appears to be coming from upstream on the
producer. Here is the route configuration for it:
from("direct:archive")
.log("Receiving ${body}")
.aggregate(header("aggregationkey"))
.aggregationStrategyRef(aggregationStrategy)
.aggregationRepositoryRef(repo
ary 2019 12:18
To: users@camel.apache.org
Subject: Re: camel-rabbitmq automated recovery
Hi
Have you been able to try with a newer release such as Camel 2.23.0, as the
camel-rabbitmq component etc may been improved / bug fixed since that version
you are using.
On Mon, Nov 12, 2018 at 5:34 PM Valdis Ander
Hi
Have you been able to try with a newer release such as Camel 2.23.0,
as the camel-rabbitmq component etc may been improved / bug fixed
since that version you are using.
On Mon, Nov 12, 2018 at 5:34 PM Valdis Andersons
wrote:
>
> Hi All,
>
>
>
> Hoping someone with more experience with Rabbit
Never mind, we figured it out. Turns out mirroring is configured on the broker
side since RabbitMQ 3.0 (:facepalm).
Once the primary went down Camel couldn't do anything with the in-flight
messages anymore since the queues were not mirrored on the secondary vm. So the
below is probably a very ex
Ok I figured out what the issue is.
You must explicitly set the exchangepattern to InOut otherwise the replyto
headers and queues are not created by default.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-RabbitMQ-tp5781455p5781457.html
Sent from the Camel - Users mai
anybody can help?
Thanks,
Jeffrey
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-rabbitmq-only-receive-one-message-when-autoAck-is-false-tp5758034p5758121.html
Sent from the Camel - Users mailing list archive at Nabble.com.
opened https://issues.apache.org/jira/browse/CAMEL-7967
thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-rabbitmq-logging-exceptions-as-debug-tp5757936p5758069.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
Yeah that sounds like we should improve this. Feel free to log a JIRA ticket
http://camel.apache.org/support
On Thu, Oct 23, 2014 at 11:08 AM, Marco Crivellaro
wrote:
> Hi,
> I am using Camel 2.14.0
> Connecting to RabbitMQ using camel-rabbitmq I've noticed that no ERROR is
> logged if the co
Thanks Claus Ibsen for looking into this. Let me know when this fix will be
available.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-RabbitMQ-acknowledges-event-though-autoAck-is-set-to-false-and-there-is-an-exception-in-the-roe-tp5756207p5756229.html
Sent from the Ca
Hi
Yeah you are right I am fixing this now.
On Mon, Sep 8, 2014 at 8:35 PM, blr_developer wrote:
> Camel RabbitMQ component acknowledges the message even though the autoAck is
> set to false and there is an exception in the route. I don't know if I am
> doing anything wrong.
>
> My guess is that
Hi,
If you set the option of autoAck is false, Camel will send the acknowledgement
to RabbitMQ when the exchange is processed.
If you want to do it in the batch mode, you may need to change the
RabbitMQConsumer, but I’m not sure how can get the channel if you want to send
the acknowledgement
Thank you Willem. After upgrading to 2.13.0 and adding BridgeEndpoint=true to
the URI solved this issue.
I ended up using "addresses" as we have 2 RabbitMQ in a cluster.
Thanks,
Muthu
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-rabbitmq-routing-issue-tp5744371p574
Hi,
If you use camel 2.13.0, you can specify the option of BridgeEndpoint=true,
then camel rabbitmq can ignore the message header which are set by camel
rabbitmq consumer.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.itey
Hi Willem,
As I removed all of the rabbitmq headers using this pattern "rabbitmq.*",
This ended up removed "rabbitmq.CONTENT_TYPE" and this is causing trouble
in converting the message to a Java Object on the consumer.
Instead of removing all the rabbitmq headers, is there one or two specific
ra
5.345.1656
ext 51656 (in office)
johcl...@adobe.com
3900 Adobe Way
Lehi, UT 84043 USA
www.adobe.com
-Original Message-
From: John H. Clark
Sent: Wednesday, March 12, 2014 10:40 AM
To: users@camel.apache.org
Cc: 'willem.ji...@gmail.com'
Subject: RE: camel-rabbitmq autoack=false
l.apache.org
Subject: Re: camel-rabbitmq autoack=false
Hi,
We have some autoack related issue in camel 2.12.1.
I just checked latest release camel 2.12.3’s code, the autoAck option is set
rightly.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspo
Hi,
We have some autoack related issue in camel 2.12.1.
I just checked latest release camel 2.12.3’s code, the autoAck option is set
rightly.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willem
Thanks Willem
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-rabbitmq-routing-issue-tp5744371p5744410.html
Sent from the Camel - Users mailing list archive at Nabble.com.
In camel we have a rule that message header can override the setting of
endpoint.
When consumer receives the message, it puts some headers which key is start
with “rabbitmq.”. As the producer always prefer the message header setting over
the endpoint setting, the producer sends the message to g
Thanks Willem for the quick response.
Your suggestion resolved my issue. Can you please explain why this issue
happened and how this fixed it?
Thanks,
Muthu
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-rabbitmq-routing-issue-tp5744371p5744374.html
Sent from the Cam
You need to remove the message header which is start with “rabbitmq.” just like
this
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On December 5, 2013 a
I just checked the code, for the dynamicRouter the endpoint is cached, but the
producer is not cached.
Please feel free to create a JIRA about it.
BTW, I want to know the difference between the RabbitMQ connection and channel
to decide if we need to create channel per producer.
--
Willem Jian
Thanks Willem,
I think creating channel per request is not a problem, but creating is
connection for each request will be a problem.
Do we require to create a producer each time if we encounter endpoint
(having same identifier) declaration. If this is the expected behavior
then yes we can have c
I just checked the code of RabbitMQProducer, it create new connection and
channel when creating the producer.
I think we need to cache the connection or channel to avoid creating a new
connection per new Producer.
In you case if there is no much of RabbitMQ Endpoint, you can setup the route
lik
Hi
Is it only rabbitmq endpoints as producers you use (eg .to rabbit) and
not consumers?
1)
Some components has an lazyCreateSession option that will only create
the connection on demand. So in that case the route will be able to
startup, and on 1st message the producer will create a connection a
I don’t see any errors in the logs, it’s only info/debug logs (given below).
I even created the exchange (direct durable) and the queue (durable)
manually. This only helped in establishing the connection and also the idle
channel was created from camel but no message was published to the queue. I
u
Camel uses the rabbitmq libs, v3.1.3, so should support 0-9-1/0-9/0-8
protocols.
The camel producer will not create the exchange/queue.
Do you not see any exceptions in the log?
On Thu, Oct 17, 2013 at 8:53 AM, tsv wrote:
> Hi Reji,
> The queue name is in the endpoint option '&queue=myqueue&'.
Hi Reji,
The queue name is in the endpoint option '&queue=myqueue&'. By removing
noop=true did not help, it’s behaving the same, rabbitmq connection is
opened and no channel, exchange, queue or message is created. I even
replaced RabbitMQ Client version to:2.8.2 from: 3.1.5 this also has no
effect.
Hey
What is the name of the queue? And also try removing noop =true and let me
know how it behaves
cheers
Reji
"tsv [via Camel]" wrote:
>
>
>Greetings,
>
>I am using camel-rabbitmq component to publish messages to rabbitmq broker.
>But I see my route opens a connection in rabbitmq server (vie
Hi
Could you tell me where have you mentioned the name of the Queue?
Alternatively please let me know how it behaves when you remove noop-true
Cheers
Reji
On Wed, Oct 16, 2013 at 3:45 PM, tsv [via Camel] <
ml-node+s465427n5741707...@n5.nabble.com> wrote:
> Greetings,
>
> I am using camel-rabbi
Hi Willem,
Thanks for your quick reply.
Thanks,
Tushar
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-RabbitMQ-from-2-12-snapshot-missing-parameter-type-direct-tp5738013p5738026.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
Camel RabbitMQ doesn't support to set the type currently.
The type value is direct, with the code like this:
channel.exchangeDeclare(endpoint.getExchangeName(),
"direct",
endpoint.isDurable(),
endpoint.isAutoDelete(),
new HashMap());
I just found the below code doesn't follow the configura
Hi,
Thanks for reporting it. I just filled a JIRA[1] and committed a fix for it.
[1]https://issues.apache.org/jira/browse/CAMEL-6617
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (
I ran into this as well and can be worked around by adding this between your
from and to:
.setHeader(RabbitMQConstants.EXCHANGE_NAME).constant("A")
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-rabbitmq-tp5
Hi
Thanks for reporting. I am fixing this on master.
On Tue, Jul 30, 2013 at 12:43 PM, kiranreddykasa wrote:
> Hi
>
> I tried to use camel-rabbitmq component from 2.12 snapshot.
>
> Here is my route.
>
>
> from("netty:tcp://0.0.0.0:7000?textline=true").to("rabbitmq://localhost/A?routingKey=B&u
47 matches
Mail list logo
