-
1. Re: Question regarding (durable) Topics on remote HornetQ-Server
ataylor May 29, 2012 6:04 AM (in response to pacodelucia)1 of 1 people found this helpfulThere is no difference as to how this works with both an invm and a remote server. The very first time the MDB is deployed the durable subscription will be created, from this point on it will always exist. any messages delivered before this point will be discarded. You need to make sure that the first time you deploy the MDB you make sure no clients are sending messages.
-
2. Re: Question regarding (durable) Topics on remote HornetQ-Server
pacodelucia May 29, 2012 11:14 AM (in response to ataylor)Thanks for your answer. But how would I remove such a durable subscription? Let's assume that an application that was subscribed to a topic is not used anymore. Someone shuts down the application server where the MDB consuming the topic was running. The HornetQ-Server will never know and keep the messages "forever" for this particular consumer. Can I remove such a durable subscription manually?
-
3. Re: Question regarding (durable) Topics on remote HornetQ-Server
ataylor May 29, 2012 11:20 AM (in response to pacodelucia)Thanks for your answer. But how would I remove such a durable subscription? Let's assume that an application that was subscribed to a topic is not used anymore. Someone shuts down the application server where the MDB consuming the topic was running. The HornetQ-Server will never know and keep the messages "forever" for this particular consumer. Can I remove such a durable subscription manually?
Thats sort of the idea with Durable subscriptions, they out last the lifetime of the consumer. If you want ro remove then you will need to use the management API or i think you can do it via the console