[ https://issues.apache.org/jira/browse/ARTEMIS-3533?focusedWorklogId=667545&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-667545 ]
ASF GitHub Bot logged work on ARTEMIS-3533: ------------------------------------------- Author: ASF GitHub Bot Created on: 20/Oct/21 08:44 Start Date: 20/Oct/21 08:44 Worklog Time Spent: 10m Work Description: gtully merged pull request #3803: URL: https://github.com/apache/activemq-artemis/pull/3803 -- 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: gitbox-unsubscr...@activemq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 667545) Time Spent: 20m (was: 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: 20m > 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)