You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Mond Raymond <mo...@gmail.com> on 2011/10/20 14:59:53 UTC
tracing large messages
I had a user today that had camel blow up because he was sending a message
body of 96Mb and had the tracer on. By default the tracer outputs bodies so
he ran out of memory ;-)
Quite an easy fix to configure a formatter and turn off the printing of
message bodies... but it made me think, shouldn't there be a limit (10k,
100k or whatever) which is the default beyond which bodies will not be
printed, unless configured explicitly ... this would prevent users shooting
off their feet.
Thoughts?
Cheers
Ray
--
View this message in context: http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921360.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: tracing large messages
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
There is already options to configure this
http://camel.apache.org/tracer
There is a maxChars option.
Also from Camel 2.8 onwards we will by default not show streams. See
the wiki page if you want to force showing streams.
On Thu, Oct 20, 2011 at 2:59 PM, Mond Raymond <mo...@gmail.com> wrote:
> I had a user today that had camel blow up because he was sending a message
> body of 96Mb and had the tracer on. By default the tracer outputs bodies so
> he ran out of memory ;-)
>
> Quite an easy fix to configure a formatter and turn off the printing of
> message bodies... but it made me think, shouldn't there be a limit (10k,
> 100k or whatever) which is the default beyond which bodies will not be
> printed, unless configured explicitly ... this would prevent users shooting
> off their feet.
>
> Thoughts?
>
> Cheers
>
> Ray
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921360.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: tracing large messages
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Oct 20, 2011 at 11:26 PM, Christian Müller
<ch...@gmail.com> wrote:
> +1 for limited length by default
>
I created a ticket
https://issues.apache.org/jira/browse/CAMEL-4574
>
> On Thu, Oct 20, 2011 at 7:48 PM, Christian Schneider <
> chris@die-schneider.net> wrote:
>
>> Am 20.10.2011 17:09, schrieb Mond Raymond:
>>
>> I think the point is that showBody should be false or at least limited in
>>> length by default
>>>
>>> --
>>> View this message in context: http://camel.465427.n5.nabble.**
>>> com/tracing-large-messages-**tp4921360p4921789.html<http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921789.html>
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>> +1 For limited length
>>
>> --
>>
>> Christian Schneider
>> http://www.liquid-reality.de
>>
>> Open Source Architect
>> Talend Application Integration Division http://www.talend.com
>>
>>
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: tracing large messages
Posted by Christian Müller <ch...@gmail.com>.
+1 for limited length by default
On Thu, Oct 20, 2011 at 7:48 PM, Christian Schneider <
chris@die-schneider.net> wrote:
> Am 20.10.2011 17:09, schrieb Mond Raymond:
>
> I think the point is that showBody should be false or at least limited in
>> length by default
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.**
>> com/tracing-large-messages-**tp4921360p4921789.html<http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921789.html>
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
> +1 For limited length
>
> --
>
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
>
Re: tracing large messages
Posted by Christian Schneider <ch...@die-schneider.net>.
Am 20.10.2011 17:09, schrieb Mond Raymond:
> I think the point is that showBody should be false or at least limited in
> length by default
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921789.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
+1 For limited length
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
Re: tracing large messages
Posted by Mond Raymond <mo...@gmail.com>.
I think the point is that showBody should be false or at least limited in
length by default
--
View this message in context: http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921789.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: tracing large messages
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Oct 20, 2011 at 3:52 PM, Matt Pavlovich <ma...@gmail.com> wrote:
> +1 Tracing just headers is very handy
>
Just turn of body then
showBody=false
http://camel.apache.org/tracer
> On Oct 20, 2011, at 9:28 AM, Daniel Kulp wrote:
>
>> On Thursday, October 20, 2011 3:07:20 PM Claus Ibsen wrote:
>>> On Thu, Oct 20, 2011 at 2:59 PM, Mond Raymond <mo...@gmail.com> wrote:
>>>> I had a user today that had camel blow up because he was sending a
>>>> message body of 96Mb and had the tracer on. By default the tracer
>>>> outputs bodies so he ran out of memory ;-)
>>>>
>>>> Quite an easy fix to configure a formatter and turn off the printing of
>>>> message bodies... but it made me think, shouldn't there be a limit (10k,
>>>> 100k or whatever) which is the default beyond which bodies will not be
>>>> printed, unless configured explicitly ... this would prevent users
>>>> shooting off their feet.
>>>
>>> But yeah maybe the maxChars default should be 10000 or something.
>>
>> Just an FYI: CXF uses 100K for the limit by default.
>>
>>> People can then use -1 or 0 for no limit.
>>> Fell free to create a JIRA. And also work on a patch :)
>>
>> I would say -1 for no limit and 0 for no body. (just log headers) That
>> seems a little more intuitive to me, but that's my opinion.
>>
>> Dan
>>
>>
>>
>>>
>>>> Thoughts?
>>>>
>>>> Cheers
>>>>
>>>> Ray
>>>>
>>>> --
>>>> View this message in context:
>>>> http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921
>>>> 360.html Sent from the Camel - Users mailing list archive at Nabble.com.
>> --
>> Daniel Kulp
>> dkulp@apache.org
>> http://dankulp.com/blog
>> Talend - http://www.talend.com
>
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: tracing large messages
Posted by Matt Pavlovich <ma...@gmail.com>.
+1 Tracing just headers is very handy
On Oct 20, 2011, at 9:28 AM, Daniel Kulp wrote:
> On Thursday, October 20, 2011 3:07:20 PM Claus Ibsen wrote:
>> On Thu, Oct 20, 2011 at 2:59 PM, Mond Raymond <mo...@gmail.com> wrote:
>>> I had a user today that had camel blow up because he was sending a
>>> message body of 96Mb and had the tracer on. By default the tracer
>>> outputs bodies so he ran out of memory ;-)
>>>
>>> Quite an easy fix to configure a formatter and turn off the printing of
>>> message bodies... but it made me think, shouldn't there be a limit (10k,
>>> 100k or whatever) which is the default beyond which bodies will not be
>>> printed, unless configured explicitly ... this would prevent users
>>> shooting off their feet.
>>
>> But yeah maybe the maxChars default should be 10000 or something.
>
> Just an FYI: CXF uses 100K for the limit by default.
>
>> People can then use -1 or 0 for no limit.
>> Fell free to create a JIRA. And also work on a patch :)
>
> I would say -1 for no limit and 0 for no body. (just log headers) That
> seems a little more intuitive to me, but that's my opinion.
>
> Dan
>
>
>
>>
>>> Thoughts?
>>>
>>> Cheers
>>>
>>> Ray
>>>
>>> --
>>> View this message in context:
>>> http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921
>>> 360.html Sent from the Camel - Users mailing list archive at Nabble.com.
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
> Talend - http://www.talend.com
Re: tracing large messages
Posted by Hadrian Zbarcea <hz...@gmail.com>.
+1. Fair enough.
Hadrian
On 10/20/2011 09:28 AM, Daniel Kulp wrote:
> On Thursday, October 20, 2011 3:07:20 PM Claus Ibsen wrote:
>> On Thu, Oct 20, 2011 at 2:59 PM, Mond Raymond<mo...@gmail.com> wrote:
>>> I had a user today that had camel blow up because he was sending a
>>> message body of 96Mb and had the tracer on. By default the tracer
>>> outputs bodies so he ran out of memory ;-)
>>>
>>> Quite an easy fix to configure a formatter and turn off the printing of
>>> message bodies... but it made me think, shouldn't there be a limit (10k,
>>> 100k or whatever) which is the default beyond which bodies will not be
>>> printed, unless configured explicitly ... this would prevent users
>>> shooting off their feet.
>>
>> But yeah maybe the maxChars default should be 10000 or something.
>
> Just an FYI: CXF uses 100K for the limit by default.
>
>> People can then use -1 or 0 for no limit.
>> Fell free to create a JIRA. And also work on a patch :)
>
> I would say -1 for no limit and 0 for no body. (just log headers) That
> seems a little more intuitive to me, but that's my opinion.
>
> Dan
>
>
>
>>
>>> Thoughts?
>>>
>>> Cheers
>>>
>>> Ray
>>>
>>> --
>>> View this message in context:
>>> http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921
>>> 360.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: tracing large messages
Posted by David Karlsen <da...@gmail.com>.
+1 sensible
Den 20. okt. 2011 15:29 skrev "Daniel Kulp" <dk...@apache.org> følgende:
> On Thursday, October 20, 2011 3:07:20 PM Claus Ibsen wrote:
> > On Thu, Oct 20, 2011 at 2:59 PM, Mond Raymond <mo...@gmail.com>
> wrote:
> > > I had a user today that had camel blow up because he was sending a
> > > message body of 96Mb and had the tracer on. By default the tracer
> > > outputs bodies so he ran out of memory ;-)
> > >
> > > Quite an easy fix to configure a formatter and turn off the printing of
> > > message bodies... but it made me think, shouldn't there be a limit
> (10k,
> > > 100k or whatever) which is the default beyond which bodies will not be
> > > printed, unless configured explicitly ... this would prevent users
> > > shooting off their feet.
> >
> > But yeah maybe the maxChars default should be 10000 or something.
>
> Just an FYI: CXF uses 100K for the limit by default.
>
> > People can then use -1 or 0 for no limit.
> > Fell free to create a JIRA. And also work on a patch :)
>
> I would say -1 for no limit and 0 for no body. (just log headers) That
> seems a little more intuitive to me, but that's my opinion.
>
> Dan
>
>
>
> >
> > > Thoughts?
> > >
> > > Cheers
> > >
> > > Ray
> > >
> > > --
> > > View this message in context:
> > >
> http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921
> > > 360.html Sent from the Camel - Users mailing list archive at
> Nabble.com.
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
> Talend - http://www.talend.com
>
Re: tracing large messages
Posted by Daniel Kulp <dk...@apache.org>.
On Thursday, October 20, 2011 3:07:20 PM Claus Ibsen wrote:
> On Thu, Oct 20, 2011 at 2:59 PM, Mond Raymond <mo...@gmail.com> wrote:
> > I had a user today that had camel blow up because he was sending a
> > message body of 96Mb and had the tracer on. By default the tracer
> > outputs bodies so he ran out of memory ;-)
> >
> > Quite an easy fix to configure a formatter and turn off the printing of
> > message bodies... but it made me think, shouldn't there be a limit (10k,
> > 100k or whatever) which is the default beyond which bodies will not be
> > printed, unless configured explicitly ... this would prevent users
> > shooting off their feet.
>
> But yeah maybe the maxChars default should be 10000 or something.
Just an FYI: CXF uses 100K for the limit by default.
> People can then use -1 or 0 for no limit.
> Fell free to create a JIRA. And also work on a patch :)
I would say -1 for no limit and 0 for no body. (just log headers) That
seems a little more intuitive to me, but that's my opinion.
Dan
>
> > Thoughts?
> >
> > Cheers
> >
> > Ray
> >
> > --
> > View this message in context:
> > http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921
> > 360.html Sent from the Camel - Users mailing list archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: tracing large messages
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Oct 20, 2011 at 2:59 PM, Mond Raymond <mo...@gmail.com> wrote:
> I had a user today that had camel blow up because he was sending a message
> body of 96Mb and had the tracer on. By default the tracer outputs bodies so
> he ran out of memory ;-)
>
> Quite an easy fix to configure a formatter and turn off the printing of
> message bodies... but it made me think, shouldn't there be a limit (10k,
> 100k or whatever) which is the default beyond which bodies will not be
> printed, unless configured explicitly ... this would prevent users shooting
> off their feet.
>
But yeah maybe the maxChars default should be 10000 or something.
People can then use -1 or 0 for no limit.
Fell free to create a JIRA. And also work on a patch :)
> Thoughts?
>
> Cheers
>
> Ray
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921360.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/