On 11/07/2012 01:52 PM, Gary Kotton wrote:
On 11/07/2012 01:49 PM, Gordon Sim wrote:
On 11/07/2012 11:36 AM, Gary Kotton wrote:
On 11/07/2012 01:12 PM, Gordon Sim wrote:
On 11/07/2012 08:08 AM, Gary Kotton wrote:
Hi,
I'm Gary and working on the OpenStack project. We have run into a
problem with eventlet monkey patching QPID. We are using python.
If the
service that I am running starts before qpidd then it hangs and
does not
recover. Even when the qpidd daemon starts it does not recover.
If qpidd is running before you start the patched client, but is then
stopped and restarted, does the client manage to reconnect?
sadly not.
Does setting the reconnect option to false have any effect? Does the
connection then fail as expected, or does it still hang?
The connect fails and does not hang.
There is a problem here too. The first iteration returnd "Connection
refused". The second returns "already open". This is due to the fact
that the flag for the open is set prior to the connection actually being
open.
2012-11-07 13:57:50 14161 ERROR quantum.openstack.common.rpc.impl_qpid
[-] Unable to connect to AMQP server: [Errno 111] Connection refused
2012-11-07 13:57:51 14161 ERROR quantum.openstack.common.rpc.impl_qpid
[-] Unable to connect to AMQP server: None(already open)
2012-11-07 13:57:52 14161 ERROR quantum.openstack.common.rpc.impl_qpid
[-] Unable to connect to AMQP server: None(already open)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
