You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2014/12/01 21:29:12 UTC
[jira] [Resolved] (QPID-4745) 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)'
[ https://issues.apache.org/jira/browse/QPID-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway resolved QPID-4745.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.30
> 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
> Fix For: 0.30
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org