On 01/31/2011 05:43 PM, Dhammika Pathirana wrote: > Try something like 512k, but I don't know about your app/traffic pattern. > These are system wide settings so you'd want to be stingy.
There's one problem with 0mq architecture that may be the cause of the problem. Namely, the I/O thread (one that handles the network traffic in async way) and application thread (the one you use to access 0mq API from) communicate via a socketpair. Now imagine that I/O thread has something to say to the app thread every now and then (such as that new connection was established or that the connection was destroyed). If the user doesn't call any 0mq functions for an extended period of time the application thread has no chance to read its mailbox. Thus the mailbox (the socketpair) will finally fill up cause this assertion. Martin _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
