[jira] [Commented] (QPID-4931) Broker should only listen to a single network address if --port 0 is specified
[ https://issues.apache.org/jira/browse/QPID-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688073#comment-13688073 ] ASF subversion and git services commented on QPID-4931: --- Commit 1494656 from [~astitcher] [ https://svn.apache.org/r1494656 ] QPID-4931: Only allow broker to listen to a single address if --port 0 specified - If more than one address is specified or implied by the defaults the broker will log a warning - This is intended to avoid testing problems where the broker fails to connect to the port of subsequent listening addresses Broker should only listen to a single network address if --port 0 is specified Key: QPID-4931 URL: https://issues.apache.org/jira/browse/QPID-4931 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: Andrew Stitcher Assignee: Andrew Stitcher The C++ broker has a setting which is really only useful for testing which allows the broker to listen to whichever port the kernel gives it. In this mode it prints the received port on stdout for subsequent testing programs to use. When you listen to multiple network addresses (addresses are multiple network interfaces or multiple protocols on the same network interface - IPv4 IPv6 for example) the broker has to remember the port it got for the first address and then try to get the same port for subsequent addresses. Unfortunately there is no guarantee that the same port will actually be available on the other addresses so the entire broker startup can fail. In the testing environment which this is useful for you only care about the IPv4 loopback address in any case so we have to ensure that this address is the only (or at least the first) address used. Because we can't guarantee getting the same port for more than one address it makes sense to restrict --port 0 to only listening to a single address. I propose that if the broker detects that more than one address has been specified or is implied by the network setup it should list to the first address and log a warning message with the actual address listened to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4931) Broker should only listen to a single network address if --port 0 is specified
[ https://issues.apache.org/jira/browse/QPID-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688225#comment-13688225 ] ASF subversion and git services commented on QPID-4931: --- Commit 1494712 from [~astitcher] [ https://svn.apache.org/r1494712 ] QPID-4931: Remove removed member function from windows SocketAddress code too. While there bring this code up to date with other recent changes to the POSIX equivalent code. Broker should only listen to a single network address if --port 0 is specified Key: QPID-4931 URL: https://issues.apache.org/jira/browse/QPID-4931 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: 0.23 The C++ broker has a setting which is really only useful for testing which allows the broker to listen to whichever port the kernel gives it. In this mode it prints the received port on stdout for subsequent testing programs to use. When you listen to multiple network addresses (addresses are multiple network interfaces or multiple protocols on the same network interface - IPv4 IPv6 for example) the broker has to remember the port it got for the first address and then try to get the same port for subsequent addresses. Unfortunately there is no guarantee that the same port will actually be available on the other addresses so the entire broker startup can fail. In the testing environment which this is useful for you only care about the IPv4 loopback address in any case so we have to ensure that this address is the only (or at least the first) address used. Because we can't guarantee getting the same port for more than one address it makes sense to restrict --port 0 to only listening to a single address. I propose that if the broker detects that more than one address has been specified or is implied by the network setup it should list to the first address and log a warning message with the actual address listened to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
