Everything makes more sense now, thank you for the detailed explanation.
--
View this message in context:
http://camel.465427.n5.nabble.com/onCompletion-not-triggerd-in-testing-tp5743163p5743559.html
Sent from the Camel - Users mailing list archive at Nabble.com.
e, now the test is working. Still, I
> find it weird that the consumer is not retrieving anything even though
> JConsole shows that the QueueSize > 0.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/onCompletion-not-triggerd-in-testing-tp574
Thank you for pointing that out for me, now the test is working. Still, I
find it weird that the consumer is not retrieving anything even though
JConsole shows that the QueueSize > 0.
--
View this message in context:
http://camel.465427.n5.nabble.com/onCompletion-not-triggerd-in-test
ID:pc-clucutar-63598-1384772199184-2:1:1:4, *lastDeliveredSequenceId:55*
>
> Even though I can see that the queueSize = 1 in JConsole, the retrieve
> operation doesn't retrieve anything and the queueSize doesn't change. The
> second call retrieves the exchange and queue
dSequenceId:55*
Even though I can see that the queueSize = 1 in JConsole, the retrieve
operation doesn't retrieve anything and the queueSize doesn't change. The
second call retrieves the exchange and queueSize becomes 0.
Any idea?
--
View this message in context:
http://camel.46542
My bad, I was looking over the libs of the project and I was tricked by a
activemq-camel library. The version is 2.7.3-fuse-00-89.
--
View this message in context:
http://camel.465427.n5.nabble.com/onCompletion-not-triggerd-in-testing-tp5743163p5743269.html
Sent from the Camel - Users mailing
t;
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/onCompletion-not-triggerd-in-testing-tp5743163p5743266.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
unit test for the whole
route, because I already have several unit tests for each processor.
--
View this message in context:
http://camel.465427.n5.nabble.com/onCompletion-not-triggerd-in-testing-tp5743163p5743266.html
Sent from the Camel - Users mailing list archive at Nabble.com.
y into Exchange and send them to the Direct
> Input
> exchange = createExchangeWithBodyAndHeader(msg,
> MessageType.END_OF_DAY);
> template.send(exchange);
>
> resultEndpoint.assertIsNotSatisfied(1000);
>
> // sending Transaction 3, which should trigger the processing of the
> E
WithBodyAndHeader(msg,
MessageType.TRANSACTION);
template.send(exchange);
// assert that we got all the messages
resultEndpoint.assertIsSatisfied(1000);
}
The syncProcessor is working fine but none of the onCompletion events get to
it.
Thanks for your support.
--
Vie
d.
I will post something tomorrow morning, maybe someone can spot the problem.
Thanks,
Cristian.
--
View this message in context:
http://camel.465427.n5.nabble.com/onCompletion-not-triggerd-in-testing-tp5743163p5743207.html
Sent from the Camel - Users mailing list archive at Nabble.com.
quot;)
> protected MockEndpoint resultEndpoint;
>
>
> Could it be that the "mock:output" is not triggering the onCompletion event?
>
> Thanks,
> Cristian.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/onCompletion-not
his is the outputEndpoint:
@EndpointInject(uri = "mock:output")
protected MockEndpoint resultEndpoint;
Could it be that the "mock:output" is not triggering the onCompletion event?
Thanks,
Cristian.
--
View this message in context:
http://camel.465427.n5.nabble.com/onCompletion-not-trig
13 matches
Mail list logo
