Hi Stevenson,
thanks a lot again. Yes, I force the failure in the CRM_LoginRoute that
throws the exception to main route where is defined a DLQ Error Handler.
Redelivery Policy doesn't work because attempts are always 1. Following a
piece of log
08:46:16,113 | INFO | rmalizedTickets] | DataWithI
Thanks for the addition configuration and logs.
Are you getting a message history in the logs that identifies exactly where the
failure occurs?
Without the message history, I’m guessing a little - but it appears the failure
is in the CRM_LoginRoute on the inOut call to the jetty URI.
I put tog
Hi Stevenson,
first of all thanks a lot for your reply. ErrorHandler definitions:
Logs simulating a ConnectException,
First Attempt
16:54:26,116 | WARN | erRedeliveryTask | HttpExchange
Can you share the configuration of the dlqErrorHandler, as well as a little
more of the log - I’d like to see the exchange history.
Quinn Stevenson
> On Jan 28, 2016, at 4:28 AM, Michele
> wrote:
>
>
>
>
>
You can still throw exceptions by putting the exception in the exchange object.
Exchange.setException(..);
Elvio
-Original Message-
From: Richa [mailto:rsinha2...@gmail.com]
Sent: 15 July 2014 15:40
To: users@camel.apache.org
Subject: Error handling in aggregation strategy
Hi,
I have
Thanks all for your replies. I have taken Kraythe's advice. Rather than just
putting a try catch in createSimpleProduct, in my route I did some splitting
so that the createSimpleProduct gets called for each item.
I guess I could have just put a try catch in but this way seems to be more
of a camel
Put a splitter in the route to split up the list and forward the split
exchanges to route b. In route b handle the items and if one fails you put
it in the DLQ, and ignore it. Another route can aggregate to do reporting
if it wants.
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA*
*Author of:
Well, if I don't misunderstand the situation, you could just use try/catch
inside "createSimpleProduct" method to skip the bad items.
Regards
Stephan
On Thu, Dec 5, 2013 at 12:33 PM, richie.rivi...@gmail.com <
richie.rivi...@gmail.com> wrote:
> Hi All,
>
> I've got a question about error handli
Hi
You have to set asyncConsumer=true on the JMS endpoint.
See details at
http://camel.apache.org/jms
On Tue, Jul 23, 2013 at 9:12 AM, Marco Westermann wrote:
> Hi,
>
> I have a route with an errorHandler configured. I set it to redeliver async.
> But when an error occures the remaining message
You can add the concurrentConsumers option to the JMS consumer. Camel
will then keep consuming messages in other threads even if the first
one is busy doing the redeliveries.
Alternatively, you can configure broker-side redeliveries in AMQ is
you want async behavior. In that case, you should not h
Can you set the Content-Type explicitly, before or after the transform?
text/plain
If you want to specify the HTTP response code, in camel-jetty you would set it
like this:
500
Hopefully it's the same for camel-servlet.
Regards,
Raúl.
On Mar 5, 2013, at 20:37, Alban wrote:
> Hi all,
>
>
Hi Henryk,
Thanks. Good idea.
I will explore this path.
Cheers
Manglu
--
View this message in context:
http://camel.465427.n5.nabble.com/Error-handling-Want-to-send-emails-on-errors-tp5727021p5727061.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Manglu,
> As part of this i want to send emails to admin with the error information.
Have you considered sending error messages to the SEDA queue and
reading them asynchronously afterwards?
errorHandler(deadLetterChannel("seda:errors"));
from("seda:errors").to(some slow and unreliable notific
Hi Lars,
So the camel endpoint you have at the end of the route is a cxf
endpoint, as you talk about a SOAP fault from the end of the route?
In a request-response scenario, you will get the SOAP fault
transferred back to the other end of the route and this is typically
returned as an HTTP 500 SOAP
Aki, thanks for the feedback.
At the moment I am only using request/response (InOut).
If the service (called by the end of the route) returns a SOAP Fault, will
then the cxf-endpoint make sure that the http status code returned to the
caller becomes 500?
Do the cxf-endpoint force the return of a
The behavior differs depending on the configuration. I'll try to give
a short overview.
If you have a request-response type service, the exception is normally
transferred to the caller. In that case, the corresponding soap fault
is returned to the caller and the http code is 500 for such general
s
On Mon, Oct 1, 2012 at 8:58 PM, gilboy wrote:
> Hi
>
> I noticed that most endpoint consumers do something like the following:
>
> try{
>getprocessor().process(exchange);
> } catch (exception e){
>getExceptionHandler.handleException();
> }
>
> Assume I have a route which consumes data from
On Tue, May 15, 2012 at 5:47 PM, Ignat wrote:
> Thanks, Claus.
>
> For some reason I saw your reply just now (and did not receive any e-mails
> from nabble, which is strange).
>
> Is there a way to attach unit of work synchronization code in Spring DSL ?
>
> This would be real help!
>
No you need
Thanks, Claus.
For some reason I saw your reply just now (and did not receive any e-mails
from nabble, which is strange).
Is there a way to attach unit of work synchronization code in Spring DSL ?
This would be real help!
--
View this message in context:
http://camel.465427.n5.nabble.com/Error
On Mon, Apr 16, 2012 at 12:58 PM, Ignat wrote:
> Hi All,
>
> I need to solve following scenario with camel:
>
> While message is being processed in route, I need to record certain
> information based on content being processed. At the end of processing this
> information have to be written to a st
Hi
Thanks for reporting. I created a JIRA
https://issues.apache.org/jira/browse/CAMEL-5110
On Fri, Mar 9, 2012 at 10:56 AM, razvan.ludvig
wrote:
> Hi.
>
> I started from the following unit test and made some changes to reproduce an
> issue we encountered in our application:
> https://fisheye6.a
> Isn't it difficult to do proper error handling with the EIP
> based approach?
I wouldn't think so. In fact it's probably easier than writing lots of specific
error handling code. I'm using Invalid Message Channel (IMS) to handle some
errors. Anything that fails goes in the IMC via a route that
i think the problem is that you have:
System.out.println(exchange.getProperty("
"+Exchange.EXCEPTION_CAUGHT,Throwable.class));
and what you actually want is:
System.out.println(" " +
exchange.getProperty(Exchange.EXCEPTION_CAUGHT,Throwable.class));
Travis
On Thu, Sep 1,
But in that case this lines should give the exception details
System.out.println(exchange.getProperty("
> "+Exchange.EXCEPTION_CAUGHT,Throwable.class));
but it is giving output as 'null"
--
View this message in context:
http://camel.465427.n5.nabble.com/Error-Handling-In-Camel-tp47
The caused exception is stored as a property on the Exchange using the key
Exchange.EXCEPTION_CAUGHT
On Wed, Aug 31, 2011 at 10:00 AM, aum.struts wrote:
> Hi All,
>
> While working with Camel i have a requirement where i need to validate an
> XML with a given XSD and in case of validation faliu
Ok, my bad. The NPE was actually happening in my code :)
Just so you know... it was happening in my AggregationStrategy implementation:
@Override
public Exchange aggregate(Exchange oldExchange, Exchange newExchange) {
if (weHaveAnException(newExchange)) {
if (weHaveTheDepo
By looking at ObjectHelper.java:1139 I also think the NPE is happening
somewhere else. I'll try to debug using breakpoints in IntelliJ idea first
thing in the morning and will also try to provide more of the stack trace.
Thanks for your help!
Mirko
Il giorno 03/ago/2011, alle ore 21:13, Claus
Hi
Do you have more of that stacktrace? I think the NPE is occurring
somewhere else.
On Tue, Aug 2, 2011 at 12:19 PM, Mirko Caserta wrote:
> Hi there,
> I'm having an issue I don't understand.
>
> I have a transactional route defined like this:
>
>
>
>
>
I've tried with:
java.lang.Exception
...snip...
but I get the same message flow + NPE at the end.
Mirko
On Tue, Aug 2, 2011 at 2:45 PM, Claus Ibsen wr
Hi
Could you try swapping the order of and .
On Tue, Aug 2, 2011 at 12:19 PM, Mirko Caserta wrote:
> Hi there,
> I'm having an issue I don't understand.
>
> I have a transactional route defined like this:
>
>
>
>
>
> java.lang.Exceptio
We were actually able to solve this by implementing a
PollingConsumerPollStrategy, since the error occurs before any Exchange has
been created and therefore won't be handled by Camel's regular Exception
handling. Please see:
https://cwiki.apache.org/confluence/display/CAMEL/Polling+Consumer
https:
Hi,
Please check out the Exception Handling capability in Camel
http://camel.apache.org/exception-clause.html
http://camel.apache.org/exception-clause.html
Cheers,
Ashwin...
-
-
Ashwin Karpe
Apache Camel Committer & Sr Principal Consu
On Wed, May 4, 2011 at 3:54 PM, bvahdat wrote:
> Hi Claus,
>
> Thanks for your reply!
>
> So my same question again: for the sake of avoiding the spring's warning
> mentioned already, would the following change on
> 'org.apache.camel.component.jms.JmsMessageListenerContainer' constructor
> make se
Hi Claus,
Thanks for your reply!
So my same question again: for the sake of avoiding the spring's warning
mentioned already, would the following change on
'org.apache.camel.component.jms.JmsMessageListenerContainer' constructor
make sense to you:
public JmsMessageListenerContainer(JmsEndpoin
Yeah there may be a spring specific error handler listener as well.
So you may have
- camel error handler (in the routes)
- jms exception listener
- spring error listener
On Tue, May 3, 2011 at 2:55 PM, bvahdat wrote:
> Hi all,
>
> I would really appreciate it if someone from the camel team co
Hi all,
I would really appreciate it if someone from the camel team could provide a
feedback if I'm wrong or not (see my previous post for details).
The only reason why I commented on this topic (although I was not the
original creater of it) was that I've got the same issue on my project, and
ju
davsclaus wrote:
>
> Welcome to the Camel community.
>
> The WARN message
> WARN | Execution of JMS message listener failed, and no ErrorHandler has
> been set.
>
> Is in fact not about the Camel error handler. Its about JMS exception
> listener you can set on the Activemq/JMS component
> htt
Hi
The workaround is to add, just before the end of the route
eg
http://localhost/mail/index/receive"/>
On Fri, Apr 29, 2011 at 10:59 AM, Claus Ibsen wrote:
> Hi
>
> I have reproduced the issue with the latest release. And created a
> ticket to track the bug fix
Hi
I have reproduced the issue with the latest release. And created a
ticket to track the bug fix
https://issues.apache.org/jira/browse/CAMEL-3913
Thanks for reporting.
On Fri, Apr 29, 2011 at 10:09 AM, davsclaus wrote:
> What version of ActiveMQ and Camel are you using?
>
>
> -Claus Ibsen
What version of ActiveMQ and Camel are you using?
-Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/--
View this message in context:
Welcome to the Camel community.
The WARN message
WARN | Execution of JMS message listener failed, and no ErrorHandler has
been set.
Is in fact not about the Camel error handler. Its about JMS exception
listener you can set on the Activemq/JMS component
http://camel.apache.org/jms
Yes I think t
Hi
I have reproduced the issue and fixed it on trunk
https://issues.apache.org/jira/browse/CAMEL-3877
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.
What Camel and Spring version are you using?
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manni
Hi
Ah you may have encountered an issue. Fell free to log a JIRA ticket.
On Tue, Apr 12, 2011 at 4:17 PM, jpalmer1026 wrote:
> Hi Claus,
>
> I'm actually not changing the error handler using adviceWith. My spring
> application context file defines a single error handler, which I reference
> as
Hi Claus,
I'm actually not changing the error handler using adviceWith. My spring
application context file defines a single error handler, which I reference
as an attribute on the camelContext tag to make it context-scoped. When I
subsequently simulate an error using advice with, I get the excepti
You cannot change error handler using adviceWith as the exception
message tell you.
Its a limitation in the routing engine. We will improve that in Camel
3.0 to make it fully dynamic.
On Mon, Apr 11, 2011 at 11:43 PM, jpalmer1026 wrote:
> I'd like to specify a context-scoped error handler in a
On Fri, Apr 1, 2011 at 4:34 PM, Claus Ibsen wrote:
> Just use a direct endpoint in the DLC.
>
> Then you can use a camel route where you can grab the caused exception
> message and do whatever you want with it.
>
You can also just use a bean endpoint in the DLC.
And then in the bean (pojo) have
Just use a direct endpoint in the DLC.
Then you can use a camel route where you can grab the caused exception
message and do whatever you want with it.
On Fri, Apr 1, 2011 at 2:58 PM, John McDonald wrote:
> I feel this is an embarrassingly simple question - but I've read around and
> cant get
for the 3 issues maybe you can use a boolean 'cascade'
Nicolas
--
View this message in context:
http://camel.465427.n5.nabble.com/error-handling-and-transaction-question-tp3341490p3344277.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Thank you for your reactivity,
Nicolas
--
View this message in context:
http://camel.465427.n5.nabble.com/error-handling-and-transaction-question-tp3341490p3344270.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I started a discussion about this use-case on the dev forum:
http://camel.465427.n5.nabble.com/DISCUSS-Route-scoped-onCompletion-tp3344202p3344202.html
On Mon, Jan 17, 2011 at 10:33 AM, Claus Ibsen wrote:
> On Mon, Jan 17, 2011 at 10:00 AM, niconic wrote:
>>
>> Hi Claus,
>>
>> Thank you for the
On Mon, Jan 17, 2011 at 10:00 AM, niconic wrote:
>
> Hi Claus,
>
> Thank you for the response.
> Could you explain me why?
> I don't understand : i use seda and i've two routes "definition", why these
> routes are anyway linked?
>
onCompletion adds itself as a callback to the Exchange so when the
Hi Claus,
Thank you for the response.
Could you explain me why?
I don't understand : i use seda and i've two routes "definition", why these
routes are anyway linked?
thx,
Nicolas
--
View this message in context:
http://camel.465427.n5.nabble.com/error-handling-and-transaction-question-tp3341
On Fri, Jan 14, 2011 at 4:58 PM, niconic wrote:
>
> Hi,
>
> When i use onecompletion on a route like this:
>
> from(getRouteFrom())
> .onCompletion().onFailureOnly()
> ...
> .end()
> .transacted("required")
> ...
> .to("seda:forcenewtransaction");
>
> from("seda:forcenewtransaction")
>
On Thu, Aug 12, 2010 at 10:33 AM, somemightsay wrote:
>
> I've been looking into this for quite a while but still haven't been able to
> find a definitive answer.
>
> How do you add error handling to a route such as the following:
>
> from("inputdir")
> .startupOrder(1)
> .setBody(constant(query))
Thanks. Somehow I thought it was a Camel issue but it was not. This is how
it was fixed.
public class ErrorHandler implements Processor {
public void process(Exchange exchange) throws Exception {
Exception c = exchange.getProperty(Exchange.EXCEPTION_CAUGHT,
On Tue, Jun 29, 2010 at 11:55 AM, Nav wrote:
>
> HI,
> We have a requirement that, on error in any of our routes, the error
> stack trace should be emailed to the developers. I am using Camel 2.3.0. I
> am not able to get the stack trace in the processor. Please let me know what
> is the best wa
Hi
Sometimes its easier just to implement a custom Processor or Bean and
then do the failover in there. Then you can handle the situations to
send different emails whatever happened.
On Mon, Jun 21, 2010 at 5:26 PM, raymond wrote:
>
> Hello,
>
> I have a simple route using failover:
>
>
Hi,
You can take a look at the wiki page of Camel about the ErrorHandler[1]
[1]http://camel.apache.org/error-handler.html
Willem
Francois Lefoll wrote:
Hi,
I tried most of possible configurations provided on documentation, but
didn't get any successful ones.
(my targets versions are camel 2.3
On Thu, Jun 10, 2010 at 10:09 PM, Steve Holmes wrote:
>
> Hi All!
>
> I originally posted this message to the "Camel in Action" forum but I'm
> hoping that someone here can help me out as well.
>
> I understand when an exception is thrown by some process during the Exchange
> (within a route) it i
Thanks, based on some of your suggestions and some more research, I was able
to come up with a suitable solution.
Allen Lau-2 wrote:
>
> I would think something like
>
> .beanRef("processor", "process")
> .split().method("mySplitterBean", "splitMessage")
> .choice
> .when(simple("${in.header.
I would think something like
.beanRef("processor", "process")
.split().method("mySplitterBean", "splitMessage")
.choice
.when(simple("${in.header.error} != null").to("mock:invalid")
.otherwise().to("mock:valid");
Your mySplitterBean would just create a 2 different messages, one with the
error hea
The splitter stuff doesn't seem to be useful for my issue, but I can see now
in the CBR page how to do logic in the route based on the header. In fact,
I was using the CBR on my route already. I'm still not clear on how to
actually set the header to the "error object in java code.
Here is the g
Look at these pages for samples.
http://camel.apache.org/splitter.html
http://camel.apache.org/content-based-router.html
I would most likely create a POJO to split the message up and then use the
content base router to
route the message.
On Wed, Mar 24, 2010 at 9:04 AM, jfaath wrote:
>
> I'll
I'll give this a shot. Can you give me a quick example or point me to a
sample that does something similar (ex. setting a header in code, performing
conditional logic in a route based on a header).
-JF
Allen Lau-2 wrote:
>
> I could be wrong here, but you could easily stick the "error" object
I could be wrong here, but you could easily stick the "error" object as part
of the message header. As long as your components
understand that header, you can easily retrieve it and only send that
portion to an error queue.
The default message headers in Camel is defined as
Map headers;
so bas
I'm not sure that would work. As I stated in my original post, I don't want
to send the entire message to the error queue, just the portion that was
invalid. So, if my original message has, say, 11 readings, and 3 of them
are bad, I only want to send the 3 bad ones to the error queue. During
pr
How about just setting a header when you are done processing and there is an
error?
Then in your route, just send any message to the error queue when the header
is detected.
On Tue, Mar 23, 2010 at 11:57 AM, jfaath wrote:
>
> I'm looking for some advice on how to deal with errors during a large
Ok, many thanks for the precious help
Claus Ibsen-2 wrote:
>
> And if you are looking for such kind of support you very likely have
> to acquired paid support. Which offers such kind of custom specific
> patches.
>
--
View this message in context:
http://old.nabble.com/Error-handling-with-r
On Fri, Nov 6, 2009 at 10:02 AM, mcrive wrote:
>
> Isn't the trunk where you commit the one containing changes after 2.0 REL?
> I am facing the issue with 2.0, everything is fine with 2.1.
>
Yeah it was against trunk.
Instead of using intercept to endpoint you could use your own kind of
recipien
Isn't the trunk where you commit the one containing changes after 2.0 REL?
I am facing the issue with 2.0, everything is fine with 2.1.
Claus Ibsen-2 wrote:
>
> On Thu, Nov 5, 2009 at 4:09 PM, mcrive wrote:
>>
>> doing the same thing with Camel 2.1 I can see what I am expecting
>> so it is
Even by removing the exchange.setOut I am not seeing the header I've added
when checking the exchange In message on the exception processor.
this is my current process for interceptSendToEndpoint:
public void process(Exchange exchange) throws Exception {
String deliveryEndPoint =
On Wed, Nov 4, 2009 at 5:12 PM, mcrive wrote:
>
> I've configured following route:
>
> interceptSendToEndpoint("*").process(new SendToEndPointHandler());
>
> onException(GenericFileOperationFailedException.class)
> .process(new DeliveryFailureHandler());
>
> from("test-jms:queue:notificatio
I've configured following route:
interceptSendToEndpoint("*").process(new SendToEndPointHandler());
onException(GenericFileOperationFailedException.class)
.process(new DeliveryFailureHandler());
On Wed, Nov 4, 2009 at 2:48 PM, mcrive wrote:
>
> thank you for such a quick reply!
>
> I am currently using 2.0 REL, is there a way to do the same thing with the
> version I have?
>
You can use interceptSendToEndpoint
http://davsclaus.blogspot.com/2009/05/on-road-to-camel-20-interceptors-round.h
thank you for such a quick reply!
I am currently using 2.0 REL, is there a way to do the same thing with the
version I have?
Claus Ibsen-2 wrote:
>
> On Wed, Nov 4, 2009 at 2:40 PM, mcrive wrote:
>>
>> I ha following route
>>
>>
>> onException(GenericFileOperationFailedException.class)
>>
On Wed, Nov 4, 2009 at 2:40 PM, mcrive wrote:
>
> I ha following route
>
>
> onException(GenericFileOperationFailedException.class)
> .process(new DeliveryFailureHandler()).stop();
>
>
> from("test-jms:queue:feed.notificationtest.queue")
> .process(processor)
> .recipientList(
I broke the route up into two routes and it seems to be working fine.
Thanks Matt
SoaMattH wrote:
>
>
> The problem:
> Occasionally I am getting poorly formed XML and am trying to fixit on the
> fly.
> Most of the time I can, 1% of the time I cannot.
>
> In the route below this is what I w
Hi
I will split the "try to patch the file" code into a 2nd route as this
generally works better than deep nested route logic.
And then use direct endpoint to "link" the two routes.
>
>
Should then be
On Mon, Oct 5, 2009 at 9:24 AM,
On Wed, May 13, 2009 at 5:09 PM, turp1twin wrote:
>
> Thanks for the reply Claus! Your help is very much appreciated. Perhaps I
> will extend the camel code to allow for redelivery functionality using
> try/catch semantics. Cheers!
Contributions is always welcome.
For starters you could create a
Thanks for the reply Claus! Your help is very much appreciated. Perhaps I
will extend the camel code to allow for redelivery functionality using
try/catch semantics. Cheers!
Jeff
Claus Ibsen-2 wrote:
>
> On Wed, May 13, 2009 at 2:59 PM, Claus Ibsen
> wrote:
>> On Tue, May 12, 2009 at 10:34 P
On Wed, May 13, 2009 at 2:59 PM, Claus Ibsen wrote:
> On Tue, May 12, 2009 at 10:34 PM, turp1twin wrote:
>>
>> Hi Claus,
>>
>> One last question... Is it possible to define retry/redelivery semantics
>> when using try/catch DSL functionality?
> Good question. As doCatch is basically also a OnExce
On Tue, May 12, 2009 at 10:34 PM, turp1twin wrote:
>
> Hi Claus,
>
> One last question... Is it possible to define retry/redelivery semantics
> when using try/catch DSL functionality?
Good question. As doCatch is basically also a OnException model it
should be in the DSL. But I have to check in th
Hi Claus,
One last question... Is it possible to define retry/redelivery semantics
when using try/catch DSL functionality?
Jeff
Claus Ibsen-2 wrote:
>
> On Tue, May 12, 2009 at 6:31 AM, turp1twin
> wrote:
>>
>> Hi Claus,
>>
>> Thanks so much for the quick response! This helps me very much!
On Tue, May 12, 2009 at 6:31 AM, turp1twin wrote:
>
> Hi Claus,
>
> Thanks so much for the quick response! This helps me very much! Yes,
> basically, if the sending the email fails, I just want to log the error and
> end the route. I want the File consumer to complete and move/delete the
> file, s
Hi Claus,
Thanks so much for the quick response! This helps me very much! Yes,
basically, if the sending the email fails, I just want to log the error and
end the route. I want the File consumer to complete and move/delete the
file, since a new file will be created and processed at a later time w
Hi
Error handling is hard, especially for non transactional transports
such as File / FTP and the likes.
>From what I understand from your description is that you want to poll
files and upload them to SFTP.
And in case this fails an email should be sent. And if this email
fails then it should ???
Hi
I would not go down the AsyncProcessor route :) Its @deprecated and
will be replaced by a new API in 2.0.
The AsyncProcessor was an experiment that was added in Camels early
days and the JDK API itself has much better solutions
for handling async tasks. Hence why we are replacing it totally in
I see both jms consumer and seda consumer uses getProcessor().process()
instead of the getAsyncProcessor().process(exchange, callback). I am
concerned whether it will block even though I have an async
producer(implemented the AsyncProcessor) down the route. If this were the
case, seda consumer woul
On Mon, May 4, 2009 at 12:44 PM, Zhi Zhou wrote:
> Great. it's closer to what I want now..Thanks Claus.
> However, my producer is a sync processor, which has finished processing that
> exchange, if I set the exception to the exchange, it seems no other way I
> can pass it to camel's control any mo
Great. it's closer to what I want now..Thanks Claus.
However, my producer is a sync processor, which has finished processing that
exchange, if I set the exception to the exchange, it seems no other way I
can pass it to camel's control any more. I just cached the exchange in the
timeout task when fi
On Mon, May 4, 2009 at 11:40 AM, Zhi Zhou wrote:
> Claus,
> Thank you very much for the quick response!
>
> On Mon, May 4, 2009 at 5:07 PM, Claus Ibsen wrote:
>
>> Hi
>>
>> What version of Camel are you using? Camel 2.0 has many improvments in
>> error handling and processing over 1.x.
>>
>
> Sor
In Camel 1.x there is AsyncProcessor interface (it extends Processor)
that allows you to handle things asynchronously. While it is rather
hard to use it, you have a chance to process your request
asynchronously.
In fact Camel doesn't specify if error handling will happen in some
thread or not - it
Claus,
Thank you very much for the quick response!
On Mon, May 4, 2009 at 5:07 PM, Claus Ibsen wrote:
> Hi
>
> What version of Camel are you using? Camel 2.0 has many improvments in
> error handling and processing over 1.x.
>
Sorry that I forgot to mention I am using 1.x for now as 2.0 is still
Hi
What version of Camel are you using? Camel 2.0 has many improvments in
error handling and processing over 1.x.
On Mon, May 4, 2009 at 10:54 AM, Zhi Zhou wrote:
> Hello all,
>
> Camel's error handling is pretty powerful, but lately I am having two
> questions about it.
>
> 1) I am working a cu
95 matches
Mail list logo
