[
https://issues.apache.org/jira/browse/ARTEMIS-3533?focusedWorklogId=667110&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-667110
]
ASF GitHub Bot logged work on ARTEMIS-3533:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 19/Oct/21 16:11
Start Date: 19/Oct/21 16:11
Worklog Time Spent: 10m
Work Description: gtully opened a new pull request #3803:
URL: https://github.com/apache/activemq-artemis/pull/3803
…-ref
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 667110)
Remaining Estimate: 0h
Time Spent: 10m
> Have federation configuration respect extra url parameters from the
> connector-ref
> ---------------------------------------------------------------------------------
>
> Key: ARTEMIS-3533
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3533
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Federation
> Affects Versions: 2.18.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.20.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> a connector ref with a url of the form:
> "tcp://localhost:61616?ackBatchSize=100&consumerWindowSize=-1"
> should be capable of configuring the ServerLocator used by a federation
> client.
> These are ignored by the transport connector but are captured as
> extraParameters in the internal configuration.
> It is simply a case of applying them. currently they are ignored!
> This is better than duplicating additional serverLocator configuration in
> federation configuration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
