Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-5719

Add clientId and subscriptionName to all durable-related exceptions and log messages within TopicRegion

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 5.11.1
    • 5.12.0
    • Broker

    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.

      Attachments

        Activity

          People

            tabish Timothy A. Bish
            cshannon Christopher L. Shannon
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: