And from Camel 2.18 onwards you can set it on the <camelContext> which makes it even easier
But in 2.17.x you need to configure it on the <redeliveryPolicy> On Fri, May 27, 2016 at 7:38 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Just look in the XSD schema and you can find where it is. > > On Fri, May 27, 2016 at 7:29 AM, Minh Tran <darth.minhs...@gmail.com> wrote: >> Hi Claus, >> >> Yes I can see on that page there is an option on the Java DSL for >> logExhaustedMessageBody, but how do I do the equivalent on the Spring DSL? >> Should I be expecting to find an attribute on the redeliveryPolicyProfile >> tag to set it? >> >>> On 27 May 2016, at 3:09 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: >>> >>> Hi >>> >>> See bottom of this page >>> http://camel.apache.org/message-history.html >>> >>> On Fri, May 27, 2016 at 2:42 AM, Minh Tran <darth.minhs...@gmail.com> wrote: >>>> Hi >>>> >>>> Prior to camel 2.17.0, when a message redelivery has been exhausted, the >>>> default logs that appear looked something like this >>>> >>>> Exhausted after delivery attempt …. >>>> Message History >>>> Exchange >>>> Stacktrace >>>> >>>> >>>> But from 2.17.0 onwards, I cannot see the Exchange details anymore which >>>> was helpful in determining problems. It now looks like this >>>> >>>> Exhausted after delivery attempt …. >>>> Message History >>>> Stacktrace >>>> >>>> I do not see any options on the <redeliveryPolicyProfile> tag to enable >>>> logging this either. I use the Spring DSL. Does anyone know how I can >>>> re-enable seeing these details? Thanks. >>>> >>>> >>> >>> >>> >>> -- >>> Claus Ibsen >>> ----------------- >>> http://davsclaus.com @davsclaus >>> Camel in Action 2: https://www.manning.com/ibsen2 >> > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
