[ 
https://issues.apache.org/jira/browse/ARTEMIS-2723?focusedWorklogId=424895&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-424895
 ]

ASF GitHub Bot logged work on ARTEMIS-2723:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Apr/20 14:04
            Start Date: 18/Apr/20 14:04
    Worklog Time Spent: 10m 
      Work Description: brusdev commented on pull request #3092: ARTEMIS-2723 
Read the default CLI connector from the related broker
URL: https://github.com/apache/activemq-artemis/pull/3092
 
 
   Read the CLI connector from the related broker instance if it isn't set by 
user.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 424895)
    Remaining Estimate: 0h
            Time Spent: 10m

> Read the default CLI connector from the related broker
> ------------------------------------------------------
>
>                 Key: ARTEMIS-2723
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2723
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Domenico Bruscino
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Artemis CLI accesses to the port of the broker through core protocol for many
> commands. However, when several brokers are installed on a single machine, 
> all the installed `artemis` command for each broker operate only one broker 
> that have `tcp://localhost:61616` by default.
> This behavior is difficult to understand and could lead to incorrect 
> operations for the different broker. The default connector could be read from 
> the broker where you are related.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to