Description
In order to make it easier to debug durable related issues it would be useful if the error messages included the clientId and subscriptionName.
The specific use case for this was that a client tried to remove their durable subscription using the wrong clientId and received an error message which did not include the clientId so it was difficult to debug.
The error received just said: javax.jms.InvalidDestinationException: No durable subscription exists for: <subscriptionName>
It would be more useful if the error was: javax.jms.InvalidDestinationException: No durable subscription exists for clientId: <clientId> and subscriptionName: <subscriptionName>
I will be attaching a pull request to this ticket with the 2 specific exception messages I would like to see changed in TopicRegion.