qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Moravec (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (QPID-5859) Qpidd only listens to protocols that are already up when it starts
Date Tue, 01 Jul 2014 14:49:24 GMT

     [ https://issues.apache.org/jira/browse/QPID-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Pavel Moravec reopened QPID-5859:

The upstream commit r1606197 made a regression for my qpid brokers on RHEL6 VM, where an attempt
to start a broker (with network fully operational on one NIC, TCP/IP v4 and v6, though virtualized)
fails with:

critical Unexpected error: Address family not supported by protocol (/data_xfs/qpid/cpp/src/qpid/sys/posix/BSDSocket.cpp:102)

> Qpidd only listens to protocols that are already up when it starts
> ------------------------------------------------------------------
>                 Key: QPID-5859
>                 URL: https://issues.apache.org/jira/browse/QPID-5859
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>            Reporter: Andrew Stitcher
>            Assignee: Andrew Stitcher
>             Fix For: 0.29
> When you run qpidd as a service it might be started before networking is fully configured,
but the network may work later on.
> Currently qpidd will only listen to protocols that have a global address configured configured
on a non loopback address.
> It would be better to not make this requirement and to listen anyway. That way if the
protocol becomes available after qpidd has started it should work "automatically"

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message