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

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

                Author: ASF GitHub Bot
            Created on: 19/Oct/19 23:55
            Start Date: 19/Oct/19 23:55
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on issue #2866: ARTEMIS-2523 
Deprecate the parameter failoverOnInitialConnection
URL: https://github.com/apache/activemq-artemis/pull/2866#issuecomment-544206991
 
 
   LGTM however there's a real test failure shown on the PR check. We can merge 
this after fixed.
 
----------------------------------------------------------------
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: 330997)
    Time Spent: 20m  (was: 10m)

> Deprecate the parameter failoverOnInitialConnection
> ---------------------------------------------------
>
>                 Key: ARTEMIS-2523
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2523
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>            Reporter: Domenico Bruscino
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The parameter failoverOnInitialConnection wouldn't seem to be used and I can't
> understand the sense of this parameter because the failover will not occur
> if the client fails to make an initial connection to the live server
> ([https://activemq.apache.org/components/artemis/documentation/latest/ha.html#failing-over-on-the-initial-connection]).
>  So I think the parameter could be deprecated from the API.
> The topic is discussed at 
> [https://activemq.markmail.org/thread/ryf32vhjrwc4e7yf]



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

Reply via email to