the Durable Elvis Problem

[pohl]

Let's say I have a durable subscriber on a topic, happily consuming messages. Let's call him Elvis. If Elvis goes away, jbossmq keeps messages for him because that's what being "durable" means.

Let's say that we no longer need Elvis and we want to make him go away, with no intention of bringing him back.

Jbossmq, being a big fan of Elvis, will keep waiting for his return. Alas, like the real Elvis, our durable subscriber will never return.

What is the right way to convince the hapless Elvis fan (jbossmq) to go on with its life and stop persisting messages for him?

From a larger perspective, how do other JMS providers handle this problem?

[hchirino]

A durable subscription is a managed resource. Currently it is setup in the jbossmq-state.xml file.

Just remove that section of XML and restart the server:

Elvis
testDurableTopic

[hunterhillegas]

JBossMQ is doomed to stay outside Elvis' house for eternity and be sure he is coming back.

[fstarsinic]

durable topics can have timeouts set so the messages go away after a specified time.