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 <[email protected]> wrote: > 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 ()) { > throw new IllegalStateException("EMFILE"); > } > > But under what circumstances this will happen? > > > > On Tue, Jan 27, 2015 at 4:22 PM, Check Peck <[email protected]> > wrote: > >> I am using ZeroMQ in Java and it was working fine but suddenly I saw this >> exception getting thrown - >> >> java.lang.IllegalStateException: EMFILE >> at zmq.Ctx.create_socket(Ctx.java:300) >> at org.zeromq.ZMQ$Socket.<init>(ZMQ.java:363) >> at org.zeromq.ZMQ$Context.socket(ZMQ.java:312) >> at org.zeromq.ZContext.createSocket(ZContext.java:113) >> >> >> Any idea what could be wrong? I am disconnecting and closing the socket >> as well. >> > > > > _______________________________________________ > 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
