On Sat, Nov 12, 2011 at 1:36 AM, awillia <antony.willi...@fronde.com> wrote: > Thanks Claus, 2.9 is not officially released yet is it? > > Sorry have another question. If I was to use this to schedule messages would > I be able to hold many messages, (eg. 1000), or does it hold onto a thread > and so would cause me performance problems? > > Would it be better to use something like quartz to try and schedule these > messages for later. >
Its best to only take out messages from the message broker when you need them. There is AFAIR an JMS property you can set which has a sort of instruction when the message is "visible" for consumers. As well there is a property when the message expires. However using this you most likely need to ensure the clients and brokers are in sync in terms of clock. ActiveMQ have a timstamp plugin that can help ensure this. If you use the Camel Delayer then the messages is stored in-memory only. It uses a scheduled thread pool to know when the message should continue. > regards > Antony > > -- > View this message in context: > http://camel.465427.n5.nabble.com/asyncDelayed-does-not-appear-to-work-tp4983202p4985966.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
