Also, you could write a utility program that would connect with that client ID and subscription name and perform an unsubscribe on the consumer's behalf. You're essentially impersonating the consumer for this one purpose, but given what you're doing, that's probably not an issue.
Tim On Fri, Sep 18, 2015 at 7:04 PM, Tim Bain <tb...@alumni.duke.edu> wrote: > Have you looked in JConsole to see if there are any actions exposed via > JMX that would allow you to remove that subscription? I've never run 5.7.0 > so I can't say whether anything is available in that version (or any > version, for that matter), but it's where I'd look. > On Sep 18, 2015 7:01 AM, "tras" <tra...@ccbilleu.com> wrote: > >> Thanks for your reply. Yes true, however the issue is that that durable >> client ID cannot be deleted and messages are not being consumed since its >> offline thus we are running out of storage. This means that when using >> activemq 5.7, we are stuck with a useless offline subscription. >> >> Is there a workaround we can do to delete that offline subscription, until >> we upgrade the version of activemq from 5.7? >> >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/Managing-Inactive-Offline-Durable-Subscription-tp4702061p4702091.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >
