Hi Claus, Tobias is a colleague of me at EnBW.
I have been able to reproduce the problem with the current HEAD of camel-core. The problem is with the batch processing as all exchanges are stored in a list. I have opened an issue and attached a test and a patch:
https://issues.apache.org/activemq/browse/CAMEL-1652 Greetings Christian -- Christian Schneider --- http://www.liquid-reality.de Claus Ibsen schrieb:
Hi Do you mind trying the SNAPSHOT version of 2.0? A million things have been fixed since 2.0m1. Details how to get it at the downloads page http://camel.apache.org/download.html On Wed, May 27, 2009 at 4:04 PM, Tobias Emmerich <[email protected]> wrote:Hallo, we use the new camel version 2.0-M1 on our project. With this version we have a problem with java heap sapce. After looking about the problem i found out that by using <convertBodyTo> the heap will grow with every xml file we read. I have tested this with a short example: <endpoint id="camel.Input" uri="file://${camel.Input}?sortBy=ignoreCase:file:name&preMove=${camel.Archiv}&initialDealy=1000&delay=500" /> <route> <from ref="camel.Input"> <convertBodyTo type="java.lang.String"> <to uri="bean:orderProcessorDummy?method=processOrder"/> </route> <bean id="orderProcessorDummy" class="OrderProcessorDummy"></bean> The class orderProcessorDummy makes nothing and looks like this: public class OrderProcessorDummy{ public void processOrder(XMLFILE xml){ } } I hope you can help us to find the bug and fix him ;). Thanks for help Tobias -- View this message in context: http://www.nabble.com/convertBodyTo-heap-problem-tp23743181p23743181.html Sent from the Camel - Users mailing list archive at Nabble.com.
