Hi, The functionality you are describing is handled by a Retroactive Consumer and governed by Subscription Recovery Policy. You can read about these features at the links below. Be sure to read the limitations of retroactive consumers.
http://activemq.apache.org/retroactive-consumer.html http://activemq.apache.org/subscription-recovery-policy.html Clark PS Great to hear ActiveMQ is being used in the cloud! Would love to hear if you are scaling ActiveMQ across images or using ActiveMQ as a cloud entry point. www.ttmsolutions.com ActiveMQ reference guide at http://bit.ly/AMQRefGuide andy95014 wrote: > > I try to use ActiveMQ in a cloud computing environment. All consumers are > durable, since they could not afford to miss any msgs. The challenge is to > ensure durable consumers to receive previously published msgs. > > Let's say that a persistent msg M arrives for a brand new topic T, and we > don't have any durable subscribers for T at that point. I need to make > sure that such a msg M will be reliablly delivered to future subscribers, > even if those subscribers show up after restart of AQ broker. > > Thanks in advance for any suggestions. > -- View this message in context: http://old.nabble.com/Enable-durable-subscribers-to-receive-previously-published-msgs-tp29311406p29315174.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
