Hallo,
we have found out a fix for the problem. We think the problem is that camel
do not free the exchange as long it found new files.
The fix is like this:
<route>
<from ref="camel.Input">
<convertBodyTo type="java.lang.String">
<to uri="bean:orderProcessorDummy?method=processOrder"/>
<to uri="bean:cleanProcessor?method=clean" />
</route>
The CleanProcessor class looks like this:
public class CleanProcessor {
public void clean(Exchange exchange){
exchange.getIn().setBody(null);
}
}
After using the CleanProcessor we have got no heap memory problems.
greetings
Tobias
--
View this message in context:
http://www.nabble.com/convertBodyTo-heap-problem-tp23743181p23743975.html
Sent from the Camel - Users mailing list archive at Nabble.com.