Hi Troy,
I ran into this same issue on my Windows box install today. I was in
the process of putting together a new system for handling queries on a
web site. I had a web front end (linux), a queue device broker
(windows), and numerous workers (windows) in the backend processing
queries.
I
I ran into this same issue on my Windows box install today. I was in
the process of putting together a new system for handling queries on a
web site. I had a web front end (linux), a queue device broker
(windows), and numerous workers (windows) in the backend processing
queries.
I am using pyzmq
2010/11/16 Martin Sustrik sust...@250bpm.com:
If someone actually tests that setting FD_SETSIZE to 1024 in 0MQ MSVC
project doesn't break client applications with different FD_SETSIZE
values (say default 64), I'll apply the change straight away.
I think it's not good idea. Maybe I don't
On 11/16/2010 09:33 AM, Олег Севостьянов wrote:
push into fds descriptors, but where is pop?
Here it is:
// Destroy retired event sources.
if (retired) {
fds.erase (std::remove_if (fds.begin (), fds.end (),
zmq::select_t::is_retired_fd), fds.end
Am 16.11.2010 10:21, schrieb Martin Sustrik:
More or less. It would be nice to call select() in client app to see
whether it works ok.
Is there a particular patch I should apply to master beforehand?
Christian
___
zeromq-dev mailing list
2010/11/16 Martin Sustrik sust...@250bpm.com:
Nope. Yust set FD_SETSIZE to 1024 in 0MQ MSVC project.
I try to change select.cpp - remove FD_SETSIZE and set 1024 as const,
and then run my test.
// Ensure we do not attempt to select () on more than FD_SETSIZE
// file descriptors.
Am 16.11.2010 10:27, schrieb Олег Севостьянов:
I try to change select.cpp - remove FD_SETSIZE and set 1024 as
const, and then run my test.
FD_SETSIZE is used internally by the Winsock headers as well so just
replacing it with a constant in the 0MQ sources will not do the trick.
Did you
On Tue, Nov 16, 2010 at 10:27 AM, Олег Севостьянов oleg@gmail.com wrote:
I try to change select.cpp - remove FD_SETSIZE and set 1024 as const,
and then run my test.
You can either:
* #define FD_SETSIZE 1024 in the 4 places that 0MQ includes
winsock.h or winsock2.h (zmq.h, select.cpp,
On Tue, Nov 16, 2010 at 10:35 AM, Pieter Hintjens p...@imatix.com wrote:
* #define FD_SETSIZE 1024 in the 4 places that 0MQ includes
winsock.h or winsock2.h (zmq.h, select.cpp, select.hpp,
windows.hpp afair)
Sorry, I'm not being clear. You need to define FD_SETSIZE _before_
including
Am 16.11.2010 10:21, schrieb Martin Sustrik:
More or less. It would be nice to call select() in client app to see
whether it works ok.
FD_SETSIZE is still #defined to 64 in client applications even if 0MQ
itself got compiled with FD_SETSIZE=1024. select() still appears to
work, but that's no
2010/11/16 Pieter Hintjens p...@imatix.com:
On Tue, Nov 16, 2010 at 10:27 AM, Олег Севостьянов oleg@gmail.com wrote:
You can either:
* -DFD_SETSIZE=1024 in the project
I add -DFD_SETSIZE=1024 in the project under Compiler-Command Line,
rebuild libzmq.dll and my test application. Test fail
Oleg,
I add -DFD_SETSIZE=1024 in the project under Compiler-Command Line,
rebuild libzmq.dll and my test application. Test fail with unhadled
exception in own.cpp:141, fnd with 0MQ error message before - Too
many open files.
I've checked your code. You are creating connection in a loop. You
Hi.
I have error assertion failed: fds.size() = FD_SETSIZE in
select.cpp:67 when run test application
(http://pastebin.com/KKu1Vxet). 0MQ sources last from git.
Assert failed stable on 65 cycle in call zmq::select_t::handle_t
zmq::select_t::add_fd (fd_t fd_, i_poll_events *events_).
--
С
Hi Олег,
You're running on Windows, right?
Could you check that FD_SETSIZE is defined in the Windows project to be 1024?
-Pieter
On Tue, Nov 16, 2010 at 8:28 AM, Олег Севостьянов oleg@gmail.com wrote:
Hi.
I have error assertion failed: fds.size() = FD_SETSIZE in
select.cpp:67 when run
Pieter,
Could you check that FD_SETSIZE is defined in the Windows project to be 1024?
Not yet.
I haven't have time to actually test the change :(
If someone actually tests that setting FD_SETSIZE to 1024 in 0MQ MSVC
project doesn't break client applications with different FD_SETSIZE
15 matches
Mail list logo
