Christian already gave you a few solutions. RecoveryPolicy is probably close to what you want, if you are prepared to write a little bit of code you can solve the problem quite nicely with temp queues and a subscription system.
Durable subscribers are just a headache. Apollo and stomp won't do more for you on this would be my suspicion. /je On Sep 6, 2013, at 3:01 PM, AlexP <apara-activ...@standardset.com> wrote: > This question is a result of me realizing that there are somewhat conflicting > requirements that I need to implement using ActiveMQ 5.8.0 and I am not sure > if it's at all possible to get these requirements satisfied. > > SCENARIO: > A backend server needs to send a message to a user accessing a web > application. > > REQUIREMENTS: > 1) If the user is not logged in, queue up the message and serve up later > (DURABLE subscription) > > 2) If the user is logged in and has multiple windows open, display the same > message in multiple windows (multiple consumers). > > From what I read, it is not possible to have multiple consumers on a DURABLE > subscription. In fact, this is an issue resolve with JMS 2.0 with this > enhancement: https://java.net/jira/browse/JMS_SPEC-40 > > Is there anything in ActiveMQ that would allow me to implement multipole > consumers on a single durable subscription? Alternatively, what version of > JMS does Apollo 1.6 implement? Can I use Apollo to resolve this issue? > > Thanks. > -AP_ > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/How-to-implement-these-somewhat-conflicting-requirements-tp4671268.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
