Have you considered durable subscribers? That sounds like what you're trying to accomplish.
Keep in mind, though, that ActiveMQ is not a message store. If the subscription consumption is based on user logins and logouts, you are probably trying to do too much without a separate store of some type. Perhaps a database into which messages are stored? The best starting point is to define the following: * the maximum numbers of messages * duration of messages pending * reliability of messaging needed Keep in mind that (a) Topics don't store messages themselves (subscriptions do), and (b) that only durable subscriptions ever persist messages. In other words, non-durable Topic subscriptions will lose messages on broker restarts. -- View this message in context: http://activemq.2283324.n4.nabble.com/Connect-ApacheMQ-with-web-application-using-JMS-tp4676387p4676418.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
