activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-5719) Add clientId and subscriptionName to all durable-related exceptions and log messages within TopicRegion
Date Mon, 13 Apr 2015 20:20:12 GMT
Christopher L. Shannon created AMQ-5719:
-------------------------------------------

             Summary: 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
            Priority: Minor


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)

Mime
View raw message