Re: [zeromq-dev] [PATCH] IPv6 changes to 4.0
On 30 August 2011 13:06, Martin Sustrik wrote: > On 08/29/2011 04:55 AM, Steven McCoy wrote: > > I'm ending up with only two realistic choices that follow the criteria >> of the users intent. >> >> 1, Do not support adapter names at all for IPv6, i.e. only support with >> ipv4only(1). >> >> 2, Manually iterate all IPv6 interfaces on the adapter and forward onto >> bind/connect. >> >> The operating systems are really pushing for #1 but I think that is a >> very weak position to take. I think we can only proceed with #2. >> > > We can start with the weak position and think about how to solve the hard > problem later on. It would still be better than the current solution the > interface name resolution does not work well in some circumstances. > > What do you think? > > That's fine, although the alternative of directing users to `/etc/networks` is also broken and no public API exists on Win32. Also, consider I re-implemented the getnetbyname API for Win32 and IPv6 specifically as a way forward for this administrative technique with OpenPGM. -- Steve-o ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] [PATCH] IPv6 changes to 4.0
On 08/29/2011 04:55 AM, Steven McCoy wrote: > I'm ending up with only two realistic choices that follow the criteria > of the users intent. > > 1, Do not support adapter names at all for IPv6, i.e. only support with > ipv4only(1). > > 2, Manually iterate all IPv6 interfaces on the adapter and forward onto > bind/connect. > > The operating systems are really pushing for #1 but I think that is a > very weak position to take. I think we can only proceed with #2. We can start with the weak position and think about how to solve the hard problem later on. It would still be better than the current solution the interface name resolution does not work well in some circumstances. What do you think? Martin ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On 08/29/2011 07:29 PM, Pieter Hintjens wrote: >> I can't recall who does this, but one of the major projects uses an >> even-odd scheme to manage stable vs development lineages. E.g. the >> even releases have are more conservative and odd more relaxed. > > We used to do that, no-one understood it, and we stopped doing it. And > it didn't match how we work anyhow, which is to create branches that > reach maturity each in their own little curve. Linux kernel did it that way, but they've abandoned the system as well. Martin ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] [ANNOUNCE] ZeroMQ/2.1.9 stable is now available
Thanks Min! On Mon, Aug 29, 2011 at 5:36 PM, MinRK wrote: > PyZMQ eggs, MSI installers have been updated to 2.1.9. > homebrew package manager also updated to 2.1.9. > -MinRK > > On Mon, Aug 29, 2011 at 14:37, Pieter Hintjens wrote: >> >> Oh, thanks for catching that. I'd missed part of the upload process. >> Jetlag... :-) >> >> Should be better now. >> >> -Pieter >> >> On Mon, Aug 29, 2011 at 11:31 PM, MinRK wrote: >> > Excellent, I'll cut the pyzmq installers tonight. >> > I do notice that the links on the website are broken, as there is no >> > 2.1.9 >> > listed at http://download.zeromq.org. Have they not been uploaded yet? >> > -MinRK >> > >> > On Mon, Aug 29, 2011 at 13:52, Pieter Hintjens wrote: >> >> >> >> Hi all, >> >> >> >> There's a new stable release 2.1.9 now available for download from >> >> http://www.zeromq.org/intro:get-the-software. >> >> >> >> Thanks to everyone who tested the 2-1 master. >> >> >> >> - >> >> Pieter Hintjens >> >> iMatix >> >> >> >> >> >> 0MQ version 2.1.9 (Stable), released on 2011/08/29 >> >> == >> >> >> >> Bug fixes >> >> - >> >> >> >> * Fixed issue 240, assertion failure in pgm_socket.cpp:437. >> >> >> >> * Fixed issue 238, assertion failure in zmq.cpp:655, when zmq_poll is >> >> used on an empty set, on Windows. >> >> >> >> * Fixed issue 239, assertion failure in zmq.cpp:223, when ZMQ_SWAP was >> >> used with explicit identities and multiple SUB sockets. >> >> >> >> * Fixed issue 236, zmq_send() and zmq_recv() did not always return >> >> error conditions such as EFSM properly. This bug was introduced in >> >> version 2.1.8 by the backport of changes for issue 231. >> >> >> >> Building >> >> >> >> >> >> * 0MQ support for Android added (Bill Roberts, Mikko Koppanen). >> >> ___ >> >> 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 >> > >> > >> ___ >> 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 > > -- Brian E. Granger Cal Poly State University, San Luis Obispo bgran...@calpoly.edu and elliso...@gmail.com ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] PUB-SUB works, server restarts, PUB-SUB fails for existing workers.
>> 2. if the server starts the worker *after* setting up 0MQ, then I get >> the error message: "Address already in use" when I kill and try to >> restart the server. > > So in this case do you have two instances of the server running at the > same time? No. I start only one instance of the server (and I checked with htop). With tcp transport, I get the 'address already in use' error message. With ipc transport, I get no reconnection. What surprises me though is that I can reduce the problem to one of order of execution: - spawn worker first, setup 0MQ second: reconnection works. - setup 0MQ first, spawn worker second: reconnection fails. and I have no good explanation for this behaviour: it should work either way, and it doesn't. ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] Cross -Compiling with gcc-3.3.1
Hi Mikko, Your suggestions worked perfectly! Can't thank you enough :) All the best, Alex On Mon, Aug 29, 2011 at 5:07 PM, Mikko Koppanen wrote: > On Tue, Aug 30, 2011 at 12:48 AM, Alex Ramirez > wrote: > > The link errors of interest I'm seeing in this example are: > > undefined reference to `std::char_traits::copy(unsigned > > char*, unsigned char const*, unsigned)' > > undefined reference to `epoll_create' > > undefined reference to `epoll_ctl' > > undefined reference to `epoll_wait' > > All these calls appear to link to libstdc++.so.6, and gcc-3.3.1 is only > > compatible with libstdc++.so.5. > > Any support is greatly appreciated! > > Hi, > > the epoll errors are caused because there is no epoll available on the > target platform. If you add -DZMQ_FORCE_POLL to CPPFLAGS it should > take care of those. I think the second error (I assume) is because too > old toolchain and ZeroMQ blob.hpp, which has the following: > > typedef std::basic_string blob_t; > > You might be able to fix this by similar fashion to: > > http://www.google.com/codesearch#NpsCNDAcr4w/MorphKad/id3lib/include/id3/id3lib_strings.h > (haven't got this old toolchain to test so just guessing here). > > -- > Mikko Koppanen > ___ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > -- “Yesterday is history. Tomorrow is a mystery. Today is a gift. That's why it is called the present.” ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] [ANNOUNCE] ZeroMQ/2.1.9 stable is now available
PyZMQ eggs, MSI installers have been updated to 2.1.9. homebrew package manager also updated to 2.1.9. -MinRK On Mon, Aug 29, 2011 at 14:37, Pieter Hintjens wrote: > Oh, thanks for catching that. I'd missed part of the upload process. > Jetlag... :-) > > Should be better now. > > -Pieter > > On Mon, Aug 29, 2011 at 11:31 PM, MinRK wrote: > > Excellent, I'll cut the pyzmq installers tonight. > > I do notice that the links on the website are broken, as there is no > 2.1.9 > > listed at http://download.zeromq.org. Have they not been uploaded yet? > > -MinRK > > > > On Mon, Aug 29, 2011 at 13:52, Pieter Hintjens wrote: > >> > >> Hi all, > >> > >> There's a new stable release 2.1.9 now available for download from > >> http://www.zeromq.org/intro:get-the-software. > >> > >> Thanks to everyone who tested the 2-1 master. > >> > >> - > >> Pieter Hintjens > >> iMatix > >> > >> > >> 0MQ version 2.1.9 (Stable), released on 2011/08/29 > >> == > >> > >> Bug fixes > >> - > >> > >> * Fixed issue 240, assertion failure in pgm_socket.cpp:437. > >> > >> * Fixed issue 238, assertion failure in zmq.cpp:655, when zmq_poll is > >> used on an empty set, on Windows. > >> > >> * Fixed issue 239, assertion failure in zmq.cpp:223, when ZMQ_SWAP was > >> used with explicit identities and multiple SUB sockets. > >> > >> * Fixed issue 236, zmq_send() and zmq_recv() did not always return > >> error conditions such as EFSM properly. This bug was introduced in > >> version 2.1.8 by the backport of changes for issue 231. > >> > >> Building > >> > >> > >> * 0MQ support for Android added (Bill Roberts, Mikko Koppanen). > >> ___ > >> 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 > > > > > ___ > 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
Re: [zeromq-dev] Cross -Compiling with gcc-3.3.1
On Tue, Aug 30, 2011 at 12:48 AM, Alex Ramirez wrote: > The link errors of interest I'm seeing in this example are: > undefined reference to `std::char_traits::copy(unsigned > char*, unsigned char const*, unsigned)' > undefined reference to `epoll_create' > undefined reference to `epoll_ctl' > undefined reference to `epoll_wait' > All these calls appear to link to libstdc++.so.6, and gcc-3.3.1 is only > compatible with libstdc++.so.5. > Any support is greatly appreciated! Hi, the epoll errors are caused because there is no epoll available on the target platform. If you add -DZMQ_FORCE_POLL to CPPFLAGS it should take care of those. I think the second error (I assume) is because too old toolchain and ZeroMQ blob.hpp, which has the following: typedef std::basic_string blob_t; You might be able to fix this by similar fashion to: http://www.google.com/codesearch#NpsCNDAcr4w/MorphKad/id3lib/include/id3/id3lib_strings.h (haven't got this old toolchain to test so just guessing here). -- Mikko Koppanen ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] Cross -Compiling with gcc-3.3.1
Hi Mikko, Am able to get the zeromq src to compile and link such that the libzmq.a and libzmq.la files are created in the hidden .lib directory. Start seeing link failures when I try to link to to the existing libzmq.la / libzmq.a files. I've attached the console output from the failures I'm seeing when I try to compile and link the performance package. The link errors of interest I'm seeing in this example are: undefined reference to `std::char_traits::copy(unsigned char*, unsigned char const*, unsigned)' undefined reference to `epoll_create' undefined reference to `epoll_ctl' undefined reference to `epoll_wait' All these calls appear to link to libstdc++.so.6, and gcc-3.3.1 is only compatible with libstdc++.so.5. Any support is greatly appreciated! Thanks, Alex On Mon, Aug 29, 2011 at 3:53 PM, Mikko Koppanen wrote: > On Mon, Aug 29, 2011 at 9:02 PM, Alex Ramirez > wrote: > > Hi, > > > > Have been attempting to cross compile libzmq.a for a PowerPC-405 > > processor which uses the following tool set versions: > > > > gcc 3.3.1 > > glibc 2.3.2 > > > > As expected, have received multiple linking errors relating to > > features not available with libstdc++.so.5 (gcc 3.3.1). The > > PopwerPC-405 is prepackaged with a custom linux installation that is > > provided by a third party vendor. I've contacted them about support > > for upgrading to newer versions of gcc and glibc, tough it's likely > > this will not be an option. > > > > Has any had any experience/success cross compiling zeromq libraries > > with these older toolsets? > > > > Hi Alex, > > which features specifically are not available? > > -- > Mikko Koppanen > ___ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > -- “Yesterday is history. Tomorrow is a mystery. Today is a gift. That's why it is called the present.” /home/omni/omni-linux-src/build-tools/gdb/build_gdb/bfd/libtool --tag=CXX --mode=link /home/omni/omni-linux-sdk/tools/bin/powerpc-405-linux-gnu-g++ -L/home/omni/omni-linux-sdk/tools/powerpc-405-linux-gnu/lib -I/home/omni/Desktop/zeromqppc/luuid/include -I/home/omni/omni-linux-sdk/tools/include -I/home/omni/omni-linux-sdk/tools/powerpc-405-linux-gnu/sys-include -L/home/omni/Desktop/zeromqppc/luuid/lib -o local_lat local_lat.o ../src/libzmq.la -luuid -lrt -lpthread -lstdc++ libtool: ignoring unknown tag CXX libtool: link: warning: library `/home/omni/omni-linux-sdk/tools/powerpc-405-linux-gnu/lib/libstdc++.la' was moved. libtool: link: warning: library `/home/omni/omni-linux-sdk/tools/powerpc-405-linux-gnu/lib/libstdc++.la' was moved. /home/omni/omni-linux-sdk/tools/bin/powerpc-405-linux-gnu-g++ -I/home/omni/Desktop/zeromqppc/luuid/include -I/home/omni/omni-linux-sdk/tools/include -I/home/omni/omni-linux-sdk/tools/powerpc-405-linux-gnu/sys-include -o local_lat local_lat.o -L/home/omni/omni-linux-sdk/tools/powerpc-405-linux-gnu/lib -L/home/omni/Desktop/zeromqppc/luuid/lib ../src/.libs/libzmq.a -L/home/omni/omni-linux-src/build-tools/crosstool-0.25/build/powerpc-405-linux-gnu/gcc-3.3.1-glibc-2.3.2/build-gcc/powerpc-405-linux-gnu/libstdc++-v3/src -L/home/omni/omni-linux-src/build-tools/crosstool-0.25/build/powerpc-405-linux-gnu/gcc-3.3.1-glibc-2.3.2/build-gcc/powerpc-405-linux-gnu/libstdc++-v3/src/.libs -lm -lm -lm -L/home/omni/omni-linux-src/build-tools/crosstool-0.25/build/powerpc-405-linux-gnu/gcc-3.3.1-glibc-2.3.2/build-gcc/gcc -L/home/omni/omni-linux-src/build-tools/crosstool-0.25/result/powerpc-405-linux-gnu/gcc-3.3.1-glibc-2.3.2/powerpc-405-linux-gnu/bin -L/home/omni/omni-linux-src/build-tools/crosstool-0.25/result/powerpc-405-linux-gnu/gcc-3.3.1-glibc-2.3.2/powerpc-405-linux-gnu/lib -L/home/omni/omni-linux-src/build-tools/crosstool-0.25/result/powerpc-405-linux-gnu/gcc-3.3.1-glibc-2.3.2/lib/gcc-lib/powerpc-405-linux-gnu/3.3.1 -L/home/omni/omni-linux-src/build-tools/crosstool-0.25/result/powerpc-405-linux-gnu/gcc-3.3.1-glibc-2.3.2/lib/gcc-lib/powerpc-405-linux-gnu/3.3.1/../../../../powerpc-405-linux-gnu/lib -lgcc_s -lc -lgcc_s -lm -lgcc_s -lc -lgcc_s -luuid -lrt -lpthread /home/omni/omni-linux-sdk/tools/powerpc-405-linux-gnu/lib/libstdc++.so -lm -lm -lm -lgcc_s -lc -lgcc_s -lm -lgcc_s -lc -lgcc_s -Wl,--rpath -Wl,/home/omni/omni-linux-sdk/tools/powerpc-405-linux-gnu/lib -Wl,--rpath -Wl,/home/omni/omni-linux-sdk/tools/powerpc-405-linux-gnu/lib ../src/.libs/libzmq.a(libzmq_la-ctx.o)(.gnu.linkonce.t._ZNSbIhSt11char_traitsIhESaIhEE4_Rep8_M_cloneERKS1_j+0xfc): In function `std::basic_string, std::allocator >::_Rep::_M_clone(std::allocator const&, unsigned)': : undefined reference to `std::char_traits::copy(unsigned char*, unsigned char const*, unsigned)' ../src/.libs/libzmq.a(libzmq_la-object.o)(.gnu.linkonce.t._ZNSbIhSt11char_traitsIhESaIhEE13_S_copy_charsEPhPKhS5_+0x38): In function `std::basic_string, std::allocator >::_S_copy_chars(unsigned char*, unsigned char const*, un
Re: [zeromq-dev] Cross -Compiling with gcc-3.3.1
On Mon, Aug 29, 2011 at 9:02 PM, Alex Ramirez wrote: > Hi, > > Have been attempting to cross compile libzmq.a for a PowerPC-405 > processor which uses the following tool set versions: > > gcc 3.3.1 > glibc 2.3.2 > > As expected, have received multiple linking errors relating to > features not available with libstdc++.so.5 (gcc 3.3.1). The > PopwerPC-405 is prepackaged with a custom linux installation that is > provided by a third party vendor. I've contacted them about support > for upgrading to newer versions of gcc and glibc, tough it's likely > this will not be an option. > > Has any had any experience/success cross compiling zeromq libraries > with these older toolsets? > Hi Alex, which features specifically are not available? -- Mikko Koppanen ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] [ANNOUNCE] ZeroMQ/2.1.9 stable is now available
Oh, thanks for catching that. I'd missed part of the upload process. Jetlag... :-) Should be better now. -Pieter On Mon, Aug 29, 2011 at 11:31 PM, MinRK wrote: > Excellent, I'll cut the pyzmq installers tonight. > I do notice that the links on the website are broken, as there is no 2.1.9 > listed at http://download.zeromq.org. Have they not been uploaded yet? > -MinRK > > On Mon, Aug 29, 2011 at 13:52, Pieter Hintjens wrote: >> >> Hi all, >> >> There's a new stable release 2.1.9 now available for download from >> http://www.zeromq.org/intro:get-the-software. >> >> Thanks to everyone who tested the 2-1 master. >> >> - >> Pieter Hintjens >> iMatix >> >> >> 0MQ version 2.1.9 (Stable), released on 2011/08/29 >> == >> >> Bug fixes >> - >> >> * Fixed issue 240, assertion failure in pgm_socket.cpp:437. >> >> * Fixed issue 238, assertion failure in zmq.cpp:655, when zmq_poll is >> used on an empty set, on Windows. >> >> * Fixed issue 239, assertion failure in zmq.cpp:223, when ZMQ_SWAP was >> used with explicit identities and multiple SUB sockets. >> >> * Fixed issue 236, zmq_send() and zmq_recv() did not always return >> error conditions such as EFSM properly. This bug was introduced in >> version 2.1.8 by the backport of changes for issue 231. >> >> Building >> >> >> * 0MQ support for Android added (Bill Roberts, Mikko Koppanen). >> ___ >> 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 > > ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] Issues with Java bindings on Mac OS X 10.6.8
You need to subscribe to the data. You don't receive any messages until a
filter pattern is applied.
listener.subscribe("".getBytes());
Be aware that the Pub/Sub sockets are non durable and that they often lose the
first set of messages send due to the time to connect and subscribe. You will
want to add a sleep to the publisher after connect.
Joshua
On Aug 29, 2011, at 5:03 PM, Tero Paananen wrote:
> I'm having issues with getting pub / sub working on a Mac OS X 10.6.8
> using the Java bindings.
>
> Compiled and installed zeromq and jzmq using these instructions:
>
> http://antoniogarrote.wordpress.com/2010/09/08/zeromq-and-clojure-a-brief-introduction/
>
> (obviously with the latest versions of everything).
>
> Simple pub / sub example is not working:
>
>
> import org.zeromq.ZMQ;
> import org.zeromq.ZMQ.Context;
> import org.zeromq.ZMQ.Socket;
>
> public class subs {
> public static void main(String[] args) throws InterruptedException {
>
> Context context = ZMQ.context(1);
>
> Socket listener = context.socket(ZMQ.SUB);
> listener.bind("tcp://127.0.0.1:5560");
>
> byte[] message = listener.recv(0);
> String msg = new String(message);
> System.out.println(msg);
>
> listener.close();
> context.term();
> }
> }
>
>
>
> import org.zeromq.ZMQ;
> import org.zeromq.ZMQ.Context;
> import org.zeromq.ZMQ.Socket;
>
> public class publ {
> public static void main(String[] args) throws InterruptedException {
> Context context = ZMQ.context(1);
> Socket messenger = context.socket(ZMQ.PUB);
> messenger.connect("tcp://127.0.0.1:5560");
>
> messenger.send(args[0].getBytes(), 0);
>
> messenger.close();
> context.term();
> }
> }
>
> I start the subs, and run the publ. Publ executes, subs doesn't report
> receiving the message.
>
> I change the socket type on subs to ZMQ.PULL and everything works marvelously.
>
> Any ideas?
>
> I'm currently installing the same stack on a Ubuntu to see if it works
> on that platform.
>
> -TPP
> ___
> 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
Re: [zeromq-dev] [ANNOUNCE] ZeroMQ/2.1.9 stable is now available
Excellent, I'll cut the pyzmq installers tonight. I do notice that the links on the website are broken, as there is no 2.1.9 listed at http://download.zeromq.org. Have they not been uploaded yet? -MinRK On Mon, Aug 29, 2011 at 13:52, Pieter Hintjens wrote: > Hi all, > > There's a new stable release 2.1.9 now available for download from > http://www.zeromq.org/intro:get-the-software. > > Thanks to everyone who tested the 2-1 master. > > - > Pieter Hintjens > iMatix > > > 0MQ version 2.1.9 (Stable), released on 2011/08/29 > == > > Bug fixes > - > > * Fixed issue 240, assertion failure in pgm_socket.cpp:437. > > * Fixed issue 238, assertion failure in zmq.cpp:655, when zmq_poll is > used on an empty set, on Windows. > > * Fixed issue 239, assertion failure in zmq.cpp:223, when ZMQ_SWAP was > used with explicit identities and multiple SUB sockets. > > * Fixed issue 236, zmq_send() and zmq_recv() did not always return > error conditions such as EFSM properly. This bug was introduced in > version 2.1.8 by the backport of changes for issue 231. > > Building > > > * 0MQ support for Android added (Bill Roberts, Mikko Koppanen). > ___ > 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
[zeromq-dev] Issues with Java bindings on Mac OS X 10.6.8
I'm having issues with getting pub / sub working on a Mac OS X 10.6.8
using the Java bindings.
Compiled and installed zeromq and jzmq using these instructions:
http://antoniogarrote.wordpress.com/2010/09/08/zeromq-and-clojure-a-brief-introduction/
(obviously with the latest versions of everything).
Simple pub / sub example is not working:
import org.zeromq.ZMQ;
import org.zeromq.ZMQ.Context;
import org.zeromq.ZMQ.Socket;
public class subs {
public static void main(String[] args) throws InterruptedException {
Context context = ZMQ.context(1);
Socket listener = context.socket(ZMQ.SUB);
listener.bind("tcp://127.0.0.1:5560");
byte[] message = listener.recv(0);
String msg = new String(message);
System.out.println(msg);
listener.close();
context.term();
}
}
import org.zeromq.ZMQ;
import org.zeromq.ZMQ.Context;
import org.zeromq.ZMQ.Socket;
public class publ {
public static void main(String[] args) throws InterruptedException {
Context context = ZMQ.context(1);
Socket messenger = context.socket(ZMQ.PUB);
messenger.connect("tcp://127.0.0.1:5560");
messenger.send(args[0].getBytes(), 0);
messenger.close();
context.term();
}
}
I start the subs, and run the publ. Publ executes, subs doesn't report
receiving the message.
I change the socket type on subs to ZMQ.PULL and everything works marvelously.
Any ideas?
I'm currently installing the same stack on a Ubuntu to see if it works
on that platform.
-TPP
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
[zeromq-dev] [ANNOUNCE] ZeroMQ/2.1.9 stable is now available
Hi all, There's a new stable release 2.1.9 now available for download from http://www.zeromq.org/intro:get-the-software. Thanks to everyone who tested the 2-1 master. - Pieter Hintjens iMatix 0MQ version 2.1.9 (Stable), released on 2011/08/29 == Bug fixes - * Fixed issue 240, assertion failure in pgm_socket.cpp:437. * Fixed issue 238, assertion failure in zmq.cpp:655, when zmq_poll is used on an empty set, on Windows. * Fixed issue 239, assertion failure in zmq.cpp:223, when ZMQ_SWAP was used with explicit identities and multiple SUB sockets. * Fixed issue 236, zmq_send() and zmq_recv() did not always return error conditions such as EFSM properly. This bug was introduced in version 2.1.8 by the backport of changes for issue 231. Building * 0MQ support for Android added (Bill Roberts, Mikko Koppanen). ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
[zeromq-dev] Cross -Compiling with gcc-3.3.1
Hi, Have been attempting to cross compile libzmq.a for a PowerPC-405 processor which uses the following tool set versions: gcc 3.3.1 glibc 2.3.2 As expected, have received multiple linking errors relating to features not available with libstdc++.so.5 (gcc 3.3.1). The PopwerPC-405 is prepackaged with a custom linux installation that is provided by a third party vendor. I've contacted them about support for upgrading to newer versions of gcc and glibc, tough it's likely this will not be an option. Has any had any experience/success cross compiling zeromq libraries with these older toolsets? Any support is greatly appreciated! Thanks, Alex ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] PUB-SUB works, server restarts, PUB-SUB fails for existing workers.
On Mon, Aug 29, 2011 at 9:03 PM, alotsof wrote: > 2. if the server starts the worker *after* setting up 0MQ, then I get > the error message: "Address already in use" when I kill and try to > restart the server. So in this case do you have two instances of the server running at the same time? -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] PUB-SUB works, server restarts, PUB-SUB fails for existing workers.
at this point, the subject line should be something like
"0MQ reconnect problem"
>> Then server and workers can't talk to each other anymore. Workers
>> spawned after the server's restart can communicate with the server...
>
> Does the same happen when you use TCP?
With TCP:
1. if the server starts the worker before setting up 0MQ, no problem. I
can kill and restart the server, and 0MQ reconnects every time.
2. if the server starts the worker *after* setting up 0MQ, then I get
the error message: "Address already in use" when I kill and try to
restart the server.
> You could be hitting a file permissions issue, if you're running the
> server and workers under different user ids.
From the command-line, same user with the code below.
#--
Usage:
./server5.py -before # starts worker before 0MQ
./server5.py -after # starts worker after 0MQ
Then kill the server, and restart it alone with:
./server5.py # starts server alone
and see when 0MQ reconnects, and when not.
#--
#!/usr/bin/python
# server5.py
import time
import os
import sys
import subprocess
import zmq
if '-before' in sys.argv:
args =('python','./worker5.py')
p = subprocess.Popen(args)
pid = "server " + str(os.getpid())
context = zmq.Context()
WorkersToServer = context.socket(zmq.PULL)
WorkersToServer.bind("tcp://*:12345")
poller = zmq.Poller()
poller.register(WorkersToServer, zmq.POLLIN)
if '-after' in sys.argv:
args =('python','./worker5.py')
p = subprocess.Popen(args)
while True:
socks = dict(poller.poll(5000))
if WorkersToServer in socks and socks[WorkersToServer] == zmq.POLLIN:
message = WorkersToServer.recv()
print pid, "=", message
else:
print pid, "timeout"
#--
#!/usr/bin/python
# worker5.py
import time
import os
import zmq
pid = "worker " + str(os.getpid())
context = zmq.Context()
WorkersToServer = context.socket(zmq.PUSH)
WorkersToServer.connect("tcp://localhost:12345")
while True:
WorkersToServer.send(time.ctime() + " from " + pid)
print "\t", pid
time.sleep(1)
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] XREQ socket connect to multi endpoints
On Mon, Aug 29, 2011 at 5:40 PM, Garrett Smith wrote: > The REP socket expects an empty message part that separates the socket > IDs from the payload, which is handled for you by REQ, but not by > XREQ. Nice catch. I'd forgotten that one. -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 5:21 PM, Garrett Smith wrote: > I'm of the opinion that "release candidates" are a vestige of time > when releases were more expensive (e.g. burnt to CDs) and that the > intent was to get everything just right. That's just not the way > things work these days. Indeed. > I can't recall who does this, but one of the major projects uses an > even-odd scheme to manage stable vs development lineages. E.g. the > even releases have are more conservative and odd more relaxed. We used to do that, no-one understood it, and we stopped doing it. And it didn't match how we work anyhow, which is to create branches that reach maturity each in their own little curve. > In any case, I personally don't care for the "rc" tag and am fine with > rolling releases, some of which are more stable than others -- in the > end, it's the list of known issues and release notes that matter. Ack. -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 5:17 PM, Dirkjan Ochtman wrote: > It's just that I have the feeling that sometimes releases get delayed > because people are busy doing other things, or don't really have > ZeroMQ releases on their mind. Sometimes that happens but it's rare. Making a release is really quite simple. So releases are driven by the amount and frequency of change, and the demand from users, which depends on how broken the previous release is/was. > I worked on one project where there are > monthly patch-level releases, and I really like the predictability of > that (of course it depends on the overhead of releases). Releases are not much work. It's really a matter of demand. > Fair enough. I guess we should just write more automated tests. It would be great to have someone do this: collect regression tests that can be run on each release. It's an insane amount of work though. -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] XREQ socket connect to multi endpoints
ok thanks
2011/8/29 Garrett Smith
> The REP socket expects an empty message part that separates the socket
> IDs from the payload, which is handled for you by REQ, but not by
> XREQ.
>
> Like this:
>
> client.send('', zmq.SNDMORE)
> client.send('hello')
>
> On Mon, Aug 29, 2011 at 10:24 AM, notedit wrote:
> > hello , anyone can help me with my question?
> > i just can not figure it out.
> > many thanks
> >
> > 2011/8/29 notedit
> >>
> >> i change the '*' to '127.0.0.1',but the client still can not work,
> >> the client just stucks there.
> >>
> >> 2011/8/29 Pieter Hintjens
> >>>
> >>> The code is OK, but you're connecting to an address '*', which is not
> >>> valid. Specify the real IP address, or domain name.
> >>>
> >>> -Pieter
> >>>
> >>> On Mon, Aug 29, 2011 at 7:25 AM, notedit wrote:
> >>> >
> >>> > hi, i just have read the zero guide, and i know DEALER/ROUTER
> >>> > ==XREQ/XREP,
> >>> > i alse read that a socket can connect to multi endpoints,
> >>> > so i do a test, i try to use a xreq socket connect to multi req
> >>> > socket,
> >>> > but it seems that it doesn't work.
> >>> > this is my code
> >>> > client : http://pastebin.com/jhcSdLgr
> >>> > worker1: http://pastebin.com/iFtTkq5j
> >>> > worker2: http://pastebin.com/jDQffB32
> >>> > anyone can explain that to me? many thanks
> >>> > --
> >>> >
> >>> > Best Wishes..
> >>> >
> >>> >
> >>> > ___
> >>> > 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
> >>
> >>
> >>
> >> --
> >>
> >> Best Wishes..
> >>
> >
> >
> >
> > --
> >
> > Best Wishes..
> >
> >
> > ___
> > 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
>
--
*
Best Wishes..
*
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] XREQ socket connect to multi endpoints
The REP socket expects an empty message part that separates the socket
IDs from the payload, which is handled for you by REQ, but not by
XREQ.
Like this:
client.send('', zmq.SNDMORE)
client.send('hello')
On Mon, Aug 29, 2011 at 10:24 AM, notedit wrote:
> hello , anyone can help me with my question?
> i just can not figure it out.
> many thanks
>
> 2011/8/29 notedit
>>
>> i change the '*' to '127.0.0.1',but the client still can not work,
>> the client just stucks there.
>>
>> 2011/8/29 Pieter Hintjens
>>>
>>> The code is OK, but you're connecting to an address '*', which is not
>>> valid. Specify the real IP address, or domain name.
>>>
>>> -Pieter
>>>
>>> On Mon, Aug 29, 2011 at 7:25 AM, notedit wrote:
>>> >
>>> > hi, i just have read the zero guide, and i know DEALER/ROUTER
>>> > ==XREQ/XREP,
>>> > i alse read that a socket can connect to multi endpoints,
>>> > so i do a test, i try to use a xreq socket connect to multi req
>>> > socket,
>>> > but it seems that it doesn't work.
>>> > this is my code
>>> > client : http://pastebin.com/jhcSdLgr
>>> > worker1: http://pastebin.com/iFtTkq5j
>>> > worker2: http://pastebin.com/jDQffB32
>>> > anyone can explain that to me? many thanks
>>> > --
>>> >
>>> > Best Wishes..
>>> >
>>> >
>>> > ___
>>> > 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
>>
>>
>>
>> --
>>
>> Best Wishes..
>>
>
>
>
> --
>
> Best Wishes..
>
>
> ___
> 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
Re: [zeromq-dev] XREQ socket connect to multi endpoints
hello , anyone can help me with my question? i just can not figure it out. many thanks 2011/8/29 notedit > i change the '*' to '127.0.0.1',but the client still can not work, > > the client just stucks there. > > > 2011/8/29 Pieter Hintjens > >> The code is OK, but you're connecting to an address '*', which is not >> valid. Specify the real IP address, or domain name. >> >> -Pieter >> >> On Mon, Aug 29, 2011 at 7:25 AM, notedit wrote: >> > >> > hi, i just have read the zero guide, and i know DEALER/ROUTER >> ==XREQ/XREP, >> > i alse read that a socket can connect to multi endpoints, >> > so i do a test, i try to use a xreq socket connect to multi req socket, >> > but it seems that it doesn't work. >> > this is my code >> > client : http://pastebin.com/jhcSdLgr >> > worker1: http://pastebin.com/iFtTkq5j >> > worker2: http://pastebin.com/jDQffB32 >> > anyone can explain that to me? many thanks >> > -- >> > >> > Best Wishes.. >> > >> > >> > ___ >> > 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 >> > > > > -- > * > > Best Wishes.. > > * > > -- * Best Wishes.. * ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 10:13 AM, Pieter Hintjens wrote: > > I'm not sure schedules are useful since we are always on a curve (more > releases when a branch is immature, fewer as it matures). But in > general we release when there've been a reasonable number of fixes and > changes. > > We've tried limited releases before, e.g. tagging on the repository, > but in fact close to no-one tests them. Experience tells us that > people only test official releases and for the most part, stable > releases only. You can see, e.g. how few issues we have on 3.0.0. I'm of the opinion that "release candidates" are a vestige of time when releases were more expensive (e.g. burnt to CDs) and that the intent was to get everything just right. That's just not the way things work these days. I can't recall who does this, but one of the major projects uses an even-odd scheme to manage stable vs development lineages. E.g. the even releases have are more conservative and odd more relaxed. In any case, I personally don't care for the "rc" tag and am fine with rolling releases, some of which are more stable than others -- in the end, it's the list of known issues and release notes that matter. Garrett ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 17:13, Pieter Hintjens wrote: > I'm not sure schedules are useful since we are always on a curve (more > releases when a branch is immature, fewer as it matures). But in > general we release when there've been a reasonable number of fixes and > changes. It's just that I have the feeling that sometimes releases get delayed because people are busy doing other things, or don't really have ZeroMQ releases on their mind. I worked on one project where there are monthly patch-level releases, and I really like the predictability of that (of course it depends on the overhead of releases). > We've tried limited releases before, e.g. tagging on the repository, > but in fact close to no-one tests them. Experience tells us that > people only test official releases and for the most part, stable > releases only. You can see, e.g. how few issues we have on 3.0.0. Fair enough. I guess we should just write more automated tests. Cheers, Dirkjan ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 2:11 PM, Dirkjan Ochtman wrote: > Further thought: it could just as well not be called -rc1, but just > publishing a candidate tarball on the mailing list only. E.g. in > Apache projects so-called "release artefacts" are always published to > a developer mailing list, tested (with a required number of sign-offs > from contributors), and only then published. If you really want to > take QA seriously, that might not be such a bad idea. (I'd also > suggest something of a release schedule, even if it's just a schedule > where the stable branch release manager considers if there are enough > fixes on the branch to justify a release.) I'm not sure schedules are useful since we are always on a curve (more releases when a branch is immature, fewer as it matures). But in general we release when there've been a reasonable number of fixes and changes. We've tried limited releases before, e.g. tagging on the repository, but in fact close to no-one tests them. Experience tells us that people only test official releases and for the most part, stable releases only. You can see, e.g. how few issues we have on 3.0.0. -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 2:08 PM, Dirkjan Ochtman wrote: > That seems fine with me. Perhaps it would be useful to publish actual > RC's for a few days before an actual release? E.g. something called > 2.1.9-rc1, leave it out there for two or three days, then publish > 2.1.9. Perhaps that would draw just the right amount of testing out of > the woodwork that you won't have to unpublish actual releases. Perhaps. I don't like two releases with the same version number; the patch level (e.g. 9) indicates change. So even one bug fix means a new patch level. -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] What's wrong with my client XREQ
Please read the documentation for router sockets (man zmq_socket) and the
Guide ch2 and ch3.
- Pieter
On Aug 29, 2011 2:16 PM, "ZOUNG KALACK Jimy (EXT)" <
jimy.zoung-kalack-...@sgcib.com> wrote:
> I've got a client, a broker and a server.
> The server sends 1000 times the same message. The message is Hello
> The client should read all the messages as they arrive.
>
> Nothing is coming to the client and I don't know why?
> Maybe I'm doing something wrong in the client.
>
> static void ClientTask()
> {
> using (Context ctx = new Context(1))
> {
> using (Socket client = ctx.Socket(SocketType.XREQ))
> {
> client.Connect("tcp://localhost:5570");
> Console.WriteLine("Client starts");
>
> PollItem[] items = new PollItem[1];
> items[0] = client.CreatePollItem(IOMultiPlex.POLLIN);
> items[0].PollInHandler += (skt, revents) =>
> {
> ZMessage zmsg = new ZMessage(skt);
> Console.WriteLine("received {0} ", zmsg.BodyToString());
>
>
> while (true)
> {
> ctx.Poll(items, 1000);
> }
> }
> }
> }
>
> static void Main(string[] args)
> {
> Thread client = new Thread(ClientTask);
> client.Start();
>
> }
>
> ---
> sender
> ---
> static void Main(string[] args)
> {
> using (Context ctx = new Context(1))
> {
> using (Socket worker = ctx.Socket(SocketType.XREP))
> {
> worker.Connect("tcp://localhost:5571");
> for(int i=0;i<1000;i++)
> {
>
> ZMessage zmsg = new ZMessage("Hello");
> zmsg.Send(worker);
> Console.WriteLine("reply back " + zmsg.BodyToString());
>
> }
> }
> }
> }
>
>
>
> broker
> -
> namespace BrokerQueue
> {
> class Program
> {
> static void Main(string[] args)
> {
> using (Context context = new Context(1))
> {
> using (Socket frontend = context.Socket(SocketType.XREP),
> backend = context.Socket(SocketType.XREQ))
> {
> // Socket facing clients
> frontend.Bind("tcp://*:5570");
> Console.WriteLine("Broker frontend: bind to Client");
>
> // Backend socket talks to workers over inproc
> backend.Bind("tcp://*:5571");
> Console.WriteLine("bind backend");
>
> // Start built-in device
> Socket.Device.Queue(frontend, backend);
> }
> }
> }
> }
> }
> *
> This message and any attachments (the "message") are confidential,
intended solely for the addressee(s), and may contain legally privileged
information.
> Any unauthorised use or dissemination is prohibited. E-mails are
susceptible to alteration.
> Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall
be liable for the message if altered, changed or
> falsified.
>
> Ce message et toutes les pieces jointes (ci-apres le "message") sont
confidentiels et susceptibles de contenir des informations couvertes
> par le secret professionnel.
> Ce message est etabli a l'intention exclusive de ses destinataires. Toute
utilisation ou diffusion non autorisee est interdite.
> Tout message electronique est susceptible d'alteration.
> La SOCIETE GENERALE et ses filiales declinent toute responsabilite au
titre de ce message s'il a ete altere, deforme ou falsifie.
> *
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] pub/sub performance help
On Aug 29, 2011, at 8:34 AM, ZOUNG KALACK Jimy (EXT) wrote: > Remes, > > http://pastie.org/2448540 (publisher) > > http://pastie.org/2448547 (subscriber) > > Jimy > -Original Message- > From: zeromq-dev-boun...@lists.zeromq.org > [mailto:zeromq-dev-boun...@lists.zeromq.org] On Behalf Of Chuck Remes > Sent: Monday,August 29,2011 2:49 PM > To: ZeroMQ development list > Subject: Re: [zeromq-dev] pub/sub performance help > > On Aug 29, 2011, at 7:05 AM, ZOUNG KALACK Jimy (EXT) wrote: > >> Thanks Pieter I will check again. >> My technique is simple. >> Publisher and subscriber are on the same box. >> The publisher sends 10.000 messages. >> The message sent is just the timestamp in the format (/mm/dd >> HH:mm:ss.f) >> For each message the subscriber receives, the latency is calculated. >> Ln = In-On >> >> Jimy > > Please put your code up for us to see. I recommend gist.github.com or > pastie.org. Good. So, to solve your first problem (you only see a fraction of the published messages) you should add a sleep between lines 27 and 28 of your publisher. Alternately, have it wait for you to press a key or something before it starts publishing. This will give you time to start up the subscriber and let it finish its connection handshake so that no messages are dropped. Secondly, the increased latency you are seeing may be due to a few factors. 1. Publishers are *always* faster than subscribers because they have less work to do. Since you do not set a HWM, by default the socket will queue as many messages as memory will allow. So the publisher is sending as fast as it can but your subscriber is slow. 2. I don't know how fast the Date operations are in python. It's entirely possible that converting to and from a string is too slow. 3. You are saving each latency calculation in a list. Perhaps it is slow to append a lot of objects to a python list. At minimum there will be many mallocs and garbage collections going on in the background all of which will slow down operations. Here are my suggestions. 1. Eliminate the current latency calculation and the list add operation. 2. Change the publisher to send a fixed message (e.g. a 50-byte string). You want to measure latency, not string allocation time. 3. Replace the latency calc with a timer. When the subscriber receives its first message, start the timer. When it receives the "STOP" message, calculate latency by measuring the overall time and dividing by the number of messages received. cr ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] pub/sub performance help
Remes, http://pastie.org/2448540 (publisher) http://pastie.org/2448547 (subscriber) Jimy -Original Message- From: zeromq-dev-boun...@lists.zeromq.org [mailto:zeromq-dev-boun...@lists.zeromq.org] On Behalf Of Chuck Remes Sent: Monday,August 29,2011 2:49 PM To: ZeroMQ development list Subject: Re: [zeromq-dev] pub/sub performance help On Aug 29, 2011, at 7:05 AM, ZOUNG KALACK Jimy (EXT) wrote: > Thanks Pieter I will check again. > My technique is simple. > Publisher and subscriber are on the same box. > The publisher sends 10.000 messages. > The message sent is just the timestamp in the format (/mm/dd > HH:mm:ss.f) > For each message the subscriber receives, the latency is calculated. > Ln = In-On > > Jimy Please put your code up for us to see. I recommend gist.github.com or pastie.org. cr ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev * This message and any attachments (the "message") are confidential, intended solely for the addressee(s), and may contain legally privileged information. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et susceptibles de contenir des informations couvertes par le secret professionnel. Ce message est etabli a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. * ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] pub/sub performance help
On Aug 29, 2011, at 7:05 AM, ZOUNG KALACK Jimy (EXT) wrote: > Thanks Pieter I will check again. > My technique is simple. > Publisher and subscriber are on the same box. > The publisher sends 10.000 messages. > The message sent is just the timestamp in the format (/mm/dd > HH:mm:ss.f) > For each message the subscriber receives, the latency is calculated. > Ln = In-On > > Jimy Please put your code up for us to see. I recommend gist.github.com or pastie.org. cr ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
[zeromq-dev] What's wrong with my client XREQ
I've got a client, a broker and a server.
The server sends 1000 times the same message. The message is Hello
The client should read all the messages as they arrive.
Nothing is coming to the client and I don't know why?
Maybe I'm doing something wrong in the client.
static void ClientTask()
{
using (Context ctx = new Context(1))
{
using (Socket client = ctx.Socket(SocketType.XREQ))
{
client.Connect("tcp://localhost:5570");
Console.WriteLine("Client starts");
PollItem[] items = new PollItem[1];
items[0] = client.CreatePollItem(IOMultiPlex.POLLIN);
items[0].PollInHandler += (skt, revents) =>
{
ZMessage zmsg = new ZMessage(skt);
Console.WriteLine("received {0} ", zmsg.BodyToString());
while (true)
{
ctx.Poll(items, 1000);
}
}
}
}
static void Main(string[] args)
{
Thread client = new Thread(ClientTask);
client.Start();
}
---
sender
---
static void Main(string[] args)
{
using (Context ctx = new Context(1))
{
using (Socket worker = ctx.Socket(SocketType.XREP))
{
worker.Connect("tcp://localhost:5571");
for(int i=0;i<1000;i++)
{
ZMessage zmsg = new ZMessage("Hello");
zmsg.Send(worker);
Console.WriteLine("reply back " + zmsg.BodyToString());
}
}
}
}
broker
-
namespace BrokerQueue
{
class Program
{
static void Main(string[] args)
{
using (Context context = new Context(1))
{
using (Socket frontend = context.Socket(SocketType.XREP),
backend = context.Socket(SocketType.XREQ))
{
// Socket facing clients
frontend.Bind("tcp://*:5570");
Console.WriteLine("Broker frontend: bind to Client");
// Backend socket talks to workers over inproc
backend.Bind("tcp://*:5571");
Console.WriteLine("bind backend");
// Start built-in device
Socket.Device.Queue(frontend, backend);
}
}
}
}
}
*
This message and any attachments (the "message") are confidential, intended
solely for the addressee(s), and may contain legally privileged information.
Any unauthorised use or dissemination is prohibited. E-mails are susceptible to
alteration.
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be
liable for the message if altered, changed or
falsified.
Ce message et toutes les pieces jointes (ci-apres le "message") sont
confidentiels et susceptibles de contenir des informations couvertes
par le secret professionnel.
Ce message est etabli a l'intention exclusive de ses destinataires. Toute
utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration.
La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de
ce message s'il a ete altere, deforme ou falsifie.
*
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 14:08, Dirkjan Ochtman wrote: > That seems fine with me. Perhaps it would be useful to publish actual > RC's for a few days before an actual release? E.g. something called > 2.1.9-rc1, leave it out there for two or three days, then publish > 2.1.9. Perhaps that would draw just the right amount of testing out of > the woodwork that you won't have to unpublish actual releases. Further thought: it could just as well not be called -rc1, but just publishing a candidate tarball on the mailing list only. E.g. in Apache projects so-called "release artefacts" are always published to a developer mailing list, tested (with a required number of sign-offs from contributors), and only then published. If you really want to take QA seriously, that might not be such a bad idea. (I'd also suggest something of a release schedule, even if it's just a schedule where the stable branch release manager considers if there are enough fixes on the branch to justify a release.) Cheers, Dirkjan ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 13:53, Pieter Hintjens wrote: > It seems tagging the release as 'rc' annoyed several people, so next > time we'll just delete such cases and skip to the next release number. > That leaves gaps but is less surprising. That seems fine with me. Perhaps it would be useful to publish actual RC's for a few days before an actual release? E.g. something called 2.1.9-rc1, leave it out there for two or three days, then publish 2.1.9. Perhaps that would draw just the right amount of testing out of the woodwork that you won't have to unpublish actual releases. Cheers, Dirkjan ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] pub/sub performance help
Thanks Pieter I will check again. My technique is simple. Publisher and subscriber are on the same box. The publisher sends 10.000 messages. The message sent is just the timestamp in the format (/mm/dd HH:mm:ss.f) For each message the subscriber receives, the latency is calculated. Ln = In-On Jimy -Original Message- From: zeromq-dev-boun...@lists.zeromq.org [mailto:zeromq-dev-boun...@lists.zeromq.org] On Behalf Of Pieter Hintjens Sent: Monday,August 29,2011 1:19 PM To: ZeroMQ development list Subject: Re: [zeromq-dev] pub/sub performance help On Mon, Aug 29, 2011 at 1:00 PM, ZOUNG KALACK Jimy (EXT) wrote: >>What does the X axis represent, is that message size? > The X axis represents messages (not the size) the first msg to the > last msg received. IMO it's an artifact of the way you're measuring latency. Normally we measure individual messages. You're measuring batches, it seems. The actual latency per message should be constant depending on the message size. In other words you've got an error in your measurement technique. -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev * This message and any attachments (the "message") are confidential, intended solely for the addressee(s), and may contain legally privileged information. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et susceptibles de contenir des informations couvertes par le secret professionnel. Ce message est etabli a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. * ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] XREQ socket connect to multi endpoints
i change the '*' to '127.0.0.1',but the client still can not work, the client just stucks there. 2011/8/29 Pieter Hintjens > The code is OK, but you're connecting to an address '*', which is not > valid. Specify the real IP address, or domain name. > > -Pieter > > On Mon, Aug 29, 2011 at 7:25 AM, notedit wrote: > > > > hi, i just have read the zero guide, and i know DEALER/ROUTER > ==XREQ/XREP, > > i alse read that a socket can connect to multi endpoints, > > so i do a test, i try to use a xreq socket connect to multi req socket, > > but it seems that it doesn't work. > > this is my code > > client : http://pastebin.com/jhcSdLgr > > worker1: http://pastebin.com/iFtTkq5j > > worker2: http://pastebin.com/jDQffB32 > > anyone can explain that to me? many thanks > > -- > > > > Best Wishes.. > > > > > > ___ > > 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 > -- * Best Wishes.. * ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 1:27 PM, Dirkjan Ochtman wrote: > I might be alone in this, but I've found the treatment of 2.1.8-rc1 > pretty confusing. E.g. in my expectations any rc is always followed by > an actual release of the same version numbers. If you want to uniquely > version releases, that's nice too, but then it would be more sensible > (to me) to unpublish the release candidate from e.g. the downloads > page. You're not the only one to be confused. In the past we unpublished stable releases that had flaws in them. The last time we discussed this the consensus was to stick to a unique release/version number that defined major/minor compatibility, and to tag releases as alpha/beta/rc depending on their maturity. So in this case when we found an issue in 2.1.8, the choice was either to delete the release, or to tag it as 'rc'. It seems tagging the release as 'rc' annoyed several people, so next time we'll just delete such cases and skip to the next release number. That leaves gaps but is less surprising. If anyone has alternative suggestions, shoot. The requirements are: - unique version numbering that indicates major/minor compatibility, plus patch level (this rules out making 2.1.8-rc, 2.1.8-rc2, 2.1.8-stable for instance). - tagging of some kind that indicates maturity (presumably alpha, beta, and rc). - handling of exceptions, i.e. a release that turns out to be more or less mature than expected (a beta that has no issues reported on it, or a stable that has a serious issue). -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 12:27, Pieter Hintjens wrote: > The idea is to always use unique release numbers, and tag them to > indicate their maturity. I might be alone in this, but I've found the treatment of 2.1.8-rc1 pretty confusing. E.g. in my expectations any rc is always followed by an actual release of the same version numbers. If you want to uniquely version releases, that's nice too, but then it would be more sensible (to me) to unpublish the release candidate from e.g. the downloads page. Cheers, Dirkjan ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] pub/sub performance help
On Mon, Aug 29, 2011 at 1:00 PM, ZOUNG KALACK Jimy (EXT) wrote: >>What does the X axis represent, is that message size? > The X axis represents messages (not the size) the first msg to the > last msg received. IMO it's an artifact of the way you're measuring latency. Normally we measure individual messages. You're measuring batches, it seems. The actual latency per message should be constant depending on the message size. In other words you've got an error in your measurement technique. -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] pub/sub performance help
Ok fair enough if the subscriber will always lose the first 100msec. it does make sense why there are missing messages. > 2- Does the latency curve below make since to you guy >What does the X axis represent, is that message size? The X axis represents messages (not the size) the first msg to the last msg received. -Original Message- From: zeromq-dev-boun...@lists.zeromq.org [mailto:zeromq-dev-boun...@lists.zeromq.org] On Behalf Of Pieter Hintjens Sent: Monday,August 29,2011 12:31 PM To: ZeroMQ development list Subject: Re: [zeromq-dev] pub/sub performance help On Mon, Aug 29, 2011 at 11:18 AM, ZOUNG KALACK Jimy (EXT) wrote: > I've got a simple pub/sub running on the same box > The publisher sends 10 000 in a loop. The message is just a timestamps.( > creation date) > 1- Surprisingly, the subscriber is able to read only 6 000. I don't > understand why Without seeing test code, it's hard to know what you mean by "in a loop", but in general the subscriber will always lose the first 100msec of data (roughly) sent by the publisher at startup. The sequence is: - subscriber starts - publisher binds socket - subscriber launches connect to pub socket - publisher starts to send messages - subscriber connect completes - subscriber starts to receive messages > 2- Does the latency curve below make since to you guy What does the X axis represent, is that message size? -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev * This message and any attachments (the "message") are confidential, intended solely for the addressee(s), and may contain legally privileged information. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et susceptibles de contenir des informations couvertes par le secret professionnel. Ce message est etabli a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. * ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] pub/sub performance help
On Mon, Aug 29, 2011 at 11:18 AM, ZOUNG KALACK Jimy (EXT) wrote: > I’ve got a simple pub/sub running on the same box > The publisher sends 10 000 in a loop. The message is just a timestamps.( > creation date) > 1- Surprisingly, the subscriber is able to read only 6 000. I don’t > understand why Without seeing test code, it's hard to know what you mean by "in a loop", but in general the subscriber will always lose the first 100msec of data (roughly) sent by the publisher at startup. The sequence is: - subscriber starts - publisher binds socket - subscriber launches connect to pub socket - publisher starts to send messages - subscriber connect completes - subscriber starts to receive messages > 2- Does the latency curve below make since to you guy What does the X axis represent, is that message size? -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] 2.1.8?
On Mon, Aug 29, 2011 at 10:17 AM, Dirkjan Ochtman wrote: > Will 2.1.8 ever come out of RC, or will we go straight to 2.1.9? Could > the NEWS file on zeromq2-1 be updated to make the situation clear? The idea is to always use unique release numbers, and tag them to indicate their maturity. I've been postponing the 2.1.9 release to give people time to test the master, and I think we're ready for a new package. So we'll do the 2.1.9 stable release today. -Pieter ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
[zeromq-dev] pub/sub performance help
Hi all, I've got a simple pub/sub running on the same box The publisher sends 10 000 in a loop. The message is just a timestamps.( creation date) The subscriber reads the message and calculate the latency of each message in milliseconds (Ln = In-On) according to the guide. 1- Surprisingly, the subscriber is able to read only 6 000. I don't understand why 2- Does the latency curve below make since to you guy [cid:image002.png@01CC663D.60F21DA0] * This message and any attachments (the "message") are confidential, intended solely for the addressee(s), and may contain legally privileged information. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et susceptibles de contenir des informations couvertes par le secret professionnel. Ce message est etabli a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. * <>___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
[zeromq-dev] 2.1.8?
Hi there, Will 2.1.8 ever come out of RC, or will we go straight to 2.1.9? Could the NEWS file on zeromq2-1 be updated to make the situation clear? Cheers, Dirkjan ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] XREQ socket connect to multi endpoints
The code is OK, but you're connecting to an address '*', which is not valid. Specify the real IP address, or domain name. -Pieter On Mon, Aug 29, 2011 at 7:25 AM, notedit wrote: > > hi, i just have read the zero guide, and i know DEALER/ROUTER ==XREQ/XREP, > i alse read that a socket can connect to multi endpoints, > so i do a test, i try to use a xreq socket connect to multi req socket, > but it seems that it doesn't work. > this is my code > client : http://pastebin.com/jhcSdLgr > worker1: http://pastebin.com/iFtTkq5j > worker2: http://pastebin.com/jDQffB32 > anyone can explain that to me? many thanks > -- > > Best Wishes.. > > > ___ > 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
