[zeromq-dev] Frequent error messages

[Gonzalo Vasquez]

That worked liked a charm!

I moved the context into the following line:

private Context ctx = ZMQ.context(1);

And commented out this line:

		//ctx.term();

How being too "clean" would harm the context creation/termination process?

In this new scenario the context will never be terminated as it'll linger idle in the application (webapp) as long as the app is running. Is there some kind of cleansing process I could use to ensure stability?


Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (R&D)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes - CP 7550099
+56 2 335 2461
gvasquez at altiuz.cl
http://www.altiuz.cl
http://www.altiuzreports.com
  


El 11-03-2013, a las 23:25, Trevor Bernard <trevor.bernard at gmail.com> escribió:

> In your private byte[] getByte(...), I see that you create and destroy
> our context each time it's called. I would try creating only one
> context for your client process and see if that helps your
> reliability.
> 
> http://zguide.zeromq.org/page:all#Getting-the-Context-Right
> 
> -Trev
> 
> On Mon, Mar 11, 2013 at 10:59 PM, Trevor Bernard
> <trevor.bernard at gmail.com> wrote:
>> 
>>> So aside, from a version number increase, and few changed comments, there
>>> doesn't seem be any real software upgrade, i.e. no src files modified, am I
>>> wrong?
>> 
>> 
>> There should have been a few files changed:. This is the diff from the
>> v2.1.2 tag with master:
>> 
>> https://github.com/zeromq/jzmq/compare/v2.1.2...master
>> 
>> Also I assume this was happening on the Mac client side since the error was
>> kqueue related?
>> 
>> I try to reproduce on it from my Mac.
>> 
>> -Trev
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev