Hi *!
I found the bug that I thought to be caused by
EINTR:
The EINTR-thingy was gone, when I fixed some illegal refference
usages, that the gcc compiler didn't complain about (but clang of LLVM
did ;o)
... the lost messages problem was still there.
BUT: when I
switched from ZMQ2 to
In CZMQ v3 the context is hidden and zctx is deprecated.
However if you use the old CZMQ v2 API, or you use the libzmq API
directly, you should be able to use multiple contexts safely.
If you've a short example that shows the problem, we can investigate.
-Pieter
On Tue, Jan 27, 2015 at 10:05
Closing sockets is asynchronous. Are you opening/closing sockets very
quickly? That could cause it to run out of empty slots.
On 1/27/15 8:34 PM, Check Peck wrote:
In Ctx.java class, I saw this line -
// If max_sockets limit was reached, return error.
if (empty_slots.isEmpty ()) {
Yes it looks like we are opening/closing pretty quickly. Does creating
sockets is asynchronous too? And should we deal with closing sockets if it
is asynchronous?
On Tue, Jan 27, 2015 at 6:44 PM, Colin Ingarfield co...@ingarfield.com
wrote:
Closing sockets is asynchronous. Are you
And we are using 0.3.4 version of ZeroMQ -
dependency
groupIdorg.zeromq/groupId
artifactIdjeromq/artifactId
version0.3.4/version
/dependency
Also, where does in the code of ZeroMQ mentions that closing sockets is
asynchronous? We are calling disconnect and then
Is it safe to close issue #1302
https://github.com/zeromq/libzmq/issues/1302 now?
On Wed, Jan 21, 2015 at 8:13 PM, Tomas Krajca to...@repositpower.com
wrote:
Hi Thomas,
I can't reproduce the error against the latest libzmq trunk either. It
must have been fixed fairly recently because we
In Ctx.java class, I saw this line -
// If max_sockets limit was reached, return error.
if (empty_slots.isEmpty ()) {
throw new IllegalStateException(EMFILE);
}
But under what circumstances this will happen?
On Tue, Jan 27, 2015 at 4:22 PM, Check Peck
