oslo.messaging/oslo/messaging/_drivers
Elena Ezhova 0d49793e34 Create ZeroMQ Context per socket
ZeroMQ Context is a singleton and thus is created only once. This leads
to problems when there is more than one process working with it.
For example, while Neutron server starts, it firstly loads core
plugin and service plugins, which start message handling server,
and only then forks to create api-workers. As a result, all child
processes get the same copy of the context.

Creating new Context for each socket will prevent such situations
from happening and will guarantee that each process works with its
own Context.

Change-Id: I56912e39b119c20f6f23311fc2c7c4b9e9e480d0
Closes-Bug: #1364814
2014-11-18 18:18:07 +03:00
..
protocols Merge "Add missing deprecated group amqp1" 2014-10-23 00:21:49 +00:00
__init__.py Remove copyright from empty files 2014-01-04 10:33:58 +08:00
amqp.py Improve help strings 2014-08-28 06:59:33 +02:00
amqpdriver.py Don't put the message payload into warning log 2014-10-28 11:38:14 +01:00
base.py Cleanup listener after stopping rpc server 2014-09-23 03:35:43 -07:00
common.py Enable oslo.i18n for oslo.messaging 2014-09-24 22:18:50 -04:00
impl_fake.py Fixes incorrect exchange lock in fake driver 2014-07-15 12:20:16 +00:00
impl_qpid.py Merge "qpid: Always auto-delete queue of DirectConsumer" 2014-10-28 20:51:56 +00:00
impl_rabbit.py Enable oslo.i18n for oslo.messaging 2014-09-24 22:18:50 -04:00
impl_zmq.py Create ZeroMQ Context per socket 2014-11-18 18:18:07 +03:00
matchmaker.py Enable oslo.i18n for oslo.messaging 2014-09-24 22:18:50 -04:00
matchmaker_redis.py Switch to oslo.utils 2014-08-27 14:14:00 +02:00
matchmaker_ring.py Enable oslo.i18n for oslo.messaging 2014-09-24 22:18:50 -04:00
pool.py Apply six for metaclass 2013-10-14 14:10:31 -04:00