Thanks Claus. I can work on fixing this and issuing a pull request.
On Tue, Jan 10, 2023 at 2:29 PM Claus Ibsen wrote:
> Hi
>
> A ticket to tweak the noisy logging
> https://issues.apache.org/jira/browse/CAMEL-18875
>
> To handle the exception you can configure an exception listener on the jms
Hi
A ticket to tweak the noisy logging
https://issues.apache.org/jira/browse/CAMEL-18875
To handle the exception you can configure an exception listener on the jms
component
On Fri, Jan 6, 2023 at 12:39 PM Claus Ibsen wrote:
> You can send a PR to tweak the log to not output the stacktrace. We
You can send a PR to tweak the log to not output the stacktrace. We could
potentially log including stacktrace in DEBUG mode so end users can turn on
that logging level in case the stacktrace is needed during troubleshooting
On Fri, Jan 6, 2023 at 12:22 PM Mark Webb wrote:
> Sure, I could tweak
Sure, I could tweak the logger. I was hoping to not have the stack trace
get logged, but a more user-friendly log generated.
On Fri, Jan 6, 2023 at 12:56 AM Claus Ibsen wrote:
> Hi
>
> Do you want that WARN to not be logged - or the logging to NOT include the
> stacktrace?
> The log is hardcode
Hi
Do you want that WARN to not be logged - or the logging to NOT include the
stacktrace?
The log is hardcoded and it can happened when using temporary reply queues.
You can tweak the logger to set logging level to ERROR
for TemporaryQueueReplyManager etc
On Thu, Jan 5, 2023 at 8:51 PM Mark Web
I'm starting up a project that will use the request/response with ActiveMQ
AMQP. When I try to send a message that I expect a response to and
ActiveMQ is down, I can't seem to catch or prevent the stack trace from
getting logged for the TemporaryQueueReplyManager. The error is:
Exception inside
Hi
I tried searching documents are also "Camel in Action - 2" to find how do I
put the custom logic when all redelivery attempts are exhausted in error
handler.
Any pointer here will be helpful.
Thanks and Regards,
Hemang Ajmera
Hemang C Ajmera | Technical Architect
Asia Pacific Communicat
Hi
Thanks for all your findings, this is great insight. You are surely
welcome to create a JIRA ticket about this bug.
We can then together work on a fix, and you can help test it.
Yeah it seems catching KafkaException is maybe too wide. And lets see
if we also can incorporate bridge error handle
digging into the code (version 3.2.0 i repeat),
i can see in the class
`org.apache.camel.component.kafka.KafkaConsumer.KafkaFetchRecords.doRun`,
lign 406:
```
catch (KafkaException e) {
// some kind of error in kafka, it may happen during
// unsubscribing or during normal processing
if (uns
I forgot to tell i am using version 3.2.0
On Sun, 26 Apr 2020 at 20:45, Joseph M'BIMBI-BENE
wrote:
> Hello everyone,
>
> I'm having a problem with the Kafka component:
> When the kafka consumer can't read a message (caused by some avro errors
> after investigation), it continuously leaves the g
Hello everyone,
I'm having a problem with the Kafka component:
When the kafka consumer can't read a message (caused by some avro errors
after investigation), it continuously leaves the group and joins again.
I would like it to just throw an exception and let me decide how to handle
it: dlq, ignor
I also realize that the property "bridgeErrorHandler" seems to never be
used, while another one, like "breakOnFirstError".
Also, going back to the exception handling, at least a couple other
subclasses of KafkaException would deserve not to be retried on. Just a few
examples:
- ConfigExceptio
Hi
Okay its a bit weird as I would assume the zip api would throw an
exception. Can you create a JIRA
On Tue, Mar 10, 2020 at 9:17 PM Gerald Kallas wrote:
>
> Dear community,
>
> I've following route
>
> http://www.osgi.org/xmlns/blueprint/v1.0.0";>
> http://camel.apache.org/schema/bluep
Dear community,
I've following route
http://www.osgi.org/xmlns/blueprint/v1.0.0";>
http://camel.apache.org/schema/blueprint";>
When I'm sending
choen
mailto:r.sch...@topdesk.com>> a écrit :
Hi,
I noticed that the error handling has changed in 3.1.0 from 3.0.1. We use
a DeadLetterChannel and when the error has been handled, I expect the
original route to stop and not to continue.
When we use enrich we pass the exchange property CamelErrorHan
Would you mind raising a JIRA issue and attaching your test ?
I'll have a look at the problem.
Le lun. 9 mars 2020 à 15:48, Remco Schoen a écrit :
> Hi,
>
> I noticed that the error handling has changed in 3.1.0 from 3.0.1. We use
> a DeadLetterChannel and when the error ha
getMockEndpoint("mock:failingRoute").expectedMessageCount(1)
getMockEndpoint("mock:nextRoute").expectedMessageCount(0)
template.sendBody('direct:start', null)
assertMockEndpointsSatisfied()
}
Regards,
Remco
Op 9 mrt. 2020, om 15:47 heeft Remco Schoen
ma
Hi,
I noticed that the error handling has changed in 3.1.0 from 3.0.1. We use a
DeadLetterChannel and when the error has been handled, I expect the original
route to stop and not to continue.
When we use enrich we pass the exchange property CamelErrorHandlerHandled back
to ensure the calling
Hi,
I have a question about best practices on error handling in Camel route A,
which calls Camel route B.
A and B are different route builder instances
class A extends RouteBuilder {
configure() {
onException(Exception.class)
.handled(true)
// produce general error message
By accident I came across a strange behavior when simulating error situations
for a CXF producer endpoint. As route starting point I use also a CXF endpoint.
There is actually no additional configuration like WSDL or steps between the
endpoints. Now I configured the simulator endpoint (which is
but instead to use the
> > > .fliter().method("MyBeanValidator") which does a Boolean whether to
> > > continue or not. But in the validator I have endpoints injected for
> > error
> > > handling. In this case I'm firing off emails to administrator
16 at 4:23 PM Carlos Rodriguez Fernandez <
carlosrodrifernan...@gmail.com> wrote:
> Hi,
>
> I'm trying to understand the error handling in Apache Camel. I have
> defined a route to processes Kafka messages and I want the fetching to keep
> trying forever, but to
Hi,
I'm trying to understand the error handling in Apache Camel. I have defined
a route to processes Kafka messages and I want the fetching to keep trying
forever, but to ignore exceptions from the processor. So I have this setup:
from(notificationSystemInboundEnd
this issue. I decided in my
> > particular case not to use the .validate() but instead to use the
> > .fliter().method("MyBeanValidator") which does a Boolean whether to
> > continue or not. But in the validator I have endpoints injected for
> error
> > handli
to use the
> .fliter().method("MyBeanValidator") which does a Boolean whether to
> continue or not. But in the validator I have endpoints injected for error
> handling. In this case I'm firing off emails to administrators. But if
> you can inject an endpoint then i
It's funny but I was just wrestling with this issue. I decided in my
particular case not to use the .validate() but instead to use the
.fliter().method("MyBeanValidator") which does a Boolean whether to
continue or not. But in the validator I have endpoints injected for error
han
I have a common pattern right now of adding .validate() to several REST DSL
params since the .required() swagger DSL appears to be a suggestion and not
a validation. Since my REST DSL is spread across several routes, I'd like
to use some sort of shared error handling. Now I see there are two
>
> My main issue to track the DB connection issues which is happening in my
> custom code when the issue goes more than a limit suspend all the routes
> running in the camelcontext.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Sp
running in the camelcontext.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Spring-Bean-error-Handling-tp5785414p5785450.html
Sent from the Camel - Users mailing list archive at Nabble.com.
. Is there a good way to handle this.
>
>
>
>
> Thx,
> Fx
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Spring-Bean-error-Handling-tp5785414.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
I saw in spring there are ApllicationEevents handling but i dont see
specific to bean handling . Is there a good way to handle this.
Thx,
Fx
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Spring-Bean-error-Handling-tp5785414.html
Sent from the Camel - Users mai
code
Can i put error handling out of main camelContext xml file?
--
View this message in context:
http://camel.465427.n5.nabble.com/Limit-of-Error-handling-in-Camel-tp5779105.html
Sent from the Camel - Users mailing list archive at Nabble.com.
620133 | Failed delivery
for (MessageId: ID-FGBAL201530-50468-1454139836959-1-16 on ExchangeId:
ID-FGBAL201530-50468-1454139836959-1-5). *On delivery attempt: 1* caught:
org.apache.camel.CamelExchangeException: JettyClient failed cause by:
Connection refused: no further information. Exchange[JmsMessage@0x62e96526].
Caused by: [java.net.ConnectException - Connection refused: no further
information]
This is very strange... I use JBoss Fuse 6.2 based on Camel with version
2.15.1.redhat-620133.
I'll try to do your example in JBoss Fuse and let you know.
Thanks for your support.
Greeting
Michele
--
View this message in context:
http://camel.465427.n5.nabble.com/Error-Handling-and-Redelivery-Policy-between-routes-tp5776905p5777038.html
Sent from the Camel - Users mailing list archive at Nabble.com.
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
Caused by: [java.net.ConnectException - Connection refused: no further
information]
16:55:27,131 | DEBUG | erRedeliveryTask | DeadLetterChannel|
198 - org.apache.camel.camel-core - 2.15.1.redhat-620133 | Redelivery delay
calculated as 6
Thanks in advance
Best regards
Mich
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:
>
>
>
>
>
Hi everyone,
error handling and redelivery policy do not work fine when a main route
requests enricher from subroute. When an error accours in subroute, the
exception is propagated to main route wich handles it by DLQError handler
but the delivery attempt remains at 1. It is not incremented until
the errorQueue?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Handling-splitting-and-error-handling-tp5765748p5765819.html
>
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
will not. But then it *will also rollback
the message to the inbound queue* AND post it to the errorQueue?
--
View this message in context:
http://camel.465427.n5.nabble.com/Handling-splitting-and-error-handling-tp5765748p5765819.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ut problems, if not the message should be sent
to the error queue.
The processors are transformers and will transform the messages to different
xsd versions
--
View this message in context:
http://camel.465427.n5.nabble.com/Handling-splitting-and-error-handling-tp5765748.html
Sent from the Camel - Users mailing list archive at Nabble.com.
View this message in context:
http://camel.465427.n5.nabble.com/CXF-Inteceptor-Error-handling-with-Camel-CXF-JMS-and-ActiveMQ-tp5758297p5758453.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ute (the exception occurs
> in an interceptor).
>
> Does anyone know a way to handle this?
>
> Thanks,
>
> g8torPaul
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/CXF-Inteceptor-Error-handling-with-Camel-CXF-JMS-and-ActiveMQ-tp5758297.html
>
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
into the route (the exception occurs
in an interceptor).
Does anyone know a way to handle this?
Thanks,
g8torPaul
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-Inteceptor-Error-handling-with-Camel-CXF-JMS-and-ActiveMQ-tp5758297.html
Sent from the Camel - Users
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
the
onException blocks. Can someone help me in handling the exceptions that
occur in the aggregation strategy?
Thanks,
Richa
--
View this message in context:
http://camel.465427.n5.nabble.com/Error-handling-in-aggregation-strategy-tp5753876.html
Sent from the Camel - Users mailing list archive at
; studio's game site went down causing the exchanges to fail. In this
>> >> > circumstance we would rather push the exchange to a dead letter queue
>> and
>> >> > then later be able to determine why the problem happened and relish
>> those
>> >
harth Shah
--
View this message in context:
http://camel.465427.n5.nabble.com/aggregator-error-handling-default-does-not-propogate-error-tp4283684p5752656.html
Sent from the Camel - Users mailing list archive at Nabble.com.
queue
> and
> >> > then later be able to determine why the problem happened and relish
> those
> >> > exchanges. Again finding the "why" in a log file isn't going to work
> out.
> >> >
> >> > -- Robert
> >> >
> >&
>> > -- Robert
>> >
>> > On Friday, May 23, 2014, Claus Ibsen wrote:
>> >
>> >> You cannot provide a reason why a rollback happens in the TX API.
>> >> There is no rollback(String message) api for that.
>> >>
gt; You cannot provide a reason why a rollback happens in the TX API.
> >> There is no rollback(String message) api for that.
> >>
> >> You need to record this somewhere else if you want to use that.
> >> Or do your own kind of TX rollback.
> >>
> >
want to use that.
>> Or do your own kind of TX rollback.
>>
>> On Thu, May 22, 2014 at 11:00 PM, kraythe . >
>> wrote:
>> > Greetings, I have many routes that read from AMQ queues and write to
>> other
>> > AMQ queues. For error handling I hav
record this somewhere else if you want to use that.
> Or do your own kind of TX rollback.
>
> On Thu, May 22, 2014 at 11:00 PM, kraythe . >
> wrote:
> > Greetings, I have many routes that read from AMQ queues and write to
> other
> > AMQ queues. For error handling I ha
any routes that read from AMQ queues and write to other
> AMQ queues. For error handling I have been using the following paradigm:
>
> from("activemq:queue:inbox")
>
> .onException(Exception.class).useOriginalMessage().handled(handled).maximumRedeliveries(0)
> .setH
Greetings, I have many routes that read from AMQ queues and write to other
AMQ queues. For error handling I have been using the following paradigm:
from("activemq:queue:inbox")
.onException(Exception.class).useOriginalMessage().handled(handled).maximumRedeliveries(0)
of a camel way.
--
View this message in context:
http://camel.465427.n5.nabble.com/error-handling-design-pattern-advice-tp5744364p5744591.html
Sent from the Camel - Users mailing list archive at Nabble.com.
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'
e a Splitter to split my route
> into individual item messages (which might work nicely) but then I realized
> that I would lose my sharedModel as the message body which i need that to
> make the service calls.
>
> What is the best design pattern for this situation?
>
> much appreciated
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/error-handling-design-pattern-advice-tp5744364.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Hi All,
I've got a question about error handling. Here is my scenario...
I have a route which calls a bean..
from(...JPA...)
.errorHandler(deadLetterChannel("log:dead")
.maximumRedeliveries(5)
.retryAttemptedLogLevel(LoggingLevel.ERROR))
.to("bean:serviceBea
Hi
Ya I was asking about timeout.
Thanks
-
Regards
kiran Reddy
--
View this message in context:
http://camel.465427.n5.nabble.com/Producer-template-error-handling-tp5743684p5743735.html
Sent from the Camel - Users mailing list archive at Nabble.com.
emplate is just like any Java api, it throws an
exception if something goes wrong.
On Fri, Nov 22, 2013 at 10:29 AM, kiranreddykasa wrote:
> Hi
>
> I would like to know how to do error handling with producer template.
>
> I'm sending a message to activemq endpoint using '
Hi
I would like to know how to do error handling with producer template.
I'm sending a message to activemq endpoint using 'requestBody' of producer
template.
Suppose if there is requestTimeout in activemq how can I catch that
exception and build response??
-
Regar
in.com/pub/robert-simmons/40/852/a39*
On Mon, Oct 7, 2013 at 12:17 PM, berhack wrote:
> I have context level defined error handling (retry interval and retry
> attempts defined) that I am trying to test out. Yet it will never be
> invoked no matter how I simulate the error with mock
I have context level defined error handling (retry interval and retry
attempts defined) that I am trying to test out. Yet it will never be
invoked no matter how I simulate the error with mock end points. Does
anyone how this can work?
Given my route I'm testing just looks like:
from(my
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
Hi,
I have a route with an errorHandler configured. I set it to redeliver
async. But when an error occures the remaining messages on the queue are
processed after the redelivery of the failed message ends.
Here is my routebuilder: http://pastebin.com/8fUED75R
Is there something wrong with it
amel-cxf / CXF in streaming mode.
> >> See the top of this page, the green tip bar, and its link(s)
> >> http://camel.apache.org/cxf
> >>
> >>
> >>
> >> On Fri, Apr 5, 2013 at 2:33 PM, Nico Mommaerts <
> nico.mommae...@gmail.com
)
>> http://camel.apache.org/cxf
>>
>>
>>
>> On Fri, Apr 5, 2013 at 2:33 PM, Nico Mommaerts
>> wrote:
>> > Hey,
>> >
>> > I've been reading the chapter on Error handling over and over but I'm
>> still
>> > failin
streaming mode.
> See the top of this page, the green tip bar, and its link(s)
> http://camel.apache.org/cxf
>
>
>
> On Fri, Apr 5, 2013 at 2:33 PM, Nico Mommaerts
> wrote:
> > Hey,
> >
> > I've been reading the chapter on Error handling over and over bu
Hi
Sounds like you use camel-cxf / CXF in streaming mode.
See the top of this page, the green tip bar, and its link(s)
http://camel.apache.org/cxf
On Fri, Apr 5, 2013 at 2:33 PM, Nico Mommaerts wrote:
> Hey,
>
> I've been reading the chapter on Error handling over and over
class);
>> accessKeyProvider.returnAccessKey(accessKey);
>> }
>> });
>>
>> BUT my current problem is that redelivery only happens when the camel
>> log4j log level is on DEBUG! What strange manner of magic is this I ask
>> thee? On INFO the exception does g
this I ask
> thee? On INFO the exception does get caught but nothing further happens,
> the route seems to be stuck somewhere, eventually Soapui (which I use to
> test) receives a timeout,
>
>
> On Fri, Apr 5, 2013 at 2:33 PM, Nico Mommaerts
> wrote:
>
>> Hey,
>&g
hee? On
INFO the exception does get caught but nothing further happens, the route
seems to be stuck somewhere, eventually Soapui (which I use to test)
receives a timeout,
On Fri, Apr 5, 2013 at 2:33 PM, Nico Mommaerts wrote:
> Hey,
>
> I've been reading the chapter on Error handlin
Hey,
I've been reading the chapter on Error handling over and over but I'm still
failing miserably..
My scenario: a cxf proxy route which modifies the soapheaders, I want all
soapfaults to be returned as-is to the caller, except when the soapfault
contains a certain string. In that c
o display a custom message in the http response
>
> Anyone can help me please ?
>
> Thank you
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Error-Handling-and-HTTP-response-tp5728599.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
different case : with setBody, with setFaultBody, ... and
i have never successed to display a custom message in the http response
Anyone can help me please ?
Thank you
--
View this message in context:
http://camel.465427.n5.nabble.com/Error-Handling-and-HTTP-response-tp5728599.html
Sent
Hello Gents,
I would like to pick your brains about a way to globally handle errors in
our routs builders. I'm pretty new to Camel so please bear with me and my
silly questions ;)
The goal:
I would like to set up a concise error handling for the SOAPFaults and our
own exceptions that we
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
View this message in context:
http://camel.465427.n5.nabble.com/Error-handling-Want-to-send-emails-on-errors-tp5727021.html
Sent from the Camel - Users mailing list archive at Nabble.com.
OAP Faults, under which circumstances does this happen?
>
> Thanks
>
> Lars
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Error-handling-when-using-camel-cxf-tp5723955p5724021.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
in context:
http://camel.465427.n5.nabble.com/Error-handling-when-using-camel-cxf-tp5723955p5724021.html
Sent from the Camel - Users mailing list archive at Nabble.com.
s
>
> Lars
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Error-handling-when-using-camel-cxf-tp5723955.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
-2,
>>> CamelSmppCommandId=5, CamelSmppMessageType=DeliverSm}, readOnlyProperties =
>>> false, readOnlyBody = false, droppable = false, text = 2314234}
>>> 2012-10-03 13:10:00,030 DEBUG [pool-1-thread-1] [TryProcessor.java:361] The
>>> exception is handled: true
ingframework.jms.UncategorizedJmsException caused by: Uncategorized
>> exception occured during JMS processing; nested exception is
>> javax.jms.JMSException: JTA transaction required for JtaMessageProducer
>> 2012-10-03 13:10:00,032 DEBUG [pool-1-thread-1] [SMPPSession.java:499]
>&
gt; > 01:10:00 [pavel] client response: (deliver_resp: (pdu: 17 8005 0 15)
> > )
>
> Does anyone know what I have to do to get this exception propagated up to
> the JSMPP library so it returns an error to the SMSC? This is not working
> as
> advertised...
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Problem-with-SMPP-Consumer-error-handling-tp5720516.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
17 8005 0 15)
> )
Does anyone know what I have to do to get this exception propagated up to
the JSMPP library so it returns an error to the SMSC? This is not working as
advertised...
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-SMPP-Consumer-error
g engine will kick in and handle errors.
The code above is just as a fail safe for a consumer.
If you got the Camel in Action book see section 5.1.2.
And read about error handling as well (and follow the links)
http://camel.apache.org/error-handling-in-camel.html
> Thanks
> Joe
>
>
if processor 2-4
throw an exception but not clear to me how it will behave if the first
processor throws an exception
Thanks
Joe
--
View this message in context:
http://camel.465427.n5.nabble.com/error-handling-query-tp5720326.html
Sent from the Camel - Users mailing list archive at Nabble.com.
on: 2.10.0.
java.net.SocketTimeoutException
cxf:bean:AddressFromProperty
RealService
--
View this message in context:
http://camel.465427.n5.nabble.com/cxf-recipientList-and-error-handling-tp5717160.html
Sent from the Camel - Users mailing list
with the Java DSL and if you use 2+ RouteBuilder classes, is that
if want to share
error handlers between them, you would need to create a base class
extending RouteBuilder. And
then let your route builders extend your base class. And in your base
class, do the global error handling.
And the
lobal exception handling (e.g. onException) with Java DSL, do
> i need to define a separate route that contains the onException code so
> that
> every route in the context will pick it up?
>
> Thanks
> Damien
>
> --
> View this message in context:
> http://camel.46542
/Camel-error-handling-tp5715132p5715177.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
Besides the docs at Apache there is a few blog posts, such as
http://www.consulting-notes.com/2010/08/camel-exception-handling-overview.html
And if you have a copy of the Camel in Action book, then the entire
chapter 5 is devoted to error handling.
On Tue, Jun 26, 2012 at 11:18 PM
Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com
Blog: http://opensourceknowledge.blogspot.com
-
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-e
Hi
from reading through camel, there seems like many ways to perform different
operations.
I have a specific question around error handling and what the general
consensus
>From what I can see, there is the dead letter channel, try, catch, finally,
global exceptions etc
>From an appli
Thanks Claus
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Error-handling-throwing-exception-not-moving-to-error-queue-tp5714076p5714676.html
Sent from the Camel - Users mailing list archive at Nabble.com.
n, Jun 11, 2012 at 3:15 PM, javaxmlsoapdev
> wrote:
>
>> using 2.9.2. Could you let me know if there is an issue with such
>> deadLetterChannel setting working with receipientList EIP?
>>
>> Thanks,
>>
>> --
>> View this message in context:
>> http://camel.
>
> Thanks,
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Error-handling-throwing-exception-not-moving-to-error-queue-tp5714076p5714290.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
using 2.9.2. Could you let me know if there is an issue with such
deadLetterChannel setting working with receipientList EIP?
Thanks,
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Error-handling-throwing-exception-not-moving-to-error-queue-tp5714076p5714290.html
Sent
1 - 100 of 251 matches
Mail list logo
