Is this related to the following issue? https://github.com/zeromq/libzmq/issues/792
In the issue, the problem only occurs with inproc transport, as also used by you. On 25 Feb 2014 16:36, "Laurent Alebarde" <[email protected]> wrote: > You are right. Possibly a bug in the lib ? > > Le 24/02/2014 18:13, Olaf Mandel a écrit : > > Am 24.02.2014 18:04, schrieb Laurent Alebarde: > > By default, you are allowed 1024 sockets per context. After having > created the context, you shall increase the quantity of sockets allowed: > > rc = zmq_ctx_set (ctx, ZMQ_MAX_SOCKETS, 10000); > assert (rc == 0); > > > -Snipp- > > Hello Laurent, > > maybe I am just unclear on the documentation and intended behaviour: is > ZMQ_MAX_SOCKETS intended to be the number of sockets for the context at > any one time or is it the absolute number of sockets that may be created > over the life-time of the context? > > In the latter case I don't think REQ-REP with e.g. the Lazy Pirate > Pattern work for long-running programs: they would eventually run out of > sockets to create. > > Best regards, > Olaf Mandel > > > > > > _______________________________________________ > zeromq-dev mailing > [email protected]http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
