Seriously? Take your pick, either the DestinationManager throws an exception when you try and delete a destination that is in use, or all the clients producing/consuming that destination get an exception. I know which one I'd choose...
Fair enough. But after the stack trace I get when trying to destroy the Topic there is an info log message saying topic destroyed and it is no longer possible to connect / subscribe to the topic.
I would exect the destroy either to fail completely or to succeed completely, but this seems a bit inconsistend.
LOL, so you're saying that you get both. That would be bug in my opinion. I reccommend you either submit it via SourceForge or modify the destination manager and submit a patch.