At the moment durable subscriptions on a topic must be managed manually, i.e. clients need to gracefully disconnect and clean up their subscription, or a subscription can be cleaned up via jconsole. It would be nice if the broker had a subscription eviction policy that could be configured for a topic, some possible criteria could be: 1. Maximum number of pending messages stored in the subscription, i.e. hit this number X number of times and the subscription is evicted 2. Maximum cursor memory usage in the subscription, again, maybe if this limit is reached X number of times the subscription is evicted 3. Maximum amount of time since the subscription went idle (i.e. the subscriber disconnected and no messages are being dispatched to it) when reached the subscription is evicted.