Are you eventually going to separate these queues in different locations? One thing that's happening when you use JMS this way is you read the records in, and then you immediately write them back out over a socket and then read them back in. Those all involve duplication of memory.
Since you may be doing it for transactional purposes then you need to make sure your LevelDB is set up to handle the data you send to it. I've used KahaDB with AMQ but not LevelDB though they are for the same purposes. In this case you'll need to specify the maximum number of in memory objects and then set policies for physical storage of the elements on disk. http://activemq.apache.org/xml-configuration.html -- View this message in context: http://camel.465427.n5.nabble.com/Best-Strategy-to-process-a-large-number-of-rows-in-File-tp5779856p5780053.html Sent from the Camel - Users mailing list archive at Nabble.com.