camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From paquettd <dan.paque...@lmco.com>
Subject Performance and MessageSupport.getBody (1.6.0)
Date Mon, 02 Mar 2009 16:54:48 GMT

I've been seeing some performance problems with Camel 1.6.0 (I have not tried
this with previous versions yet).

My profiler is pointing the finger at MessageSupport.getBody,
TypeConverter.convertTo, and DefaultTypeConverter.findTypeConverter
specifically

findTypeConverter is always throwing a NoTypeConversionAvailableException;
which is then being caught and ignored in MessageSupport.getBody; at which
point processing continues successfully.

protected <T> T getBody(Class<T> type, Object body) is the specific getBody
in question.

Is this exception an expected behavior? It's weird how the catch block
doesn't even log a warning. Should a converter have been found? My message
payload is just a java.lang.String.

I suspect I've done something wrong but I don't know where to start looking.
I'm concerned with this; as I'm comparing Camel to some other message
routing solutions. This is making Camel take 40 times longer than the
competition and I want to make sure I do a fair comparison.
-- 
View this message in context: http://www.nabble.com/Performance-and-MessageSupport.getBody-%281.6.0%29-tp22291841p22291841.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Mime
View raw message