You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2015/09/04 15:52:45 UTC

[jira] [Commented] (AMQ-5956) Improve CLI commands error handling

    [ https://issues.apache.org/jira/browse/AMQ-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730849#comment-14730849 ] 

clebert suconic commented on AMQ-5956:
--------------------------------------

I have tried for instance to run the producer against artemis and I wasn't able to.

It would be nice to remove that check. I didn't have time to see what to change.. sorry about that.

> Improve CLI commands error handling
> -----------------------------------
>
>                 Key: AMQ-5956
>                 URL: https://issues.apache.org/jira/browse/AMQ-5956
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.12.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.13.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)