Open Stack

eventlet.moneky_patch(all=True, os=False, select=False, socket=False,
thread=False, time=False)

Since eventlet.monkey_patch works with smaller scope, if Quantum only
needs to monkey_patch a few smaller area, (say socket/thread), and
what qpidd needs to make reconnection work (say select) happens to
fall out of this scope, you are lucky.  If it's not, I have no idea...

On Mon, Nov 5, 2012 at 6:55 PM, Gary Kotton <gkotton at redhat.com> wrote:
> Hi,
> I have the encountered following problem
> (https://bugs.launchpad.net/quantum/+bug/1073999). The Quantum service and
> qpid daemon are running on the same host. If the Quantum service starts and
> the QPIDD daemon is not running then the Quantum service will hang in the
> callself.connection.open()
> (https://github.com/openstack/quantum/blob/master/quantum/openstack/common/rpc/impl_qpid.py#L357).
> When QPID starts/restarts the Quantum service is still waiting on a file
> descriptor here and never recovers. The work around is to restart the
> Quantum service.
> If I comment out the lineeventlet.monkey_patch()
> (https://github.com/openstack/quantum/blob/master/bin/quantum-server#L25)
> then the logs indicate that the re-connection to qpidd is attempted - the
> problem here is that the RPC requires that monkey patch.
> Any help or input will be greatly appreciated.
> Thanks
> Gary
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Regards
Huang Zhiteng