On 17/02/2011 11:58, Naira & Kobo wrote:
I am curious, is it the TraceEventHandler that impedes the performance or
the TraceInceptor or the InterceptStrategy?
Well it's definitely not the TraceEventHandler, because unless you
provide one, there isn't one.
Beyond saying that if you want a defin
that writes to the db but also easily plug in
e.g. a live monitoring console.
Christian
-Ursprüngliche Nachricht-
Von: Naira & Kobo [mailto:lekkie.ay...@gmail.com]
Gesendet: Donnerstag, 17. Februar 2011 12:59
An: users@camel.apache.org
Betreff: Re: Camel Tracer impedes perform
it can still be
completed as if the tracer were not turned on. How long its takes traces to
be log is not a big deal as it is a trace, so it can take for as long it
wants to - reasonably though.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Tracer-impedes-performance-tp
On 17/02/2011 11:21, Naira & Kobo wrote:
Thanks a lot for your response.
Whats is the name of the default trace event handler used by camel tracer?
I 'd like to take a look at that class and see how I can optimize it.
I will actually prefer if messages intercepted and logged in a separate
thr
This way, the main exchange can keep
running without having to be blocked/impeded by the trace handler.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Tracer-impedes-performance-tp3389173p3389254.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On 17/02/2011 10:01, Naira & Kobo wrote:
Hi,
I noticed that extending the camel tracer to log exchange data into the
database impedes performance on the ESB.
I followed the example in the camel samples, where I defined a direct
endpoint
http://ca
. (May be
its just my imagination)
It is also noteworthy that the main route uses vm and the preferred endpoint
uri while the log interfaces uses the direct uri.
Is there another way, I can efficiently do this?
kr.
--
View this message in context:
http://camel.465427.n5.nabble.com/Ca
