[
https://issues.apache.org/jira/browse/QPID-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687962#comment-13687962
]
Alan Conway commented on QPID-4745:
-----------------------------------
I can't recall why I put that --port option in there so I'll take it out, as it
does appear incorrect.
Currently the broker for the python system tests is externally launched so
qpidd-p0 can be a drop in replacement. We could move that into the python tests
if there's benefit in doing so. ha_tests.py already such a launcher built in,
but in that case it is doing more work than qpidd-p0, it holds onto ports so
brokers can be restarted on the same port.
> qpidd --port 0 sometimes fails with 'Can't bind to port 0.0.0.0:49337:
> Address already in use (qpid/sys/posix/Socket.cpp:206)'
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4745
> URL: https://issues.apache.org/jira/browse/QPID-4745
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Clustering
> Affects Versions: 0.22
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Minor
>
> Many of the tests use "qpidd --port=0" to start a broker on an available port.
> Thhis sporadically fails with: Can't bind to port 0.0.0.0:49337: Address
> already in use (qpid/sys/posix/Socket.cpp:206)
> Many HA tests use --port=0 to start a broker on an available port, but then
> need to shutdown and restart the broker _on the same port_. This is not safe,
> on a busy system it is possible for another process to take the port between
> the time the broker is shut down and the time it is restarted.
> See also https://bugzilla.redhat.com/show_bug.cgi?id=906277
--
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: [email protected]
For additional commands, e-mail: [email protected]
