qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Stitcher (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (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)'
Date Tue, 18 Jun 2013 21:50:20 GMT

    [ https://issues.apache.org/jira/browse/QPID-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687245#comment-13687245
] 

Andrew Stitcher commented on QPID-4745:
---------------------------------------

I think the new qpidd-p0.py has a mistake - the command line it uses is:

qpidd --socket-fd <n> --disable-listen tcp --port <port of fd n>

I think the --port <...> is in error is seems to try to listen to the same port as the
socket it was passed in!

Also I think that for the python system tests it would make more sense to make this a qpidd
launching class that is used as part of the test setup. This would create a socket pair and
pass one end to the broker and pass the other to the tests to use directly (I think this last
part will need a small amount of implementation in the python code).
                
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message