Within the broker, if your messages are marked persistent, they will be stored on disk (in your KahaDB) until they are delivered to a consumer and the consumer acks them.
It sounds like your camel route is building them up in memory, not the broker. Run your route in a transaction so that when camel consumes the message, it won't ack it unless it's been persisted to the DB. http://camel.apache.org/transactional-client.html On Thu, Oct 11, 2012 at 6:25 AM, guerra <jg.gue...@gmail.com> wrote: > The broker is queueing up messages in RAM. When I start the database again > the messages are dequeued and sent okay to the database, but from memory. I > am using the camel monitor and the seda queue is building up messages > continuously . My point is why this messages are not stored on disk and if > there is a way to do it. > To be honest, I am not sure whether I am missing something or I am doing > something wrong, but my tests shed this behaviour. > Thanks > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/On-disk-persisted-message-queues-on-consumer-failure-tp4657706p4657720.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog
