ay to use Spring annotations but with the advantages of
CamelSpringTestSupport (by using createRouteBuilder())?
--
Damien NICOLAS
Ok.. I forgot to add the InOut pattern on my camel consuming queue.
Le ven. 19 oct. 2018 à 09:18, Damien Nicolas a
écrit :
> up
>
> Le mar. 16 oct. 2018 à 16:40, Damien Nicolas a
> écrit :
>
>> Hello,
>>
>> I have a Springboot war with Camel routes depl
up
Le mar. 16 oct. 2018 à 16:40, Damien Nicolas a
écrit :
> Hello,
>
> I have a Springboot war with Camel routes deployed on a JBoss EAP 7.1
> server. The routes are generated dynamically and some of them have
> *concurrentConsumers
> > 1* because a route can have s
, "xxx");
try (JMSContext context =
connectionFactory.createContext(userName, password)) {
context.createProducer().send(destination, m);
...
Is the problem comes about the fact there is less header properties
generated when I create manually the headers?? or something else???
Here is the difference between the header properties of the first version
of the project and the second one <https://pastebin.com/qvahstrq>
--
Damien NICOLAS
Hello,
I would like to unit test a processor containing a service as an autowired
bean (*messageInformationService*). I would like to mock this bean to make
it return the data I want, but when I do that with Mockito, my service is
null.
*Here is my test class:*
public class
u'd
> try it with the annotation @RunWith(MockitoJUnitRunner.class) at your class.
>
> HTH,
> Christian
>
> -Ursprüngliche Nachricht-
> Von: Damien Nicolas [mailto:dmn.nico...@gmail.com]
> Gesendet: Montag, 5. November 2018 14:47
> An: users@camel.apache.org
> Betreff:
rn new StubWebServicesFacadeImpl();
> }
> ...
>
> And so on...
>
>
> Thanks,
> Valdis
>
> -Original Message-
> From: Damien Nicolas [mailto:dmn.nico...@gmail.com]
> Sent: 02 October 2018 15:47
> To: users@camel.apache.org
> Sub
he best or the most correct way of doing
> things it's been working very reliably so far for us.
>
> Regards,
> Valdis
>
> -Original Message-
> From: Damien Nicolas [mailto:dmn.nico...@gmail.com]
> Sent: 01 October 2018 10:20
> To: users@camel.apache.org
> Subject: Re
send various messages to the
> endpoints and assert the results when consuming from the output endpoints.
> What is you test setup, maybe you can provide a small sample to illustrate
> the issue you're facing?
>
> Regards,
> Valdis
>
> -Original Message-
> From: Damien N
ner - Execution of JMS
message listener failed. Caused by: [org.apache.camel.RuntimeCamelException
- org.apache.camel.ExchangeTimedOutException: The OUT message was not
received within: 2 millis due reply message with correlationID:
ID:37303433444200000000 not received.
How can I make it works without disabling jms replying?
--
Damien NICOLAS
).process(p1);
from(direct:p2).process(p2);
from(direct:p3).process(p3);
Hope this help,
Alex
On Sun, Sep 23, 2018 at 11:59 AM Damien Nicolas
wrote:
> I have several Camel routes defining a "circuit" like this (where `qx` is
> the queue number x, `px` is the processor number
Hello,
I am developping a CXF Rest service using Camel and deployed on a JBoss EAP
7.1 server.
My service works perfectly, but when I undeploy the application, the HTTP
server used for CXF is still active, so when I want to reupload my
application I get a "bind already exists..." exception.
zoran
>
> [1]
> https://github.com/wildfly-extras/wildfly-camel-examples/tree/master/camel-cxf-jaxrs
>
> On Wed, Apr 3, 2019 at 2:44 PM Damien Nicolas
> wrote:
> >
> > Hello,
> > I am developping a CXF Rest service using Camel and deployed on a JBoss
> EAP
&g
*EDIT:*
if I change
#java:jboss/datasources/test_db
by
#dataSource
I get:
org.apache.camel.RuntimeCamelException: java.lang.IllegalStateException:
Cannot obtain PGConnection
Le ven. 22 févr. 2019 à 09:25, Damien Nicolas a
écrit :
> Hello,
>
> I have a Camel backend running on a
ectly defined cause I use it with my service without
any problem.
What do i have to do to get rid of this error?
--
Damien NICOLAS
Hello,
I was using dynamicRouter to compute destination of messages through my JMS
queues routes.
Now, I want to replace these JMS queue routes by Kafka topics and still
using dynamicRouter to determine which route should consume a particular
messages.
*example:*
Hello,
I am trying Camel (2.21.0) with Kafka and something has not the behaviour
that I want:
I have a cluster of 3 Kafka nodes (1 leader, 2 for replication) for 1
partition and 1 topic, when I produce a message in my system, it is
correctly consumed with the Camel components.
But, when I kill
Hello,
I am trying to inject a message in my camel business with the JMX API of
Artemis, with the method "sendTextMessage".
I added few personal headers on the message for my intern routing and
nothing else.
The principle of my business is the following :
If a my server is down (JBoss EAP 7.1),
up
Le ven. 26 juil. 2019 à 16:08, Damien Nicolas a
écrit :
> Hmmm actually, if I add a queue, it just move the problem. Any idea?
>
> Le ven. 26 juil. 2019 à 14:46, Damien Nicolas a
> écrit :
>
>> Hello,
>> I have multiple sequential queues in InOut pattern,
Hello,
I have a set of processor and queue in this design:
q1 -> p1 -> q2 -> p2 -> ... -> qn -> pn
My queues are in InOut exchange pattern. I would like to know if it is
possible to get the ack for a queue after each processor consumption,
instead of having that after the last consumer (pn)?
Hello,
I have multiple sequential queues in InOut pattern, each queue leads to one
processor.
If a processor takes too much time for a treatment, I would like that the
request-reply detects a timeout and send a timeout exception.
The timeout with "*CamelJmsRequestTimeout*" works but only for the
Writing my problem helps me to figure out how to solve it:
the message in q1 is injected from Spring and no queue for reply was
defined. I changed the exchange pattern of the q1 to InOnly, and now it
works.
Le ven. 26 juil. 2019 à 14:46, Damien Nicolas a
écrit :
> Hello,
> I have mu
Hmmm actually, if I add a queue, it just move the problem. Any idea?
Le ven. 26 juil. 2019 à 14:46, Damien Nicolas a
écrit :
> Hello,
> I have multiple sequential queues in InOut pattern, each queue leads to
> one processor.
> If a processor takes too much time for a treatment,
Hello,
I have an exception handler on a route of queue. If I got an exception, I
want to put the exchange in a DLQ and stop totally the exchange.
But, I put the message in a DLQ, after x seconds I got an
ExchangeTimedOutException. I want to get rid of this. How can i do that?
Here is a sample of
Hello,
I need to restart the camel context with a quartz at fixed interval.
But when I do context.stop() and then context.start() inside quartz
processing; the context stop but doesnt start again...
Also, when I remotely invoke the JMX camel restart, it works.
Is this a normal behaviour?
Thanks.
25 matches
Mail list logo