On 24 May 2013 16:15, Claus Ibsen wrote:
> There is no bug on the seda consumer.
Claus, you are right as always, there is no bug.
I was referring to line 196 from SedaConsumer [1]
If an exception happens during processing, it is logged and not propagated
back, but that is never the case, beca
Ah, I see. It is the a-sync nature of stub that causes the difference. I will
look into how I can use stub and still get the exception thrown from the
produces (will look into receive).
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/Why-doesn-t-the-stub-component-thr
There is no bug on the seda consumer. He sends a InOnly message.
So the consumer can only "handle" the exception itself by logging it.
If he does a InOut then the producer template will wait for the reply
message, and because it failed with the exception, the reply message is the
exception.
On F
Hi,
can you try to set the exception on the exchange instead of throwing it?
If that's the case then I think there might a bug in SedaConsumer which
propagates back exceptions on the exchange but doesn't propagate thrown
exceptions.
Bilgin
On 24 May 2013 12:31, dancerjohn wrote:
>
> I disagre
Hi
Study the EIPs and components again. And the difference between a direct
component vs a stub/seda (eg sync vs async) and the InOnly vs InOut.
And the send vs request methods on the producer template.
They all have an influence on what happens.
Also for testing purpose you may wanna take a l
I disagree... the javadoc for ProducerTemplate.sendBody() states "Notice:
that if the processing of the exchange failed with an Exception it is thrown
from this method as a CamelExecutionException with the caused exception
wrapped.". So if an exception is thrown during processing sendBody should
t
Hi
Read the javadoc API on the producer template and the methods you use,
eg sendBody vs requestBody.
eg its about InOnly vs InOut messaging style.
The eips
http://camel.apache.org/event-message.html
http://camel.apache.org/request-reply.html
On Thu, May 23, 2013 at 8:15 PM, dancerjohn wrote:
>
I am writing a test for my error handling. The route I am testing uses JMS
and therefore has URL properties that are not compatible with the direct
component. The way I have it set up is that I pass the following to the
Route Builder ("jms:queue:myqueue") and then it adds the additional URL
propert
