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

Improve CLI commands error handling

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 5.12.0
    • 5.13.0
    • None
    • None

    Description

      It's a bit messy at the moment as lot of commands check if broker is running or not, before executing. That leads to problems like not being able to run producer/consumer commands when broker is not running.

      The better approach is to fix commands to print meaningful errors when they can't connect to the service (jmx or jms) and leave this logic out of CLI scripts.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dejanb Dejan Bosanac
            dejanb Dejan Bosanac
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment