>Is your JBI endpoint a Binding Component that sends the exchange on a JBI
based workflow? Is your JBI flow up and running?

Yes, the JBI is working, but it returns JBI Fault which is translated into 
FaultException for Camel.


I've change the Camel flow so that it uses doTry() instead of continued(true)
And now it works completely..


> Also, please set your log level to DEBUG, use a Tracer component to trace
your flow and check to see how your exception is being handled and how
messages are flowing through Camel/JBI.

I've debugged the code and I see that error is thrown after second invocation 
of 
org.apache.servicemix.camel.CamelConsumerEndpoint.processReponse(...)
So it is a bug in Camel... I'll try to prepare complete test to show it.



-- 
Regards,
Mateusz Nowakowski

-----Original Message-----
From: Ashwin Karpe [mailto:aka...@fusesource.com] 
Sent: Wednesday, June 01, 2011 7:47 PM
To: users@camel.apache.org
Subject: Re: Second error handed by continued(true) doesn't work

Hi,

JBI flows/endpoints use an NMR for communication between the components, and
the NMR in JBI by default is a SEDA (java.util.concurrent.BlockingQueue)
based implementation.

Is your JBI endpoint a Binding Component that sends the exchange on a JBI
based workflow? Is your JBI flow up and running?

Also, please set your log level to DEBUG, use a Tracer component to trace
your flow and check to see how your exception is being handled and how
messages are flowing through Camel/JBI.

http://camel.apache.org/tracer.html http://camel.apache.org/tracer.html 

Cheers,

Ashwin...

-----
---------------------------------------------------------
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com 

Blog: http://opensourceknowledge.blogspot.com 
CamelOne 2011: http://fusesource.com/camel2011 
---------------------------------------------------------
--
View this message in context: 
http://camel.465427.n5.nabble.com/Second-error-handed-by-continued-true-doesn-t-work-tp4445730p4445908.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to