Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.216.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=gj2BgGvi0pDFNzdl5wVVe6Qvpswqm/h84z4cZPk1mAdM/bshGsBs4jWbNufvWtFHjc
         UE6JZ7CfZUB0Z1SVha66TWb2Hw910JvY/s8SytmHV/vXAuvhOZS2UbkAU55s4jvPqkmK
         pgFoYhzudq0CwLUGK/r81IJoWSHXXwX+t3PaM=
MIME-Version: 1.0
In-Reply-To: 
 <BB54F5B84B72C841B4D4CB2C1D98C20E77B8E92F@LDNPCMMGMB03.INTRANET.BARCAPINT.COM>
References: 
 <BB54F5B84B72C841B4D4CB2C1D98C20E77B8E923@LDNPCMMGMB03.INTRANET.BARCAPINT.COM>
 <AANLkTi==BoM0Vk0H0J0oGQ3xKMXRRBo_bXL_CePKXS3F@mail.gmail.com>
 <BB54F5B84B72C841B4D4CB2C1D98C20E77B8E926@LDNPCMMGMB03.INTRANET.BARCAPINT.COM>
 <AANLkTi=u=7WiuNq3AG-UKgcM32KNPp84rGokzwo4cBvu@mail.gmail.com>
 <BB54F5B84B72C841B4D4CB2C1D98C20E77B8E929@LDNPCMMGMB03.INTRANET.BARCAPINT.COM>
 <AANLkTim0B-Bqy1-Pr893Qo66_kGT7PoD-4czxiAVjpP0@mail.gmail.com>
 <BB54F5B84B72C841B4D4CB2C1D98C20E77B8E92C@LDNPCMMGMB03.INTRANET.BARCAPINT.COM>
 <AANLkTimZ5MQwmO9Z9Li58TZSF3Tg9GROq9m59UmszU5Z@mail.gmail.com>
 <BB54F5B84B72C841B4D4CB2C1D98C20E77B8E92D@LDNPCMMGMB03.INTRANET.BARCAPINT.COM>
 <AANLkTim634Rm9vEZ7GtN+s4GfaGnBV8bbuT_BeFGH2mG@mail.gmail.com>
 <BB54F5B84B72C841B4D4CB2C1D98C20E77B8E92F@LDNPCMMGMB03.INTRANET.BARCAPINT.COM>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 29 Sep 2010 11:17:40 +0200
Message-ID: <AANLkTimjjF_74j7aNrOsQ8dvx6cSpf3mHKc03MiN+rn1@mail.gmail.com>
Subject: Re: Exception details
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Just use "direct:errorHandlerRoute" instead of ref:direct:errorHandlerRoute

On Wed, Sep 29, 2010 at 10:49 AM,  <Steve.Hedges@barclayscapital.com> wrote=
:
> Claus
>
> This is the relevant (more complete) extract of the spring config:
>
>
> =A0 =A0 =A0 =A0<errorHandler id=3D"loggingErrorHandler" type=3D"LoggingEr=
rorHandler"
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0level=3D"INFO" xmlns=3D"http://camel.apach=
e.org/schema/spring" />
>
> =A0 =A0 =A0 =A0<errorHandler id=3D"errorHandler" type=3D"DeadLetterChanne=
l"
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0deadLetterUri=3D"direct:errorHandlerRoute"=
 />
>
> =A0 =A0 =A0 =A0<camelContext id=3D"camel" xmlns:stp=3D"http://www.barcap.=
com/gcd/stpengine/1-0">
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<template id=3D"camelTemplate" />
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<endpoint id=3D"JMS_IN" uri=3D"jms:queue:$=
{input.queue}" />
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<endpoint id=3D"JMS_OUT" uri=3D"jms:queue:=
${output.queue}" />
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<endpoint id=3D"JMS_ERROR" uri=3D"jms:queu=
e:${error.queue}" />
>
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<route>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<from ref=3D"direct:errorH=
andlerRoute"/>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<log message=3D"RAISED EXC=
EPTION: ${exception}" loggingLevel=3D"ERROR"/>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<to ref=3D"JMS_ERROR"/>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</route>
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<route id=3D"compression-workflow" errorHa=
ndlerRef=3D"errorHandler">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<from ref=3D"JMS_IN" />
>
> ...
>
> Execution gives the following error:
>
> INFO: Apache Camel 2.5-SNAPSHOT (CamelContext: camel) is shutdown in 0.01=
6 seconds
> Exception in thread "main" org.apache.camel.RuntimeCamelException: org.ap=
ache.camel.FailedToCreateRouteException: Failed to create route route1: Rou=
te[[From[ref:direct:errorHandlerRoute]] -> [Log[RAISED EX... because of No =
endpoint could be found for: ref:direct:errorHandlerRoute, please check you=
r camel registry with id direct:errorHandlerRoute
> =A0 =A0 =A0 =A0at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelExce=
ption(ObjectHelper.java:1133)
> =A0 =A0 =A0 =A0at org.apache.camel.spring.SpringCamelContext.onApplicatio=
nEvent(SpringCamelContext.java:103)
> =A0 =A0 =A0 =A0at org.apache.camel.spring.CamelContextFactoryBean.onAppli=
cationEvent(CamelContextFactoryBean.java:236)
> =A0 =A0 =A0 =A0at org.springframework.context.event.SimpleApplicationEven=
tMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:97)
> =A0 =A0 =A0 =A0at org.springframework.context.support.AbstractApplication=
Context.publishEvent(AbstractApplicationContext.java:303)
> =A0 =A0 =A0 =A0at org.springframework.context.support.AbstractApplication=
Context.finishRefresh(AbstractApplicationContext.java:911)
> =A0 =A0 =A0 =A0at org.springframework.context.support.AbstractApplication=
Context.refresh(AbstractApplicationContext.java:428)
> =A0 =A0 =A0 =A0at org.springframework.context.support.ClassPathXmlApplica=
tionContext.<init>(ClassPathXmlApplicationContext.java:139)
> =A0 =A0 =A0 =A0at org.springframework.context.support.ClassPathXmlApplica=
tionContext.<init>(ClassPathXmlApplicationContext.java:93)
> =A0 =A0 =A0 =A0at com.barcap.gcdit.compressionworkflow.CompressionWorkflo=
w.<init>(CompressionWorkflow.java:20)
> =A0 =A0 =A0 =A0at com.barcap.gcdit.compressionworkflow.CompressionWorkflo=
w.main(CompressionWorkflow.java:16)
> Caused by: org.apache.camel.FailedToCreateRouteException: Failed to creat=
e route route1: Route[[From[ref:direct:errorHandlerRoute]] -> [Log[RAISED E=
X... because of No endpoint could be found for: ref:direct:errorHandlerRout=
e, please check your camel registry with id direct:errorHandlerRoute
> =A0 =A0 =A0 =A0at org.apache.camel.model.RouteDefinition.addRoutes(RouteD=
efinition.java:179)
> =A0 =A0 =A0 =A0at org.apache.camel.impl.DefaultCamelContext.startRoute(De=
faultCamelContext.java:607)
>
>
> My theory is that the errroHandler (which is defined outside the camelCon=
text) cannot refer to a route (which is defined inside the camelContext). =
=A0Given that you said this was straightforward using the Java DSL, does th=
is mean the Spring XML is weaker/deficient? =A0Or have I hust made some obv=
ois blatant error? =A0(Latter is by far the most likely.)
>
>
> Thanks
>
> Steven Hedges
> IT - Credit Booking Derivs
>
>
> -----Original Message-----
> From: Claus Ibsen [mailto:claus.ibsen@gmail.com]
> Sent: 28 September 2010 18:30
> To: users@camel.apache.org
> Subject: Re: Exception details
>
> You need to set the errorHandlerRef attribute on either the <camelContext=
> or the <route> in which the error handler should apply.
>
>
>
> On Tue, Sep 28, 2010 at 6:14 PM, =A0<Steve.Hedges@barclayscapital.com> wr=
ote:
>> Claus
>>
>> I am having difficulty with this as I am using the Spring XML config app=
roach. =A0The errorHandler is defined outside of the camelContext while the=
 routes are defied inside the camel context. =A0At the point at which the e=
rrorHandler is instantiated it cannot see the error route.
>>
>> So I have:
>>
>> =A0 =A0 =A0 =A0<errorHandler id=3D"errorHandler" type=3D"DeadLetterChann=
el"
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0deadLetterUri=3D"direct:errorHandlerRoute=
" />
>>
>> And
>>
>> =A0 =A0 =A0 =A0<camelContext id=3D"camel"
>> xmlns:stp=3D"http://www.barcap.com/gcd/stpengine/1-0">
>> ...
>>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<route id=3D"errorHandlerRoute">
>>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<log message=3D"RAISED EX=
CEPTION: ${exception}"
>> loggingLevel=3D"ERROR"/>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<to ref=3D"JMS_ERROR"/>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</route>
>>
>> ...
>> />
>>
>> I'm guessing that this would not be a problem using the Java DSL. =A0But=
 I really don't want to use that approach. =A0(From a commercial point of v=
iew, ease of writing code in no way outweighs the advantages of having XML =
configs that can be read by support staff at 2am).
>>
>> Your continuing help is much appreciated
>>
>>
>> Steven Hedges
>> IT - Credit Booking Derivs
>>
>>
>> -----Original Message-----
>> From: Claus Ibsen [mailto:claus.ibsen@gmail.com]
>> Sent: 28 September 2010 16:35
>> To: users@camel.apache.org
>> Subject: Re: Exception details
>>
>> On Tue, Sep 28, 2010 at 5:27 PM, =A0<Steve.Hedges@barclayscapital.com> w=
rote:
>>> You realise I am going to have to get my 50 c of help now :-)
>>>
>>> Is it possible to use a route as an error handler? =A0I would like to b=
e able to log an exception, raise an SMS and push the message onto a queue =
for later reprocessing. =A0We are trying to keep all of our config in the S=
pring XML. =A0(Config file releases are much simpler admin-wise than code r=
eleases).
>>>
>>
>> Yeah use the DeadLetterChannel and set the endpoint to a
>> direct:myRoute
>>
>> And then define a route with from("direct:myRoute") and its just like an=
y other route.
>>
>>
>>>
>>> Steven Hedges
>>> IT - Credit Booking Derivs
>>>
>>> -----Original Message-----
>>> From: Claus Ibsen [mailto:claus.ibsen@gmail.com]
>>> Sent: 28 September 2010 16:13
>>> To: users@camel.apache.org
>>> Subject: Re: Exception details
>>>
>>> On Tue, Sep 28, 2010 at 3:46 PM, =A0<Steve.Hedges@barclayscapital.com> =
wrote:
>>>> I've bought the book!
>>>>
>>>
>>> Ah great. Then Jonathan and I earned 50 cent today.
>>>
>>> I hope the book will help and inspire you with your current endeavor wi=
th Camel. Good luck.
>>>
>>>>
>>>>
>>>> Steven Hedges
>>>> IT - Credit Booking Derivs
>>>>
>>>> 10 The South Colonnade
>>>> Canary Wharf,
>>>> London E14 4PU,
>>>> United Kingdom
>>>>
>>>> 02031344655
>>>> x44655
>>>>
>>>> -----Original Message-----
>>>> From: Claus Ibsen [mailto:claus.ibsen@gmail.com]
>>>> Sent: 28 September 2010 14:33
>>>> To: users@camel.apache.org
>>>> Subject: Re: Exception details
>>>>
>>>> On Tue, Sep 28, 2010 at 3:26 PM, =A0<Steve.Hedges@barclayscapital.com>=
 wrote:
>>>>> I'll get the book...
>>>>>
>>>>> From the info on that page, is it correct to assume that it is imposs=
ible to get at the exception info from the Spring XML config? =A0All I want=
 to do is to log the actual exception to a file.
>>>>>
>>>>
>>>> The simple language can access the caused exception using $exception
>>>> See simple http://camel.apache.org/simple
>>>>
>>>> Something like this:
>>>>
>>>> onException(Exception.class).handled(true).transform(simple("Damn
>>>> the problem is $exception.message and
>>>> stacktrace\n$exception")).to("file:errors");
>>>>
>>>> But reading the entire chapter 5 about error handling will help you un=
derstand some of the many features it provides.
>>>> The wiki pages is a bit of a mess here and there for error handling as=
 its a hard topic to document well.
>>>>
>>>>
>>>>>
>>>>>
>>>>> Steven Hedges
>>>>> IT - Credit Booking Derivs
>>>>>
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Claus Ibsen [mailto:claus.ibsen@gmail.com]
>>>>> Sent: 28 September 2010 14:09
>>>>> To: users@camel.apache.org
>>>>> Subject: Re: Exception details
>>>>>
>>>>> On Tue, Sep 28, 2010 at 2:49 PM, =A0<Steve.Hedges@barclayscapital.com=
> wrote:
>>>>>> Hi
>>>>>>
>>>>>> This is probably very straightforward, but I've scoured the docs and=
 can't find an answer.
>>>>>>
>>>>>> Is it possible to get details of the actual exception that
>>>>>> occurred in an error handler? =A0So far, I can see how to access the
>>>>>> message that caused an error (using the $body variable) but not
>>>>>> the exception itself
>>>>>>
>>>>>
>>>>> Yeah if you got the Camel in Action book, see section 5.4.4
>>>>>
>>>>> And you can find also some details about it here
>>>>> http://camel.apache.org/exception-clause.html
>>>>>
>>>>> see section _Using a processor as failure handler_
>>>>>
>>>>>> Thanks in advance
>>>>>>
>>>>>>
>>>>>> Steven Hedges
>>>>>> IT - Credit Booking Derivs
>>>>>>
>>>>>> 10 The South Colonnade
>>>>>> Canary Wharf,
>>>>>> London E14 4PU,
>>>>>> United Kingdom
>>>>>>
>>>>>> 02031344655
>>>>>> x44655
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>>
>>>>>> This e-mail may contain information that is confidential, privileged=
 or otherwise protected from disclosure. If you are not an intended recipie=
nt of this e-mail, do not duplicate or redistribute it by any means. Please=
 delete it and any attachments and notify the sender that you have received=
 it in error. Unless specifically indicated, this e-mail is not an offer to=
 buy or sell or a solicitation to buy or sell any securities, investment pr=
oducts or other financial product or service, an official confirmation of a=
ny transaction, or an official statement of Barclays. Any views or opinions=
 presented are solely those of the author and do not necessarily represent =
those of Barclays. This e-mail is subject to terms available at the followi=
ng link: www.barcap.com/emaildisclaimer. By messaging with Barclays you con=
sent to the foregoing. =A0Barclays Capital is the investment banking divisi=
on of Barclays Bank PLC, a company registered in England (number 1026167) w=
ith its registered office at 1 Churchill Place, London, E14 5HP. =A0This em=
ail may relate to or be sent from other members of the Barclays Group.
>>>>>> _______________________________________________
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> Apache Camel Committer
>>>>>
>>>>> Author of Camel in Action: http://www.manning.com/ibsen/ Open
>>>>> Source
>>>>> Integration: http://fusesource.com
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>> Twitter: http://twitter.com/davsclaus
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> Apache Camel Committer
>>>>
>>>> Author of Camel in Action: http://www.manning.com/ibsen/ Open Source
>>>> Integration: http://fusesource.com
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Twitter: http://twitter.com/davsclaus
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> Apache Camel Committer
>>>
>>> Author of Camel in Action: http://www.manning.com/ibsen/ Open Source
>>> Integration: http://fusesource.com
>>> Blog: http://davsclaus.blogspot.com/
>>> Twitter: http://twitter.com/davsclaus
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Author of Camel in Action: http://www.manning.com/ibsen/ Open Source
>> Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Inte=
gration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>


--=20
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus