[
https://issues.apache.org/jira/browse/AMQ-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5719.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.12.0
Assignee: Timothy Bish
Applied to master for 5.12.0
> Add clientId and subscriptionName to all durable-related exceptions and log
> messages within TopicRegion
> -------------------------------------------------------------------------------------------------------
>
> Key: AMQ-5719
> URL: https://issues.apache.org/jira/browse/AMQ-5719
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.11.1
> Reporter: Christopher L. Shannon
> Assignee: Timothy Bish
> Priority: Minor
> Labels: easyfix
> Fix For: 5.12.0
>
>
> 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}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
