Wolf, Yes, almost 100% unresponsive, even closing windows is extremely slow.
The server component is terminated by a single CTRL-C, i.e. it's interrupted....as the main is invoked in a black cmd window. I've also realized that I also had to the terminate the client side to recover 100% responsiveness, this part of the code is running as a webapp in IBM WAS Server It's virutalized in an ESXi server.- Thanks. 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 gvasq...@altiuz.cl http://www.altiuz.cl http://www.altiuzreports.com El 10-04-2013, a las 12:34, Wolfgang Richter <w...@cs.cmu.edu> escribió: > What do you mean by: > > the server get's really "stuck" until I terminate the server component. > > Do you mean your Windows Server becomes almost unresponsive? > > Other processes can't work properly? > > How do you terminate the server component? > > Also, is this in a virtualized/cloud environment, or bare metal Windows > Server? > > -- > Wolf > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
