ZeroMQ core engine in C++, implements ZMTP/3.1

Last update: Jan 8, 2023

Overview

ZeroMQ

Welcome

The ZeroMQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. ZeroMQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Supported platforms

Libzmq is mainly written in C++98 with some optional C++11-fragments. For configuration either autotools or CMake is employed. See below for some lists of platforms, where libzmq has been successfully compiled on.

Supported platforms with primary CI

OS and version	Architecture	Compiler and version	Build system	Remarks
Android NDK r20	arm, arm64, x86, x86_64	llvm (see NDK)	autotools	DRAFT
Ubuntu 14.04.5 LTS (trusty)	amd64	clang 5.0.0	autotools	STABLE, extras: GSSAPI, PGM, NORM, C++98 mode only
Ubuntu 14.04.5 LTS (trusty)	amd64	gcc 4.8.4	autotools	STABLE, DRAFT, extras: GSSAPI, PGM, NORM, TIPC, IPV6, also POLLER=poll, POLLER=select, also valgrind and address sanitizer executions
Ubuntu 14.04.5 LTS (trusty)	amd64	gcc 4.8.4	CMake 3.12.2	STABLE
Windows Server 2012 R2	x86	Visual Studio 2008	CMake 3.12.2	DRAFT
Windows Server 2012 R2	x86	Visual Studio 2010 SP1	CMake 3.12.2	DRAFT
Windows Server 2012 R2	x86	Visual Studio 2012 Update 5	CMake 3.12.2	DRAFT
Windows Server 2012 R2	x86, amd64	Visual Studio 2013 Update 5	CMake 3.12.2	DRAFT, STABLE (x86 Release only), also POLLER=epoll
Windows Server 2012 R2	x86	Visual Studio 2015 Update 3	CMake 3.12.2	DRAFT
Windows Server 2016	x86	Visual Studio 2017 15.9.6	CMake 3.13.3	DRAFT
cygwin 3.0.0 on Windows Server 2012 R2	amd64	gcc 7.4.0	CMake 3.6.2	DRAFT
MSYS2 ? on Windows Server 2012 R2	amd64	gcc 6.4.0	CMake ?	DRAFT
Mac OS X 10.13	amd64	Xcode 9.4.1, Apple LLVM 9.1.0	autotools	STABLE, DRAFT
Mac OS X 10.13	amd64	Xcode 9.4.1, Apple LLVM 9.1.0	CMake 3.11.4	DRAFT

Note: the platforms are regularly updated by the service providers, so this information might get out of date without any changes on the side of libzmq. For Appveyor, refer to https://www.appveyor.com/updates/ regarding platform updates. For travis-ci, refer to https://changelog.travis-ci.com/ regarding platform updates.

Supported platforms with secondary CI

OS and version	Architecture	Compiler and version	Build system
CentOS 6	x86, amd64	?	autotools
CentOS 7	amd64	?	autotools
Debian 8.0	x86, amd64	?	autotools
Debian 9.0	ARM64, x86, amd64	?	autotools
Fedora 28	ARM64, ARM32, amd64	?	autotools
Fedora 29	ARM64, ARM32, amd64	?	autotools
Fedora Rawhide	ARM64, ARM32, amd64	?	autotools
RedHat Enterprise Linux 7	amd64, ppc64	?	autotools
SuSE Linux Enterprise 12 SP4	ARM64, amd64, ppc64, s390x	?	autotools
SuSE Linux Enterprise 15	amd64	?	autotools
xUbuntu 12.04	x86, amd64	?	autotools
xUbuntu 14.04	x86, amd64	?	autotools
xUbuntu 16.04	x86, amd64	?	autotools
xUbuntu 18.04	x86, amd64	?	autotools
xUbuntu 18.10	x86, amd64	?	autotools

Supported platforms with known active users

At the time of writing, no explicit reports have been available. Please report your experiences by opening a PR adding an entry or moving an entry from the section below.

Under "last report", please name either the SHA1 in case of an unreleased version, or the version number in case of a released version.

OS and version	Architecture	Compiler and version	Build system	Last report
Solaris 10	x86, amd64, sparc	GCC 8.1.0	CMake	2019/03/18
DragonFly BSD	amd64	gcc 8.3	autotools	2018/08/07 git-72854e63
IBM i	ppc64	gcc 6.3	autotools	2019/10/02 git-25320a3
QNX 7.0	x86_64	gcc 5.4.0	CMake	4.3.2

Supported platforms without known active users

Note: this list is incomplete and inaccurate and still needs some work.

OS and version	Architecture	Compiler and version	Build system
Any Linux distribution	x86, amd64	gcc ?+, clang ?+, icc ?+	autotools, CMake
SunOS, Solaris	x86, amd64	SunPro	autotools, CMake
GNU/kFreeBSD	?	?	autotools, CMake
FreeBSD	?	?	autotools, CMake
NetBSD	?	?	autotools, CMake
OpenBSD	?	?	autotools, CMake
DragonFly BSD	amd64	gcc 8.3	autotools, CMake
HP-UX	?	?	autotools, CMake
GNU/Hurd	?	?	autotools
VxWorks 6.8	?	?	?
Windows CE	?	?	?
Windows UWP	?	?	?
OpenVMS	?	?	?

Unsupported platforms

OS and version	Architecture	Compiler and version	Remarks
QNX 6.3	?	gcc 3.3.5	see #3371, support was added by a user, but not contributed to upstream
Windows 10	ARM, ARM64	Visual Studio 2017	see #3366, probably only minor issues

For more details, see here.

For some platforms (Linux, Mac OS X), prebuilt binary packages are supplied by the ZeroMQ organization. For other platforms, you need to build your own binaries.

Installation of binary packages

Linux

For Linux users, pre-built binary packages are available for most distributions. Note that DRAFT APIs can change at any time without warning, pick a STABLE build to avoid having them enabled.

Latest releases

DEB

RPM

Bleeding edge packages

DEB

RPM

Example: Debian 9 latest release, no DRAFT apis

echo "deb http://download.opensuse.org/repositories/network:/messaging:/zeromq:/release-stable/Debian_9.0/ ./" >> /etc/apt/sources.list
wget https://download.opensuse.org/repositories/network:/messaging:/zeromq:/release-stable/Debian_9.0/Release.key -O- | sudo apt-key add
apt-get install libzmq3-dev

OSX

For OSX users, packages are available via brew.

brew install zeromq

Build from sources

To build from sources, see the INSTALL file included with the distribution.

Android

To build from source, see README file in the android build directory.

Resources

Extensive documentation is provided with the distribution. Refer to doc/zmq.html, or "man zmq" after you have installed libzmq on your system.

Website: http://www.zeromq.org/

Development mailing list: [email protected] Announcements mailing list: [email protected]

Git repository: http://github.com/zeromq/libzmq

ZeroMQ developers can also be found on the IRC channel #zeromq, on the Freenode network (irc.freenode.net).

License

The project license is specified in COPYING and COPYING.LESSER.

libzmq is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License (LGPL) as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

As a special exception, the Contributors give you permission to link this library with independent modules to produce an executable, regardless of the license terms of these independent modules, and to copy and distribute the resulting executable under terms of your choice, provided that you also meet, for each linked independent module, the terms and conditions of the license of that module. An independent module is a module which is not derived from or based on this library. If you modify this library, you must extend this exception to your version of the library.

libzmq is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

Contributing

This project uses C4(Collective Code Construction Contract) process for contributions.

Comments

$4.1.2: Assertion failed: Connection reset by peer (zeromq\src\signaler.cpp:298)$
4.1.2: Assertion failed: Connection reset by peer (zeromq\src\signaler.cpp:298)
Environment

Windows 10 x64

zeromq installed via pyzmq bundle (libzmq-4.1.2)

Compiler: MSVC9 (Windows SDK 7.0 / VS2008)

Reproduction

...is difficult, but for at least one user, leaving a Jupyter notebook running can die with any of the following asserts:

Assertion failed: Connection reset by peer (src\signaler.cpp:181) Assertion failed: Connection reset by peer (src\signaler.cpp:298) Assertion failed: nbytes == sizeof (dummy) (src\signaler.cpp:303) Assertion failed: ok (src\mailbox.cpp:94)

The mailbox assert is longstanding and still open at #1108. Any ideas on what might be the cause of the connection resets or the size mismatch?
Area (Runtime / Usage) Binding (non-C) Symptom (Assertion failure)
opened by minrk 84
Very high latency in dealer-router

Using libzmq 4 2.5 on centos 7. Getting very high latency when messages are sent from dealer to router and even from router to dealer. So i wrote simple client-server program using tcp and sent messages between them just for comparison. Tcp appears to be fast.

Sending single byte from dealer to router, zmq takes 900 microseconds.

Sending single byte from client to server, tcp takes 150 microseconds.

What am I doing wrong. I thought zmq will be atleast as fast as tcp. Is there any tuning I can do to make zmq faster?
stale

opened by nagarajsherigar 81
Linger -1 is still not working correctly

https://github.com/zeromq/libzmq/issues/919 noted that https://github.com/zeromq/libzmq/pull/1511 seemed to fix the issue, however based on more testing it seems the fix is not complete. In a scenario I have, a stable PULL socket, with multiple dynamic PUSH sockets, the last message may not get sent before close(). I have validated that by sending HWM +1 messages of size SNDBUF that the last message will then get delivered. This is a really bad issue as it involves data loss. I'll try to get a testcase extracted from my application soon. I'm guessing there's some extra OS level buffering that's not being accounted for.
Area (Runtime / Usage) Symptom (Unexpected behavior)

opened by thehesiod 81
CI and AppVeyor Build Issues
The CI builds seem to be failing and the shields in README are marked as such, so I have put this up in case anyone gets to it before I do, or if anyone would like to help.

Issues:

AppVeyor builds failing at the test stage (about 5 of the tests fail)

AppVeyor build configurations need to be reviewed

Travis CI builds are failing

These are good starter problems for anyone who wants to get involved in the project.
Area (Build/Compilation) Area (Testing) Platform (windows/msvc) Starter Tasks stale
opened by hitstergtd 61

PUB crash when SUB exceeded SNDHWM

Please use this template for reporting suspected bugs or requests for help.

Issue description

When all of these conditions are satisfied, the assertion failure from mtrie.cpp occurs:

A connection between a PUB socket and many SUB sockets.
A SUB socket subscribe/unsubscribe many prefixes.
Call zmq_getsockopt() with ZMQ_EVENTS for SUB sockets.

Assertion failed: erased == 1 (src/mtrie.cpp:297)
[1]    30266 abort (core dumped)  ./a.out

Environment

libzmq version (commit hash if unreleased): 4.2.0 and 4.2.3
OS: Ubuntu 16.04 LTS

Minimal test code / Steps to reproduce the issue

To reproduce this crash, we should prepare a PUB socket and many SUB sockets.

We will call this sequence (pseudo-code): pub.connect(sub) or sub.connect(pub); pub.getsockopt(ZMQ_EVENTS); sub.subscribe(prefix); sub.getsockopt(ZMQ_EVENTS); sub.unsubscribe(prefix); sub.getsockopt(ZMQ_EVENTS). There will be many prefixes to subscribe/unsubscribe.

Calling getsockopt(ZMQ_EVENTS) after SUB's SUBSCRIBE/UNSUBSCRIBE, or PUB's zmq_connect() will produce a crash due to the assertion failure in mtrie_t::rm_helper.

You can switch PUB<->SUB connection topology by the pub_to_sub variable.

#include "zmq.h"
#include <stdio.h>

// Set 1 or 0 to switch the PUB<->SUB connection topology.
static int pub_to_sub = 1;

void gen_topic(int n, char* topic)
{
    // Simple hash function to generate a subscription prefix from a number.
    n = (n * 2654435761);
    sprintf(topic, "%08x", n);
}

void getsockopt_events_within_many_subscriptions(void* sub)
{
    char topic[8];
    char opt[256];
    size_t opt_len = 256;

    for (int j = 0; j < 10000; ++j)
    {
        gen_topic(j, topic);
        zmq_setsockopt(sub, ZMQ_SUBSCRIBE, &topic, 8);
        // CRASH: Get ZMQ_EVENTS from a SUB socket.
        zmq_getsockopt(sub, ZMQ_EVENTS, opt, &opt_len);
    }
    for (int j = 0; j < 10000; ++j)
    {
        gen_topic(j, topic);
        zmq_setsockopt(sub, ZMQ_UNSUBSCRIBE, &topic, 8);
        // CRASH: Get ZMQ_EVENTS from a SUB socket.
        zmq_getsockopt(sub, ZMQ_EVENTS, opt, &opt_len);
    }
}

int main()
{
    printf("%d.%d.%d\n", ZMQ_VERSION_MAJOR, ZMQ_VERSION_MINOR, ZMQ_VERSION_PATCH);

    void *context = zmq_ctx_new();
    void *pub = zmq_socket(context, ZMQ_PUB);
    void *sub;

    char addr[256]; size_t addr_len = 256;
    char opt[256];  size_t opt_len  = 256;

    if (pub_to_sub)
    {
        // PUB->SUB
        for (int i = 0; i < 100; ++i)
        {
            sub = zmq_socket(context, ZMQ_SUB);

            zmq_bind(sub, "tcp://127.0.0.1:*");
            zmq_getsockopt(sub, ZMQ_LAST_ENDPOINT, addr, &addr_len);
            zmq_connect(pub, addr);

            getsockopt_events_within_many_subscriptions(sub);
        }
    }
    else
    {
        // SUB->PUB
        zmq_bind(pub, "tcp://127.0.0.1:*");
        zmq_getsockopt(pub, ZMQ_LAST_ENDPOINT, addr, &addr_len);
        for (int i = 0; i < 100; ++i)
        {
            sub = zmq_socket(context, ZMQ_SUB);

            zmq_connect(sub, addr);

            getsockopt_events_within_many_subscriptions(sub);

            // CRASH: Get ZMQ_EVENTS from the PUB socket.
            zmq_getsockopt(pub, ZMQ_EVENTS, opt, &opt_len);
        }
    }
}

What's the actual result? (include assertion message & call stack if applicable)

$ gcc zmq_events_crash.c -L ~/usr/local/lib -lzmq && ./a.out
4.2.3
Assertion failed: erased == 1 (src/mtrie.cpp:297)
[1]    30266 abort (core dumped)  ./a.out

What's the expected result?

$ gcc zmq_events_crash.c -L ~/usr/local/lib -lzmq && ./a.out
4.2.3
$ echo $?
0

When SUB sockets connect to the PUB socket, this crash doesn't happen.

Platform (linux/generic) Symptom (Assertion failure)

opened by sublee 60

ZeroMQ does not build for QNX 6.3 with CMake
Issue description

I am evaluating ZeroMQ for use with our embedded product, but we are constrained to running on QNX 6.3 (ancient) and building with GCC 3.3.5. I am cross-compiling the library on Windows using CMake within Qt Creator/MinGW. CMake generation succeeds, but compilation fails.

For example, ZeroMQ expects malloc() to be declared in <stdlib.h> but QNX declares it in <malloc.h>. This could be fixed with something like:

#ifdef __QNXNTO__ #include <malloc.h> #endif

A similar conditional would correct the problem that QNX has <sys/poll.h> instead of <poll.h>.

Environment

libzmq version: 4.3.1

OS: Windows 7 x64 SP1

QNX Momentics IDE 6.3.0 + Service Pack 2 provides the toolchain - GCC 3.3.5

CMake 3.9.4

Qt Creator 3.6.1 - kit: Desktop Qt 5.6.0 MinGW 32bit

Minimal test code / Steps to reproduce the issue

It's complicated since it requires custom CMake files that include setup for cross-compiling for QNX.

What's the actual result? (include assertion message & call stack if applicable)

15:01:46: Running steps for project 3rdPartyResearch... 15:01:46: Starting: "C:\Projects\Qt\5.6.0\MingW\Tools\mingw492_32\bin\mingw32-make.exe" [ 0%] Building C object libzmq/CMakeFiles/objects.dir/src/tweetnacl.c.o [ 1%] Building CXX object libzmq/CMakeFiles/objects.dir/src/precompiled.cpp.o [ 1%] Building CXX object libzmq/CMakeFiles/objects.dir/src/address.cpp.o [ 1%] Building CXX object libzmq/CMakeFiles/objects.dir/src/client.cpp.o In file included from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/socket_base.hpp:39, from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/client.hpp:33, from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/client.cpp:32: C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp: In constructor zmq::blob_t::blob_t(unsigned int): C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp:79: error: malloc undeclared (first use this function) C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp:79: error: (Each undeclared identifier is reported only once for each function it appears in.) C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp: In constructor zmq::blob_t::blob_t(const unsigned char*, unsigned int): C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp:89: error: malloc undeclared (first use this function) C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp: In member function void zmq::blob_t::set_deep_copy(const zmq::blob_t&): C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp:129: error: malloc undeclared (first use this function) C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp: In member function void zmq::blob_t::set(const unsigned char*, unsigned int): C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp:140: error: malloc undeclared (first use this function) C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp: In member function void zmq::blob_t::clear(): C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp:151: error: free undeclared (first use this function) C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp: In destructor zmq::blob_t::~blob_t(): C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/blob.hpp:160: error: free undeclared (first use this function) In file included from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/poller.hpp:52, from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/socket_base.hpp:41, from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/client.hpp:33, from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/client.cpp:32: C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/poll.hpp:43:18: poll.h: No such file or directory In file included from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/poller.hpp:52, from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/socket_base.hpp:41, from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/client.hpp:33, from C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/client.cpp:32: C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/poll.hpp: At global scope: C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/poll.hpp:96: error: pollfd was not declared in this scope C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/poll.hpp:96: error: template argument 1 is invalid C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/poll.hpp:96: error: template argument 2 is invalid C:/Data/Workspaces/3rdPartyResearch/source/zeromq-4.3.1/src/poll.hpp:96: error: ISO C++ forbids declaration of pollset_t with no type cc: C:/QNX630/host/win32/x86/usr/lib/gcc-lib/i386-pc-nto-qnx6.3.0/3.3.5/cc1plus caught signal 1 libzmq\CMakeFiles\objects.dir\build.make:133: recipe for target 'libzmq/CMakeFiles/objects.dir/src/client.cpp.o' failed mingw32-make[2]: [libzmq/CMakeFiles/objects.dir/src/client.cpp.o] Error 1 CMakeFiles\Makefile2:128: recipe for target 'libzmq/CMakeFiles/objects.dir/all' failed mingw32-make[1]: [libzmq/CMakeFiles/objects.dir/all] Error 2 makefile:128: recipe for target 'all' failed mingw32-make: [all] Error 2 15:01:51: The process "C:\Projects\Qt\5.6.0\MingW\Tools\mingw492_32\bin\mingw32-make.exe" exited with code 2. Error while building/deploying project 3rdPartyResearch (kit: Desktop Qt 5.6.0 MinGW 32bit) When executing step "Make" 15:01:51: Elapsed time: 00:04.

What's the expected result?

Code compiles without errors for QNX 6.3.
Area (Build/Compilation) Platform (qnx)
opened by sherwood-nyab 54
one crash in windows server 2008

developing a 32-bit server plugin dll project which runs on windows server 2008 64bit i tried zmq function with connect, send, close. It causes the server down every time. So, I focused on the code, if I ignore the line send_plug (object_) in own.cpp, it will not lead the sever down. But I don't know if it works well if without this line.

is there probably a bug for socket thread management in zmq? I also notice "LIBZMQ_UNUSED (priority_)" in the code. anyway, I want that helps fix.

opened by gebogebo 52
Problem: address parsing code is tied to the TCP code

Solution: Factor the code into a different file with a well defined API and add unit tests.

My Debian doesn't have a recent-enough clang-format to run make clang-format-check so apologies in advance if I messed up the coding style here and there (which is almost certain given the size of the patch).

I've attempted to match the previous implementation perfectly, including the arguable "quirks" such as the ones I've reported in #3069 (and a few others that I'm not sure about, such as specifying a %scope for an IPv4 address).

This is a pretty huge patch so I tried to be very comprehensive in the unit tests. I think the only path of the code that's not tested is when specifying an interface name as a bind point since the implementations to find the IP address associated with a network interface vary wildly from platform to platform so it's not trivial to come up with generic test code. I've tested manually that it still worked on Linux at least and I haven't made significant modifications to the architecture-specific code so I have good hopes that I haven't irremediably broken it.

opened by simias 51
Significant performance decrease compared to 4.1.5
Hello,

I noticed a drop of performance between 4.1.5 and the current 4.2.0 HEAD.

I ran the performance tests on the two versions with 1MB message size (to clearly see it, but it seems to happen as well with 100B messages, with about x2 difference factor in throughtput) repeated 1000 times. The local and remote are on the same physical machines, but in two separate docker containers (I can provide all the dockerfiles & co. if you have trouble reproducing it).

Version 4.1.5 throughput test: local_thr tcp://*:7000 1048576 1000 remote_thr tcp://local:7000 1048576 1000

ZMQ Version: 4.1.5 message size: 1048576 [B] message count: 1000 mean throughput: 1614 [msg/s] mean throughput: 13539.213 [Mb/s] real 0m0.954s user 0m0.064s sys 0m0.620s

Version 4.2.0 throughput test: local_thr tcp://*:7000 1048576 1000 remote_thr tcp://local:7000 1048576 1000

ZMQ Version: 4.2.0 message size: 1048576 [B] message count: 1000 mean throughput: 227 [msg/s] mean throughput: 1904.214 [Mb/s] real 0m4.693s user 0m0.144s sys 0m3.916s

Version 4.1.5 latency test: local_lat tcp://*:7000 1048576 1000 remote_lat tcp://local:7000 1048576 1000

ZMQ Version: 4.1.5 real 0m2.598s user 0m0.068s sys 0m0.800s message size: 1048576 [B] roundtrip count: 1000 average latency: 646.348 [us]

Version 4.2.0 latency test: local_lat tcp://*:7000 1048576 1000 remote_lat tcp://local:7000 1048576 1000

ZMQ Version: 4.2.0 real 0m10.371s user 0m0.248s sys 0m5.004s message size: 1048576 [B] roundtrip count: 1000 average latency: 4517.717 [us]

I notice this performance drop also in the real application as well as in this application own performance tests (using different socket types than from the zmq perf testers).

Any idea which change could have brought such drop?

Cheers, Axel
Critical Resource Utilization (Performance / Memory) Area (Runtime / Usage) Platform (linux/generic)
opened by AxelVoitier 50
deadlock between zmq_poll, zmq_send using inproc PAIR sockets
Issue description

Using the pattern described in "Signaling between Threads” zmq_send deadlocks when the receiving (bind) thread is in zmq_poll.

Environment

libzmq version (commit hash if unreleased): d17581929cceceda02b4eb8abb054f996865c7a6

OS: CentOS 6

What's the actual result? (include assertion message & call stack if applicable)

Call stack attached. There appears to be a deadlock between thread 1 & thread 5.

What's the expected result?

zmq_send should succeed and trigger zmq_poll to return with read event on the PAIR socket.

poll-hang.txt
Area (Runtime / Usage) Platform (linux/generic) Symptom (Hang) stale
opened by WallStProg 49
assertion failure in mailbox.cpp:82
Environment

OS - MS Windows 7 Ultimate SP1,

Compiler - Visual Studio 2013

Version of ZeroMQ - 4.0.4, both variants: linking compiled dll and compile ZMQ source code.

We checked previous stable version 3.2.4 and development master on github - the same problem

How to reproduce

The C++ application is running and in several hours zmq_assert raises an exception in zmq::mailbox_t::recv line 82 and the application is crashed. Timeout isn't constant, could be 4 hours and more. It occurs even if the application has not had any zeromq tcp connections.

We found that ZeroMQ creates internal tcp connection (several sockets). It passes signals between zeromq threads or something else. But this is other sockets than for publisher-subsribers connection.

The exception raises when a disconnect event occurs in this internal tcp connection (got it in an network sniffer). We didn't find who initiated disconnect; we didn't find that ZeroMQ calls socket closing before.

The disconnect event changes the status of socket for WinSock select() method, it generates an read operation:

void zmq::select_t::loop () { . . . if (FD_ISSET (fds [i].fd, &readfds)) fds [i].events->in_event (); ß line 197 . . . }

http://msdn.microsoft.com/en-us/library/windows/desktop/ms740141(v=vs.85).aspx

readfds:

If listen has been called and a connection is pending, accept will succeed.

Data is available for reading (includes OOB data if SO_OOBINLINE is enabled).

Connection has been closed/reset/terminated.

Then ZeroMQ is trying to read data from socket:

void zmq::io_thread_t::in_event () { . . . command_t cmd; int rc = mailbox.recv (&cmd, 0); ß line 69 . . . }

And it raises an exception on checks after reading because there is nothing to read:

int zmq::mailbox_t::recv (command_t *cmd_, int timeout_) { . . . // Get a command. errno_assert (rc == 0); bool ok = cpipe.read (cmd_); zmq_assert (ok); ß line 82 (crashed here) return 0; }
Platform (windows/msvc) Area (Runtime / Usage) Symptom (Assertion failure) stale
opened by hintjens 41

Self-test failures

Please use this template for reporting suspected bugs or requests for help.

Issue description

Three of the libzmp test-suites are "FAIL"

Environment

libzmq version: 4.3.4 ** with PR #4478 patch ** with patch to ./configure for 10.10+ bug in ancient libtool (dynamic-library options)
OS: OS X 10.13, xcode-10.1
libsodium (1.0.18) and all other non-Apple-default tools via fink (prefix is /sw)

Minimal test code / Steps to reproduce the issue

export CPPFLAGS=-I/sw/include LDFLAGS=-L/sw/lib
./configure --prefix=/sw --disable-silent-rules
/usr/bin/make
ulimit -n 1200; make check

What's the actual result? (include assertion message & call stack if applicable)

Nothing obviously problematic in configure process. The only configuration diagnostics that seem useful are:

checking for libbsd... no
configure: WARNING: Cannot find libbsd
[...]
configure: Building stable and legacy API (no draft API)
checking for libunwind... no
configure: WARNING: Cannot find libunwind

The compiling itself has no warnings. But then three tests fail. The test-suite.log segments are:

FAIL: tests/test_reqrep_tcp

WARNING: Forced closure of 4 sockets, this is an implementation error unless the test case failed
WARNING: Forced closure of 3 sockets, this is an implementation error unless the test case failed
WARNING: Forced closure of 4 sockets, this is an implementation error unless the test case failed
WARNING: Forced closure of 3 sockets, this is an implementation error unless the test case failed
tests/test_reqrep_tcp.cpp:212:test_single_connect_ipv4:PASS
tests/test_reqrep_tcp.cpp:96:test_multi_connect_ipv4:FAIL: zmq_connect (sc, my_endpoint_3) failed, errno = 22 (Invalid argument)
tests/test_reqrep_tcp.cpp:142:test_multi_connect_same_port_ipv4:FAIL: zmq_connect (sc0, my_endpoint_2) failed, errno = 22 (Invalid argument)
tests/test_reqrep_tcp.cpp:215:test_single_connect_ipv6:PASS
tests/test_reqrep_tcp.cpp:96:test_multi_connect_ipv6:FAIL: zmq_connect (sc, my_endpoint_3) failed, errno = 22 (Invalid argument)
tests/test_reqrep_tcp.cpp:142:test_multi_connect_same_port_ipv6:FAIL: zmq_connect (sc0, my_endpoint_2) failed, errno = 22 (Invalid argument)
-----------------------
6 Tests 4 Failures 0 Ignored
FAIL
FAIL tests/test_reqrep_tcp (exit status: 4)

FAIL: tests/test_stream_exceeds_buffer

WARNING: Forced closure of 1 sockets, this is an implementation error unless the test case failed
tests/test_stream_exceeds_buffer.cpp:47:test_stream_exceeds_buffer:FAIL: zmq_connect (zsock, my_endpoint) failed, errno = 22 (Invalid argument)

-----------------------
1 Tests 1 Failures 0 Ignored
FAIL
FAIL tests/test_stream_exceeds_buffer (exit status: 1)

FAIL: tests/test_use_fd

WARNING: Forced closure of 2 sockets, this is an implementation error unless the test case failed
WARNING: Forced closure of 2 sockets, this is an implementation error unless the test case failed
tests/test_use_fd.cpp:64:test_req_rep_tcp:FAIL: zmq_connect (*out_sc_, my_endpoint) failed, errno = 22 (Invalid argument)
tests/test_use_fd.cpp:64:test_pair_tcp:FAIL: zmq_connect (*out_sc_, my_endpoint) failed, errno = 22 (Invalid argument)
tests/test_use_fd.cpp:205:test_client_server_tcp:PASS
tests/test_use_fd.cpp:207:test_req_rep_ipc:PASS
tests/test_use_fd.cpp:208:test_pair_ipc:PASS
tests/test_use_fd.cpp:209:test_client_server_ipc:PASS

-----------------------
6 Tests 2 Failures 0 Ignored
FAIL
FAIL tests/test_use_fd (exit status: 2)

What's the expected result?

All tests PASS (or SKIP/XFAIL as appropriate)

opened by dmacks 0

Do not force LTO on MSVC users in CMake
Issue description

When building through CMake with MSVC, BUILD_SHARED=on and CMAKE_BUILD_TYPE != Debug then /GL and /LTCG are automatically added to the compilation. This forces consumers to also link their application with /LTCG which is not always desired. Recommendation: Allow users to choose link-time optimization themselves, e.g. by setting CMAKE_INTERPROCEDURAL_OPTIMIZATION.

Environment

libzmq version 4.3.4:

OS: Windows

Compiler: MSVC (Microsoft (R) C/C++ Optimizing Compiler Version 19.34.31937 for x64)

Minimal test code / Steps to reproduce the issue

vcpkg install --host-triplet=x64-windows-static --triplet=x64-windows-static zeromq

Link the installed library into a test project and compile a release build

What's the actual result? (include assertion message & call stack if applicable)

libzmq-mt-s-4_3_4.lib(zmq.cpp.obj) : MSIL .netmodule or module compiled with /GL found; restarting link with /LTCG; add /LTCG to the link command line to improve linker performance

What's the expected result?

Nothing
opened by Tradias 0
sprintf deprecation error failing build on macOS
Issue description

Build is failing in macOS 13.1

Environment

OS: macOS 13.1 Build Environment: Apple clang version 14.0.0 (clang-1400.0.29.202) Target: x86_64-apple-darwin22.2.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

libzmq version (commit hash if unreleased): dfbfc59c3fe4e782d1640f32af1056a2e74f9aaa

OS: macOS 13.1

Minimal test code / Steps to reproduce the issue

Run the following command after git clone:

./autogen.sh

./configure

make

What's the actual result? (include assertion message & call stack if applicable)

make[1]: Nothing to be done for `all'. CXX src/libzmq_la-tcp_address.lo src/tcp_address.cpp:132:12: error: 'sprintf' is deprecated: This function is provided for compatibility reasons only. Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Werror,-Wdeprecated-declarations] pos += sprintf (pos, "%d", ntohs (port_)); ^ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/stdio.h:188:1: note: 'sprintf' has been explicitly marked deprecated here __deprecated_msg("This function is provided for compatibility reasons only. Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead.") ^ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:215:48: note: expanded from macro '__deprecated_msg' #define __deprecated_msg(_msg) attribute((deprecated(_msg))) ^ 1 error generated. make[1]: *** [src/libzmq_la-tcp_address.lo] Error 1 make: *** [all-recursive] Error 1

What's the expected result?

Build should pass
opened by ghmanoj 2
Assertion failed: false (src/object.cpp:170)
Issue description

I am using CZMQ + ZMQ. I process around 1000 msgs per second on PUB/SUB and about once a day my process crashes with this line printed: Assertion failed: false (src/object.cpp:170). What would the most likely cause of this?

Environment

libzmq version (commit hash if unreleased): latest master

OS: linux
opened by yuriymyronovych 0
loss of subscription, when inside a docker container who's host had a network outage
Issue description

A nodeJS powered zeroMQ subscriber loses connection to the broker/publisher. Said subscriber is inside a docker container, whose host just had a network-event, that caused a disconnect-reconnect of the network interface the docker host would connect to the zeroMQ broker/publisher. Any messages targeted to the subscribers topics will not reach the subscriber any more, until the docker container it is running inside is restartet.

If the subscriber is not inside a docker, but rather directly on the docker host, the network-outage does not influence its ability to receive messages of topics subscribed to.

manipulating the TCP timeouts (inside the docker and on the docker host) cannot solve this.

Environment

libzmq version (commit hash if unreleased): npm [email protected] / npm [email protected] (I do not know which libzmq that is)

OS: ubuntu 22.04 and 20.04 (fails on both, propably even down to 16.04)

nodeJS 14.x and 17.x and 18.12

Minimal test code / Steps to reproduce the issue

you need Docker for that and two VMs (works with physical devices too).

by re-using a tutorial for upcomming zeroMQ 6 on nodeJs vom dev.to, two js files were created. note that this is the code for 6.0.0b; you can make it work for 5.2.8, if you switch out the socket creation (there is a commented line with the code for that).

Beware, the worker has a fixed IP for the VM inserted, where the Broker/Publisher/Server is running. You should adjust that to fit your setup:

// @/server.js const Fastify = require("fastify"); const zmq = require("zeromq"); const app = Fastify(); // const sock = zmq.socket("pub"); const sock = new zmq.Publisher(); app.post("/", async (request, reply) => { await sock.send(["dev.to", JSON.stringify({ ...request.body })]); return reply.send("Sent to the subscriber/worker."); }); const main = async () => { try { await sock.bind("tcp://*:7890"); await app.listen(3000, '0.0.0.0'); } catch (err) { console.error(err); process.exit(1); } }; main();

// @/worker.js const zmq = require("zeromq"); //const sock = zmq.socket("sub"); const sock = new zmq.Subscriber(); // is for zeromq 6 // const main = async () => { try { sock.connect("tcp://10.0.2.4:7890"); sock.subscribe("dev.to"); for await (const [topic, msg] of sock) { console.log("Received message from " + topic + " channel:"); console.log(JSON.parse(msg)); } //sock.on("message", function(topic, message) { // console.log("message:", message, "topic", topic); // //}); }catch(err) { console.error(err); process.exit(1); } }; main();

next, a Dockerfile is used to create an image, containing both files (you can make two images with one file each too, but this way is faster):

FROM ubuntu:22.04 RUN apt-get update && apt-get install -y curl RUN curl -sL https://deb.nodesource.com/setup_14.x -o /tmp/nodesource_setup.sh RUN bash /tmp/nodesource_setup.sh RUN apt-get update && apt-get install -y nodejs net-tools RUN node -v && npm -v RUN npm install zeromq fastify COPY server.js /var/tmp/server.js COPY worker.js /var/tmp/worker.js WORKDIR /var/tmp/

build that with

docker build ./ -t zeromq

which should result in an image with the tag zeromq:latest being build. That can be startet with a docker-compose.yml:

version: '3' networks: zero: services: worker: image: zeromq:latest networks: zero: command: node worker.js server: image: zeromq:latest networks: zero: command: node server.js ports: - 3000:3000 - 7890:7890

As you see, this docker-compose.yml defines two services, one is running the server.js, one is running the worker.js. Start the server on VM A, and the client on VM B with

docker-compose up server and docker-compose up worker

We do not detach from these, so we can see the log immediately. You should start a second worker at VM A, next to the broker, so you can compare their output.

And now you can send stuff to the broker with

curl -X POST 10.4.0.2:3000 -d "test"

or using Postman, if you like. However, the Container for the worker should now log whatever was in -d.

Now... go to the VM B, running the worker docker, and disconnect it from your network. I am useing VirtualBox, which enables me to just un-tick and re-tick the network device.

Now POST a message again and... the VM B worker will not receive any messages, while the one at A still does. B will not receive any messages, until you restart the docker.

EDiT: There is an other way of recreating the connection... kind of. If you go inside the docker (docker-compose exec worker /bin/bash) and start the worker again / a second time (node worker.js), then this instance will be able to receive messages published. But this instance will also fail to do so, if you do the dis/reconnect again afterwards.

So, whatever zeroMQ does to hold the connection breaks apart once the host of its docker container has a network hickup.

What's the actual result? (include assertion message & call stack if applicable)

I am sorry, the result is "nothing happens at the subscribers side"... so I do not have anything to put here.

What's the expected result?

the subscriber either manages to reconnect after a while, or it does not lose the connection at all. Messages published will reach the subscriber at the dis/reconnected docker host.

how was this noticed?

this Project: https://github.com/DeviceFarmer/stf it uses zeromq 5.2.8 on nodejs 17.4 to allow communication between the different services, that make it up. if one of the secondary servers encounters an network outage of some kind (however short), the android phones connected to it cannot be used any more, as the zeroMQ subscriber running there will not receive messages from the main server any more.

At least, we were able to replicate the issue there with the network dis/reconnect, which in the end was found out to be caused by zeroMQ, as it seems.
opened by ConfusedMerlin 0

Releases(v4.3.4)

v4.3.4(Jan 17, 2021)
0MQ version 4.3.4 stable, released on 2021/01/17

New DRAFT (see NEWS for 4.2.0) socket option:

ZMQ_PRIORITY will set the SO_PRIORITY socket option on the underlying sockets. Only supported on Linux. See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details.

Fixed #4113 - compilation errors on kFreeBSD and GNU/Hurd

Fixed #4086 - excessive amount of socket files left behind in Windows TMP directory

Fixed #4108 - regression that breaks using IPv6 link-local addresses on Linux

Fixed #4078 - compilation errors on Android

Fixed #4074 - compilation error with ulibc and libbsd

Fixed #4060 - stack overflow on Windows x64

Fixed #4051 - various compilation errors on Windows ARM 32bit

Fixed #4043 - various compilation warnings with XCode

Fixed #4038 - return value of zmq_ctx_get changed unintentionally

Source code(tar.gz)
Source code(zip)
libzmq-mingw64-4_3_4.zip(8.40 MB)
libzmq-v100-4_3_4.zip(2.10 MB)
libzmq-v120-4_3_4.zip(2.08 MB)
libzmq-v120-epoll-4_3_4.zip(2.08 MB)
libzmq-v120-gd-4_3_4.zip(41.46 MB)
libzmq-v120-gd-x64-4_3_4.zip(42.75 MB)
libzmq-v120-nocurve-4_3_4.zip(1.67 MB)
libzmq-v120-x64-4_3_4.zip(2.51 MB)
libzmq-v140-4_3_4.zip(1.81 MB)
libzmq-v140-x64-4_3_4.zip(2.24 MB)
libzmq-v141-4_3_4.zip(1.80 MB)
libzmq-v141-gd-uwp-4_3_4.zip(2.78 MB)
libzmq-v141-uwp-4_3_4.zip(867.37 KB)
libzmq-v141-x64-4_3_4.zip(2.25 MB)
libzmq-v142-x64-4_3_4.zip(2.48 MB)
libzmq-v90-4_3_4.zip(2.04 MB)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.3.4.tar.gz(2.37 MB)
zeromq-4.3.4.zip(3.22 MB)
v4.3.3(Sep 7, 2020)
0MQ version 4.3.3 stable, released on 2020/09/07

Security advisories:

CVE-2020-15166: Denial-of-Service on CURVE/ZAP-protected servers by unauthenticated clients. If a raw TCP socket is opened and connected to an endpoint that is fully configured with CURVE/ZAP, legitimate clients will not be able to exchange any message. Handshakes complete successfully, and messages are delivered to the library, but the server application never receives them. For more information see the security advisory: https://github.com/zeromq/libzmq/security/advisories/GHSA-25wp-cf8g-938m

Stack overflow on server running PUB/XPUB socket (CURVE disabled). The PUB/XPUB subscription store (mtrie) is traversed using recursive function calls. In the remove (unsubscription) case, the recursive calls are NOT tail calls, so even with optimizations the stack grows linearly with the length of a subscription topic. Topics are under the control of remote clients - they can send a subscription to arbitrary length topics. An attacker can thus cause a server to create an mtrie sufficiently large such that, when unsubscribing, traversal will cause a stack overflow. For more information see the security advisory: https://github.com/zeromq/libzmq/security/advisories/GHSA-qq65-x72m-9wr8

Memory leak in PUB server induced by malicious client(s) without CURVE/ZAP. Messages with metadata are never processed by PUB sockets, but the metadata is kept referenced in the PUB object and never freed. For more information see the security advisory: https://github.com/zeromq/libzmq/security/advisories/GHSA-4p5v-h92w-6wxw

Memory leak in client induced by malicious server(s) without CURVE/ZAP. When a pipe processes a delimiter and is already not in active state but still has an unfinished message, the message is leaked. For more information see the security advisory: https://github.com/zeromq/libzmq/security/advisories/GHSA-wfr2-29gj-5w87

Heap overflow when receiving malformed ZMTP v1 packets (CURVE disabled). By crafting a packet which is not valid ZMTP v2/v3, and which has two messages larger than 8192 bytes, the decoder can be tricked into changing the recorded size of the 8192 bytes static buffer, which then gets overflown by the next message. The content that gets written in the overflown memory is entirely decided by the sender. For more information see the security advisory: https://github.com/zeromq/libzmq/security/advisories/GHSA-fc3w-qxf5-7hp6

Note for packagers: an external, self-contained sha1 library is now included in the source tree under external/sha1/ - it is licensed under BSD-3-Clause and thus it is fully compatible with libzmq's license. It is only used if WebSockets support is enabled, and if neither GnuTLS nor NSS are available.

Note for packagers: an internal reimplementation of strlcpy is now included, for wider platform compatibility. libbsd can be used and is enabled by default if available instead of the internal implementation, for better security maintenance in distros.

Note for packagers: ZeroMQConfig.cmake is now installed in the arch-dependent subdirectory - eg: /usr/lib/x86_64-linux-gnu/cmake/

New DRAFT (see NEWS for 4.2.0) socket type:

ZMQ_CHANNEL is a thread-safe alternative to ZMQ_PAIR. See doc/zmq_socket.txt for details.

New DRAFT (see NEWS for 4.2.0) socket option:

ZMQ_ONLY_FIRST_SUBSCRIBE will cause only the first part of a multipart message to be processed as a subscribe/unsubscribe message, and the rest will be forwarded as user data to the application.

ZMQ_RECONNECT_STOP will cause a connecting socket to stop trying to reconnect in specific circumstances. See the manpage for details.

ZMQ_HELLO_MSG to set a message that will be automatically sent to a new connection.

ZMQ_DISCONNECT_MSG to set a message that will be automatically received when a peer disconnects. See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details.

New DRAFT (see NEWS for 4.2.0) zmq_ctx_get_ext/zmq_ctx_set_ext APIs were added to allow enhancing the context options with variable data inputs. See doc/zmq_ctx_get_ext.txt and doc/zmq_ctx_set_ext.txt for details.

New DRAFT (see NEWS for 4.2.0) transport options WS and WSS added for support of WebSockets (and secure WebSockets via TLS) via the ZWS 2.0 protocol. WSS requires the GnuTLS library for TLS support. ZMQ_WSS_ specific socket options were added to support TLS. WebSockets support is disabled by default if DRAFT APIs are disabled.

New DRAFT (see NEWS for 4.2.0) socket type, PEER, which is thread safe and a related zmq_connect_peer function which atomically and thread-safely connects and returns a routing-id.

New DRAFT (see NEWS for 4.2.0) zmq_msg_init_buffer API was added to allow the construction of a message by copying from an existing buffer.

New DRAFT (see NEWS for 4.2.0) zmq_poller_size API was added to allow querying the number of sockets/fds registered in a zmq_poller.

ZMTP 3.1 peers will receive subscribe/cancel on PUB/SUB via commands rather than using the first byte of the payload.

zmq_z85_decode now checks that the input string's length is at least 5 characters and always a multiple of 5 as per API specification.

Fixed #3566 - malformed CURVE message can cause memory leak

Fixed #3567 - missing ZeroMQ_INCLUDE_DIR in ZeroMQConfig.cmake when only static lib is built

Fixed #3576 - CURVE plaintext secrets now stored in libsodium's secure memory

Fixed #3588 - install debug libraries for debug msvc builds with CMake

Fixed #3591 - incorrect ZMQ_MAX_SOCKETS default value in doc

Fixed #3594 - fixed stream_engine use after free due to concurrent heartbeats

Fixed #3586 - error when compiling with MinGW due to usage of MS-specific __except keyword

Fixed #3603 - fixed CMake build on SL6.9

Fixed #3607 - added scripts to ease performance graph generation

Fixed #3608 - fix for IPv4 mapping not supported in DragonFlyBSD

Fixed #3636 - added ENABLE_PRECOMPILED CMake option to fix build with Ninja

Fixed #2862 - UDP engine aborts on networking-related errors from socket syscalls

Fixed #3656 - segfault on sending data from XSUB to XPUB

Fixed #3646 - static-only test run fails

Fixed #3668 - fixed CMAKE_CXX_FLAGS_* regexes on MSVC

Fixed #110 - do not include winsock2.h in public zmq.h header

Fixed #3683 - allow "configure --disable-maintainer-mode"

Fixed #3686 - fix documentation about sockets blocking on send operations

Fixed #3323 - fix behavior of ZMQ_CONFLATE on PUB sockets

Fixed #3698 - fix build on IBM i/PASE/os400

Fixed #3705 - zero-sized messages cause assertion when glibc assertion are on

Fixed #3713 - remove dependency on math library by avoiding std::ceil

Fixed #3694 - build targeting Windows XP is broken

Fixed #3691 - added support for IPC on Windows 10 via AF_UNIX

Fixed #3725 - disable by default test that requires sudo on CMake

Fixed #3727 - fix zmq_poller documentation example

Fixed #3729 - do not check for FD_OOB when using WSAEventSelect on Windows

Fixed #3738 - allow renaming the library in CMake

Fixed #1808 - use AF_UNIX instead of TCP for the internal socket on Windows 10

Fixed #3758 - fix pthread_set_affinity detection in CMake

Fixed #3769 - fix undefined behaviour in array.hpp

Fixed #3772 - fix compiling under msys2-mingw

Fixed #3775 - add -latomic to the private libs flag in pkg-config if needed

Fixed #3778 - fix documentation of zmq_poller's thread safety

Fixed #3792 - do not allow creation of new sockets after zmq_ctx_shutdown

Fixed #3805 - improve performance of CURVE by reducing copies

Fixed #3814 - send subscribe/cancel as commands to ZMTP 3.1 peers

Fixed #3847 - fix building without PGM and NORM

Fixed #3849 - install .cmake file in arch-dependent subdirectory

Fixed #4005 - allow building on Windows ARM/ARM64

Source code(tar.gz)
Source code(zip)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.3.3.tar.gz(2.01 MB)
zeromq-4.3.3.zip(2.62 MB)
v4.3.2(Jul 8, 2019)
0MQ version 4.3.2 stable, released on 2019/07/08

CVE-2019-13132: a remote, unauthenticated client connecting to a libzmq application, running with a socket listening with CURVE encryption/authentication enabled, may cause a stack overflow and overwrite the stack with arbitrary data, due to a buffer overflow in the library. Users running public servers with the above configuration are highly encouraged to upgrade as soon as possible, as there are no known mitigations. All versions from 4.0.0 and upwards are affected. Thank you Fang-Pen Lin for finding the issue and reporting it!

New DRAFT (see NEWS for 4.2.0) zmq_socket_monitor_versioned API that supports a versioned monitoring events protocol as a parameter. Passing 1 results in the same behaviour as zmq_socket_monitor. Version 2 of the events protocol allows new events, new metadata, different socket types for the monitors and more. It is described in details in doc/zmq_socket_monitor_versioned.txt

New DRAFT (see NEWS for 4.2.0) zmq_socket_monitor_pipes_stats that triggers a new ZMQ_EVENT_PIPES_STATS to be delivered via zmq_socket_monitor_versioned v2 API, which contains the current status of all the queues owned by the monitored socket. See doc/zmq_socket_monitor_versioned.txt for details.

New DRAFT (see NEWS for 4.2.0) zmq_poller_fd that returns the FD of a thread safe socket. See doc/zmq_poller.txt for details.

New DRAFT (see NEWS for 4.2.0) socket options:

ZMQ_XPUB_MANUAL_LAST_VALUE is similar to ZMQ_XPUB_MANUAL but allows to avoid duplicates when using last value caching.

ZMQ_SOCKS_USERNAME and ZMQ_SOCKS_PASSWORD that implement SOCKS5 proxy authentication. See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details.

Implemented background thread names for Windows, when the Visual Studio debugger is being used.

Fixed #3358 - test_security_zap failing due to SIGBUS on SPARC64, hard-coded IPC socket binds in tests cause race conditions

Fixed #3361 - enabling GSSAPI support (when using autools) does not work due to regression introduced in 4.2.3

Fixed #3362 - remove documentation for ZMQ_THREAD_PRIORITY context option getter, it's not implemented

Fixed #3363 - tests fail to build due to stricter compiler printf validation in new versions of GCC

Fixed #3367 - try to infer cacheline size at build time, first with getconf LEVEL1_DCACHE_LINESIZE, and then by reading /sys/devices/system/cpu/cpu0/cache/index0/coherency_line_size (autoconf only), and only then falling back to the previous default of 64 bytes. Avoids false sharing on POWER and s390x. Import ax_func_posix_memalign.m4 as a more reliable check for posix_memalign presence on some unix platforms. Prefer c++11 atomic primitives to compiler intrinsics, when both are available, as the former is more reliable. Set test_pair_ipc and test_rebind_ipc to XFAIL on GNU/Hurd due to non-functioning getsockname on AF_UNIX.

Fixed #3370 - Make queue length and HWM state observable

Fixed #3373 - performance regression in zmq_poll on CentOS 6/7

Fixed #3375 - assign names to all pthreads created by the library to ease debugging

Fixed #3376 - assigned random TIPC port is not returned by ZMQ_LAST_ENDPOINT

Fixed #3385 - TCP port in ZMQ_LAST_ENDPOINT depends on global locale

Fixed #3404 - use std::condition_variable_any when possible

Fixed #3436 - reconnect interval exponential backoff and may lead to integer overflows

Fixed #3440 - improve zmq_proxy performance by batching of up to 1000 consecutive messages (if any) and add perf/proxy_thr tool

Fixed #3451 - fix support of /dev/poll on Solaris

Fixed #3452 - strnlen may not be available

Fixed #1462 - test failure in test_filter_ipc due to invalid system groups

Fixed #3269 - Boost.ASIO integration stopped working with v4.3.0

Fixed #3479 - ZeroMQ does not build for QNX 6.6 with CMake

Fixed #3481 - add include to fix uClibc++ compilation

Fixed #3491 - build broken on Fedora 30

Fixed #3494 - ZeroMQConfig.cmake fails if shared libraries are not built

Fixed #3498 - syntax error on Windows related to socket descriptor type

Fixed #3500 - PLAIN HELLO message incorrectly uses WELCOME literal, regression introduced in 4.3.0

Fixed #3517 - configure errors because of syntax errors in the use of test shell command

Fixed #3521 - document how to achieve high performance with the PGM transport

Fixed #3526 - failure case behavior unclear in zmq_msg_send documentation

Fixed #3537 - fix build on z/OS by using pthread_equal instead of comparing variables directly

Fixed #3546 - CMake links with librt on MinGW which is not available

Many coding style, duplication, testing and static analysis improvements.

Source code(tar.gz)
Source code(zip)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.3.2.tar.gz(1.61 MB)
zeromq-4.3.2.zip(2.37 MB)
v4.3.1(Jan 12, 2019)
0MQ version 4.3.1 stable, released on 2019/01/12

CVE-2019-6250: A vulnerability has been found that would allow attackers to direct a peer to jump to and execute from an address indicated by the attacker. This issue has been present since v4.2.0. Older releases are not affected. NOTE: The attacker needs to know in advance valid addresses in the peer's memory to jump to, so measures like ASLR are effective mitigations. NOTE: this attack can only take place after authentication, so peers behind CURVE/GSSAPI are not vulnerable to unauthenticated attackers. See https://github.com/zeromq/libzmq/issues/3351 for more details. Thanks to Guido Vranken for uncovering the issue and providing the fix!

Note for packagers: as pkg-config's Requires.private is now used to properly propagate dependencies for static builds, the libzmq*-dev or zeromq-devel or equivalent package should now depend on the libfoo-dev or foo-devel packages of all the libraries that zmq is linked against, or pkg-config --libs libzmq will fail due to missing dependencies on end users machines.

Fixed #3351 - remote code execution vulnerability.

Fixed #3343 - race condition in ZMQ_PUSH when quickly disconnecting and reconnecting causes last part of multi-part message to get "stuck" and resent by mistake to the new socket.

Fixed #3336 - set Requires.private in generate pkg-config file.

Fixed #3334 - set TCP_NODELAY after connect() on Windows for the I/O socket.

Fixed #3326 - assert on Android when opening a socket and disabling WiFi.

Fixed #3320 - build failure on OpenBSD with GCC.

Source code(tar.gz)
Source code(zip)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.3.1.tar.gz(1.42 MB)
zeromq-4.3.1.zip(2.16 MB)
v4.3.0(Nov 28, 2018)
0MQ version 4.3.0 stable, released on 2018/11/28

The following DRAFT APIs have been marked as STABLE and will not change anymore:

ZMQ_MSG_T_SIZE context option (see doc/zmq_ctx_get.txt)

ZMQ_THREAD_AFFINITY_CPU_ADD and ZMQ_THREAD_AFFINITY_CPU_REMOVE (Posix only) context options, to add/remove CPUs to the affinity set of the I/O threads. See doc/zmq_ctx_set.txt and doc/zmq_ctx_get.txt for details.

ZMQ_THREAD_NAME_PREFIX (Posix only) context option, to add a specific integer prefix to the background threads names, to easily identify them. See doc/zmq_ctx_set.txt and doc/zmq_ctx_get.txt for details.

ZMQ_GSSAPI_PRINCIPAL_NAMETYPE and ZMQ_GSSAPI_SERVICE_PRINCIPAL_NAMETYPE socket options, for the corresponding GSSAPI features. Additional definitions for principal name types:

ZMQ_GSSAPI_NT_HOSTBASED

ZMQ_GSSAPI_NT_USER_NAME

ZMQ_GSSAPI_NT_KRB5_PRINCIPAL See doc/zmq_gssapi.txt for details.

ZMQ_BINDTODEVICE socket option (Linux only), which will bind the socket(s) to the specified interface. Allows to use Linux VRF, see: https://www.kernel.org/doc/Documentation/networking/vrf.txt NOTE: requires the program to be ran as root OR with CAP_NET_RAW

zmq_timers_* APIs. These functions can be used for cross-platforms timed callbacks. See doc/zmq_timers.txt for details.

The following socket monitor events:

ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL: unknown errors during handshake.

ZMQ_EVENT_HANDSHAKE_SUCCEEDED: Handshake completed with authentication.

ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL: Protocol errors with peers or ZAP.

ZMQ_EVENT_HANDSHAKE_FAILED_AUTH: Failed authentication requests. See doc/zmq_socket_monitor.txt for more details and error codes.

zmq_stopwatch_intermediate which returns the time elapsed without stopping the stopwatch.

zmq_proxy_steerable command 'STATISTICS' to retrieve stats about the amount of messages and bytes sent and received by the proxy. See doc/zmq_proxy_steerable.txt for more information.

The build-time configuration option to select the poller has been split, and new API_POLLER (CMake) and --with-api-poller (autoconf) options will now determine what system call is used to implement the zmq_poll/zmq_poller APIs. The previous POLLER and --with-poller options now only affects the internal I/O thread. In case API_POLLER is not specified, the behaviour keeps backward compatibility intact and will be the same as with previous releases.

The non-default "poll" poller for the internal I/O thread (note: NOT for the zmq_poll/zmq_poller user APIs!) has been disabled on Windows as WSAPoll does not report connection failures. For more information see:

https://daniel.haxx.se/blog/2012/10/10/wsapoll-is-broken/

https://curl.haxx.se/mail/lib-2012-10/0038.html

https://bugs.python.org/issue16507

New epoll implementation for Windows, using the following implementation: https://github.com/piscisaureus/wepoll/tree/v1.5.4 To use this, select "epoll" as the poller option in the build system. Note for distributors: the wepoll source code is embedded and distributed. It is licensed under the BSD-2-Clause and thus it is compatible with LGPL-3.0. Note that, if selected at build time, the license text must be distributed with the binary in accordance to the license terms. A copy can be found at: external/wepoll/license.txt

The pre-made Visual Studio solutions file are deprecated, and users are encouraged to use the CMake solution generation feature instead.

New DRAFT (see NEWS for 4.2.0) socket options:

ZMQ_ROUTER_NOTIFY to deliver a notification when a peer connects and/or disconnects in the form of a routing id plus a zero-length frame.

ZMQ_MULTICAST_LOOP to control whether the data sent should be looped back on local listening sockets for UDP multicast sockets (ZMQ_RADIO). See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details.

New perf tool, perf/benchmark_radix_tree, to measure the performance of the different internal implementations of the trie algorithm used to track subscriptions. Requires a compiler that supports C++11.

New autoconf flag "--enable-force-CXX98-compat" which will force -std=gnu++98 and, if the compiler supports them (clang++ at the moment), it will also add -Wc++98-compat -Wc++98-compat-pedantic so that compatibility with C++98 can be tested.

Many, many coding style, duplication and static analysis improvements.

Many, many improvements to the CMake build system, especially on Windows.

Many, many improvements to unit tests.

Fixed #3036 - Compilation error when -pedantic is used.

Fixed #3028 - Failure when zmq_poller_destroy is called after zmq_ctx_term.

Fixed #2989 - CMake: Linker PDB install rule does not work when Visual Studio generators are used.

Fixed #3045 - configure.ac: search for dladdr only when using libunwind.

Fixed #3060 - REQ sockets terminate TCP connection after first heartbeat if ZMQ_HEARTBEAT_IVL is set.

Fixed #2212 - UDP: need ability to specify bind address separately from multicast address for multi-homed hosts.

Fixed #2891 - UDP: address name resolution is limited to dotted IPv4 rather than being capable of IPv4, IPv6, and hostname lookup.

Fixed #3085 - autoconf/CMake getrandom test does not check if it's working but only for its presence.

Fixed #3090 - compilation broken with Solaris Studio.

Fixed #3094 - UDP: pass interface via IP[V6]_MULTICAST_IF if provided.

Fixed #3061 - implement ZMTP 3.1 ping/pong context sending/receiving.

Fixed #2188 - Added documentation for new zmq_poller API.

Fixed #3088 - zmq_poller_add/zmq_poller_modify should reject invalid events arguments.

Fixed #3042 - Fixed compilation on ARM with ZMQ_ATOMIC_PTR_MUTEX.

Fixed #3107 - test_immediate_3/test_reconnect_inproc do not terminate with POLL as the I/O thread poller under Windows.

Fixed #3046 - Aborts when iOS abuses EBADF to report a socket has been reclaimed.

Fixed #3136 - Cannot set ZMQ_HEARTBEAT_TTL to more than 655.3 seconds.

Fixed #3083 - link with -latomic when needed.

Fixed #3162 - build failure with MUSL libc.

Fixed #3158 - -1 value of ZMQ_RECONNECT_IVL was not correctly handled on some platforms.

Fixed #3170 - improved documentation for ZMQ_PAIR.

Fixed #3168 - correctly use symbols map on Debian/kFreeBSD and Debian/HURD to avoid exporting standard library symbols.

Fixed #3168 - correctly process ZMTP 3.1 cancel/subscribe commands.

Fixed #3171 - improve documentation for ZMQ_CONFLATE.

Fixed #2876 - stack overflow on Windows 64.

Fixed #3191 - race condition with received message causes ZMQ_CONNECT_ROUTING_ID to be assigned to wrong socket.

Fixed #3005 - added documentation for new zmq_timers_* API.

Fixed #3222 - use /Z7 debug on Release builds too on Windows (CMake).

Fixed #3226 - possible PGM receiver crash.

Fixed #3236 - UDP dish socket can't bind to a multicast port already in use.

Fixed #3242 - improve HWM documentation.

Fixed #2488 - improve zmq_msg_send doc return value documentation.

Fixed #3268 - HWM in ZMQ_DGRAM socket does not respect multipart message.

Fixed #3284 - added support for ZMQ_MULTICAST_HOPS with UDP sockets.

Fixed #3245 - use-after-free reported in zmq::pipe_t::terminate.

Fixed #1400 - use patricia trie for subscription to improve performances and memory usage. Note: only active in DRAFT builds for now.

Fixed #3263 - fix abort on Windows when a large TCP read is requested and fails.

Fixed #3312 - fix build on Android Things 1.06 with Termux.

Source code(tar.gz)
Source code(zip)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.3.0.tar.gz(1.41 MB)
zeromq-4.3.0.zip(2.16 MB)
v4.2.5(Mar 23, 2018)
0MQ version 4.2.5 stable, released on 2018/03/23

Fixed #3018 - fix backward-incompatible change in the NULL auth mechanism that slipped in 4.2.3 and made connections with a ZAP domain set on a socket but without a working ZAP handler fail. See ZMQ_ZAP_ENFORCE_DOMAIN and RFC27.

Fixed #3016 - clarify in zmq_close manpage that the operation will complete asynchronously.

Fixed #3012 - fix CMake build problem when using LIBZMQ_WERROR and a compiler other than GCC.

Source code(tar.gz)
Source code(zip)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.2.5.tar.gz(1.34 MB)
zeromq-4.2.5.zip(2.05 MB)
v4.2.4(Mar 21, 2018)
New DRAFT (see NEWS for 4.2.0) socket options:

ZMQ_LOOPBACK_FASTPATH to enable faster TCP loopback on Windows

ZMQ_METADATA to set application-specific metadata on a socket See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details.

New DRAFT (see NEWS for 4.2.0) context options:

ZMQ_ZERO_COPY_RECV to disable zero-copy receive to save memory at the expense of slower performance See doc/zmq_ctx_set.txt and doc/zmq_ctx_get.txt for details.

New DRAFT API zmq_stopwatch_intermediate which returns the time elapsed without stopping the stopwatch.

TIPC: support addressing TIPC Port Identity addresses.

Added CMake option to disable tests: BUILD_TESTS

Added CMake and autotools make targets to support clang-formatter: make clang-format, clang-format-check and clang-format-diff to help developers make sure their code conforms to the style guidelines

For distributors: a new test framework has been added, which includes a copy of the Unity source code. This source code library is distributed under the MIT license and thus is compatible with libzmq's LGPL3.

Fixed #2867 - add ZeroMQConfig.cmake.in to distributable tarball

Fixed #2868 - fix OpenBSD build

Fixed #2870 - fix VC++ 11.0 (VS2012) build

Fixed #2879 - prevent duplicate connections on PUB sockets

Fixed #2872 - fix CMake tests on Windows

Fixed #2895 - fix assert on Windows with POLL

Fixed #2920 - fix Windows build with Intel compiler

Fixed #2930 - use std::atomic when available with VC++ and VS2015

Fixed #2910 - fix race condition with ZMQ_LINGER socket option

Fixed #2927 - add support for ZMQ_XPUB_NODROP on ZMQ_RADIO

Fixed #2820 - further clarify ZMQ_XPUB_VERBOSE(R) documentation.

Fixed #2911 - ZMQ_DISH over UDP triggers errno_assert() after hitting watermark

Fixed #2942 - ZMQ_PUB crash when due to high volume of subscribe and unsubscribe messages, an unmatched unsubscribe message is received in certain conditions

Fixed #2946 - fix Windows CMake build when BUILD_SHARED is off

Fixed #2960 - fix build with GCC 8

Fixed #2967 - fix race condition on thread safe sockets due to pthread condvar timeouts on OSX

Fixed #2977 - fix TIPC build-time availability check to be more relaxed

Fixed #2966 - add support for WindRiver VxWorks 6.x

Fixed #2963 - fix some PVS Studio static analysis warnings

Fixed #2983 - fix MinGW cross-compilation

Fixed #2991 - fix mutex assert at shutdown when the zmq context is part of a class declared as a global static

Source code(tar.gz)
Source code(zip)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.2.4.tar.gz(1.33 MB)
zeromq-4.2.4.zip(2.05 MB)
v4.2.3(Dec 13, 2017)
0MQ version 4.2.3 stable, released on 2017/12/13

API change: previously ZMQ_POLLOUT on a ZMQ_ROUTER socket returned always true due to how the type works. When ZMQ_ROUTER_MANDATORY is set, sending fails when the peer is not available, but ZMQ_POLLOUT always returns true anyway, which does not make sense. Now when ZMQ_ROUTER_MANDATORY is set, ZMQ_POLLOUT on a ZMQ_ROUTER will return true only if at least one peer is available. Given ZMQ_POLLOUT with ZMQ_ROUTER was not usable at all previously, we do not consider this a breakage warranting a major or minor version increase.

ZMQ_IDENTITY has been renamed to ZMQ_ROUTING_ID and ZMQ_CONNECT_RID has been renamed to ZMQ_CONNTECT_ROUTING_ID to disambiguate. ZMQ_IDENTITY and ZMQ_CONNECT_RID are still available to keep backward compatibility, and will be removed in a future release after further advance notice.

DRAFT API change: zmq_poller_wait, zmq_poller_wait_all and zmq_poller_poll have been changed to be inline with other existing APIs that have a timeout to return EAGAIN instead of ETIMEDOUT as the errno value. See #2713 for details.

Existing non-DRAFT socket types ZMQ_REP/REQ, ZMQ_ROUTER/DEALER and ZMQPUB/SUB, that were previously declared deprecated, have been reinstated as stable and supported. See #2699 for details.

Tweetnacl: add support for, and use preferably if available, getrandom() as a simpler and less error-prone alternative to /dev/urandom on OSes where it is available (eg: Linux 3.18 with glibc 2.25).

Curve: all remaining traces of debug output to console are now removed, and new DRAFT events are available to properly debug CURVE, PLAIN, GSSAPI and ZAP events and failures. See below for details on the new events.

New DRAFT (see NEWS for 4.2.0) socket options:

ZMQ_GSSAPI_PRINCIPAL_NAMETYPE and ZMQ_GSSAPI_SERVICE_PRINCIPAL_NAMETYPE, for the corresponding GSSAPI features. Additional definitions for principal name types:

ZMQ_GSSAPI_NT_HOSTBASED

ZMQ_GSSAPI_NT_USER_NAME

ZMQ_GSSAPI_NT_KRB5_PRINCIPAL See doc/zmq_gssapi.txt for details.

ZMQ_BINDTODEVICE (Linux only), which will bind the socket(s) to the specified interface. Allows to use Linux VRF, see: https://www.kernel.org/doc/Documentation/networking/vrf.txt NOTE: requires the program to be ran as root OR with CAP_NET_RAW

ZMQ_ZAP_ENFORCE_DOMAIN, enables strict RFC 27 compatibility mode and makes the ZAP Domain mandatory when using security. See: https://rfc.zeromq.org/spec:27/ZAP See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details.

New DRAFT (see NEWS for 4.2.0) context options:

ZMQ_THREAD_AFFINITY_CPU_ADD and ZMQ_THREAD_AFFINITY_CPU_REMOVE (Posix only), to add and remove CPUs to the affinity set of the I/O threads. Useful to pin the background threads to specific CPUs.

ZMQ_THREAD_NAME_PREFIX (Posix only), to add a specific integer prefix to the background threads names, to easily identify them for debugging purposes. See doc/zmq_ctx_set.txt and doc/zmq_ctx_get.txt for details.

New DRAFT (see NEWS for 4.2.0) message property name definitions to facilitate the use of zmq_msg_gets:

ZMQ_MSG_PROPERTY_ROUTING_ID

ZMQ_MSG_PROPERTY_SOCKET_TYPE

ZMQ_MSG_PROPERTY_USER_ID

ZMQ_MSG_PROPERTY_PEER_ADDRESS See doc/zmq_msg_gets.txt for details.

New DRAFT (see NEWS for 4.2.0) API zmq_socket_get_peer_state, to be used to query the state of a specific peer (via routing-id) of a ZMQ_ROUTER socket.

New DRAFT (see NEWS for 4.2.0) Socket Monitor events:

ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL, unknown system error and returns errno

ZMQ_EVENT_HANDSHAKE_SUCCEEDED, handshake was successful

ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL, protocol errors between peers or server and ZAP handler. Returns one of ZMQ_PROTOCOL_ERROR_* - see manpage for list

ZMQ_EVENT_HANDSHAKE_FAILED_AUTH, failed authentication, returns ZAP status These events trigger when the ZMTP security mechanism handshake is completed or failed. See doc/zmq_socket_monitor.txt for more information.

New DRAFT (see NEWS for 4.2.0) zmq_proxy_steerable command 'STATISTICS' to retrieve stats about the amount of messages and bytes sent and received by the proxy. See doc/zmq_proxy_steerable.txt for more information.

Add new autoconf --disable-libunwind option to stop building with libunwind even if it is available.

Add new autoconf --disable-Werror option to avoid building with the Werror flag.

Use pkg-config as the first method for finding and building with external optional dependencies such as libnorm, libpgm and gssapi.

On Posix platform where the feature is available, name the ZMQ background threads to simplify debugging: "ZMQbg/<num_thread>"

Improve performance of zmq_poller_* (and zmq_poll and zmq_proxy when building with DRAFT APIs enabled).

The TCP unit tests have been refactored to bind and connect to random ports rather than hard-coded ones, to allow running tests in parallel. There are 6 exceptions where it is necessary to use an hard-coded port to test specific code paths that would not be exercised when binding to a wildcard port. These are listed in tests/testutil.hpp so that distributions can easily patch them if they wish to and so that they can be unique across all the tests, allowing parallel runs. The IPC unit tests have been changed as well to use unique socket file names per test, where before there were some clashes.

Fixed #2349 - fix building with libsodium when using CMake

Fixed #2334 - do not assert when tuning socket options fails due to network errors, but simply retry again when connecting or send a socket monitor ZMQ_EVENT_ACCEPT_FAILED event when binding

Fixed #2341 - fix source files path in VS2015 solution

Fixed #2344 - Note that on Windows with VS2012 it is mandatory to increase the default stack size to at least 2MB

Fixed #2348 - ZMQ_ROUTER send with ZMQ_ROUTER_MANDATORY can be stuck in case of network problem

Fixed #2358 - occasional abort on zmq_connect on Windows

Fixed #2370 - zmq_curve_keypair should return an error on failure rather than ignoring them and always returning 0

Fixed #2452 - __STDC_LIMIT_MACROS before precompiled headers causes VC++ warning

Fixed #2457 - fix building with libsodium in Visual Studio solutions

Fixed #2466 - add const qualifier to internal and public API that does not modify parameters

Fixed #2471 - do more checks for OOM conditions when dynamic allocations is used

Fixed #2476 - assertion causes abort after ZAP stop at shutdown

Fixed #2479 - improve zmq_poller performance on Windows

Fixed #2481 - potential memory leaks due to ZMTP handshake failures

Fixed #2531 - ZMQ_GSSAPI_PRINCIPAL sockopt has no effect on client side

Fixed #2535 - add BUILD_SHARED and BUILD_STATIC options to CMake, both on by default, to toggle shared and static library builds

Fixed #2537 - use SYSTEM_CLOCK on OSX and CLOCK_MONOTONIC elsewhere for internal timers to avoid races

Fixed #2540 - new zmq_poller used by zmq_poll without DRAFTs

Fixed #2552 - Fix WITH_DOC CMake build to avoid checking for asciidoc if the option is disabled

Fixed #2567 - Memory leak in REP socket handling

Fixed #2579 - Compilation issue on Windows with CMake + ninja

Fixed #2588 - SIGBUS under 64-bit SunOS Sparc

Fixed #2590 - crash when using ZMQ_IMMEDIATE and ZMQ_LINGER to non-zero

Fixed #2601 - XPUB_MANUAL subscriptions not removed on peer term

Fixed #2602 - intermittent memory leak for ZMQ_REQ/REP send/recv

Fixed #2608 - CURVE server (connect) fails when client rebinds

Fixed #2610 - print backtraces in mutual exclusion to avoid mixing different traces

Fixed #2621 - add missing CMake files to distributable tarball

Fixed #2630 - improve compatibility with OpenBSD w.r.t. IPV6_V6ONLY

Fixed #2638 - note in INSTALL that when using Windows builds on Linux with Wine it is necessary to increase the minimum TCP buffers

Fixed #2632 - Fix file descriptor leak when using Tweetnacl (internal NACL implementation) instead of Libsodium, and fix race condition when using multiple ZMQ contexts with Tweetnacl

Fixed #2681 - Possible buffer overflow in CURVE mechanism handshake. NOTE: this was protected by an assert previously, so there is no security risk.

Fixed #2704 - test_sockopt_hwm fails occasionally on Windows

Fixed #2701 - pgm build via cmake doesn't link libzmq with libpgm

Fixed #2711 - ZAP handler communication errors should be handled consistently

Fixed #2723 - assertion in src\select.cpp:111 or hang on zmq_ctx_destroy on Windows

Fixed #2728 - fix support O_CLOEXEC when building with CMake

Fixed #2761 - improve compatibility with TrueOS (FreeBSD 12)

Fixed #2764 - do not unlink IPC socket files when closing a socket to avoid race conditions

Fixed #2770 - support lcov 1.13 and newer

Fixed #2787 - add libiphlpapi to PKGCFG_LIBS_PRIVATE for static mingw builds

Fixed #2788 - document that adding -DZMQ_STATIC is required for Windows static builds with Mingw

Fixed #2789 - description of zmq_atomic_counter_value return value is cloned from zmq_atomic_counter_new

Fixed #2791 - fix building with DRAFT APIs on CentOS 6

Fixed #2794 - router_t methods should not allocate memory for lookup in outpipes

Fixed #2809 - optimize select() usage on Windows

Fixed #2816 - add CMake and autoconf check for accept4, as it is not available on old Linux releases, and fallback to accept + FD_CLOEXEC

Fixed #2824 - ZMQ_REQ socket does not report ZMQ_POLLOUT when ZMQ_REQ_RELAXED is set

Fixed #2827 - add support for Haiku

Fixed #2840 - fix building with VS2008

Fixed #2845 - correct the ZMQ_LINGER documentation to accurately reflect that the default value is -1 (infinite). It never was 30 second in any released version, it was only changed briefly and then changed back, but the manpage was not reverted.

Fixed #2861 - CMake/MSVC: export ZMQ_STATIC when needed.

Source code(tar.gz)
Source code(zip)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.2.3.tar.gz(1.26 MB)
zeromq-4.2.3.zip(1.97 MB)
v4.2.2(Feb 18, 2017)
0MQ version 4.2.2 stable, released on 2017/02/18

Improve compatibility with GNU Hurd

Fixed #2286 - improve CMake on Windows documentation

Fixed #1235 - improved compatibility with mingw64

Improve zmq_proxy documentation to state it can return ETERM as well

Fixed #1442 - SO_NOSIGPIPE and connection closing by peer race condition

Improve CMake functionality on Windows: ZeroMQConfig.cmake generation CPack option, correct static library filename, ship FindSodium.cmake in tarball

Fixed #2228 - setting HWM after connect on inproc transport leads to infinite HWM

Add support for Visual Studio 2017

New DRAFT (see NEWS for 4.2.0) zmq_has option "draft" option that returns true if the library was built with DRAFT enabled. Useful for FFI bindings. See doc/zmq_has.txt for more information

Fixed #2321 - zmq_z85_decode does not validate its input. The function has been fixed to correctly follow RFC32 and return NULL if the input is invalid

Fixed #2323 - clock_t related crash on Apple iOS 9.3.2 and 9.3.5

Fixed #1801 - OSX: Cmake installs libzmq in a weird PATH

Fixed potential divide by zero in zmq::lb_t::sendpipe

Improve compatibility with OpenIndiana by skipping epoll and using poll/select

Fix IPv4-in-IPv6 mapped addresses parsing error

Source code(tar.gz)
Source code(zip)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.2.2.tar.gz(1.17 MB)
zeromq-4.2.2.zip(1.88 MB)
v4.2.1(Dec 31, 2016)
0MQ version 4.2.1 stable, released on 2016/12/31

New DRAFT (see NEWS for 4.2.0) Socket Monitor events:

ZMQ_EVENT_HANDSHAKE_SUCCEED

ZMQ_EVENT_HANDSHAKE_FAILED These events trigger when the ZMTP security mechanism handshake is completed. See doc/zmq_socket_monitor.txt for more information.

New DRAFT (see NEWS for 4.2.0) Context options:

ZMQ_MSG_T_SIZE See doc/zmq_ctx_get.txt for more information.

Fixed #2268 - improved compatibility with mingw32

Fixed #2254 - ZMQ_PUB compatibility with libzmq 2.x broken

Fixed #2245 - added support for VS2017, Windows SDK 10.0.14393.0, toolset v141

Fixed #2242 - file descriptors leaks on fork+exec

Fixed #2239 - retired poller item crash from reaper thread

Fixed #2234 - improved compatibility with AIX 7.1

Fixed #2225 - cannot pick select for poller

Fixed #2217 - CMake build uses library version as the ABI version

Fixed #2208 - added support for ZMQ_TOS on IPv6

Fixed #2200 - no documentation for ZMQ_SOCKS_PROXY

Fixed #2199 - no documentation for zmq_curve_public

Fixed #2196 - fixed build and runtime errors on kFreeBSD

Source code(tar.gz)
Source code(zip)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.2.1.tar.gz(1.18 MB)
zeromq-4.2.1.zip(1.89 MB)
v4.2.0(Nov 4, 2016)
0MQ version 4.2.0 stable, released on 2016/11/04

For Pieter. Thanks for making all of this possible.

"Tell them I was a writer. A maker of software. A humanist. A father. And many things. But above all, a writer. Thank You. :)"

Pieter Hintjens

This release introduces new APIs, but it is ABI compatible with libzmq 4.1.2 and up.

Note for ARM and SPARC users: an alignment problem in zmq_msg_t that could in some cases and on some CPUs cause a SIGBUS error was solved, but it requires a rebuild of your application against the 4.2.0 version of include/zmq.h. To clarify, this change does not affect the internals of the library but only the public definition of zmq_msg_t, so there is no ABI incompatibility.

Security with Curve is now available by default thanks to Tweetnacl sources: https://tweetnacl.cr.yp.to/index.html Libsodium is still fully supported but has to be enabled with the build flag --with-libsodium. Distribution and package maintainers are encouraged to use libsodium so that the security implementation can be audited and maintained separately.

New Context options:

ZMQ_MAX_MSGSZ

ZMQ_BLOCKY

See doc/zmq_ctx_set.txt and doc/zmq_ctx_get.txt for details.

New Socket options:

ZMQ_HANDSHAKE_IVL

ZMQ_SOCKS_PROXY

ZMQ_XPUB_NODROP

ZMQ_XPUB_MANUAL

ZMQ_XPUB_WELCOME_MSG

ZMQ_STREAM_NOTIFY

ZMQ_INVERT_MATCHING

ZMQ_HEARTBEAT_IVL

ZMQ_HEARTBEAT_TTL

ZMQ_HEARTBEAT_TIMEOUT

ZMQ_XPUB_VERBOSER

ZMQ_CONNECT_TIMEOUT

ZMQ_TCP_MAXRT

ZMQ_THREAD_SAFE

ZMQ_MULTICAST_MAXTPDU

ZMQ_VMCI_BUFFER_SIZE

ZMQ_VMCI_BUFFER_MIN_SIZE

ZMQ_VMCI_BUFFER_MAX_SIZE

ZMQ_VMCI_CONNECT_TIMEOUT

ZMQ_USE_FD

See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details.

New CURVE helper function to derive z85 public key from secret key: zmq_curve_public

New cross-platform atomic counter helper functions: zmq_atomic_counter_new, zmq_atomic_counter_set, zmq_atomic_counter_inc, zmq_atomic_counter_dec, zmq_atomic_counter_value, zmq_atomic_counter_destroy See doc/zmq_atomic_*.txt for details.

New DRAFT APIs early-release mechanism. New APIs will be introduced early in public releases, and until they are stabilized and guaranteed not to change anymore they will be unavailable unless the new build flag --enable-drafts is used. This will allow developers and early adopters to test new APIs before they are finalized. NOTE: as the name implies, NO GUARANTEE is made on the stability of these APIs. They might change or disappear entirely. Distributions are recommended NOT to build with them.

New socket types have been introduced in DRAFT state: ZMQ_SERVER, ZMQ_CLIENT, ZMQ_RADIO, ZMQ_DISH, ZMQ_GATHER, ZMQ_SCATTER, ZMQ_DGRAM All these sockets are THREAD SAFE, unlike the existing socket types. They do NOT support multipart messages (ZMQ_SNDMORE/ZMQ_RCVMORE). ZMQ_RADIO, ZMQ_DISH and ZMQ_DGRAM also support UDP as transport, both unicast and multicast. See doc/zmq_udp.txt for more details. New methods to support the new socket types functionality: zmq_join, zmq_leave, zmq_msg_set_routing_id, zmq_msg_routing_id, zmq_msg_set_group, zmq_msg_group See doc/zmq_socket.txt for more details.

New poller mechanism and APIs have been introduced in DRAFT state: zmq_poller_new, zmq_poller_destroy, zmq_poller_add, zmq_poller_modify, zmq_poller_remove, zmq_poller_wait, zmq_poller_wait_all, zmq_poller_add_fd zmq_poller_modify_fd, zmq_poller_remove_fd and a new supporting struct typedef: zmq_poller_event_t They support existing socket type, new thread-safe socket types and file descriptors (cross-platform). Documentation will be made available in the future before these APIs are declared stable.

New cross-platform timers helper functions have been introduced in DRAFT state: zmq_timers_new, zmq_timers_destroy, zmq_timers_add, zmq_timers_cancel, zmq_timers_set_interval, zmq_timers_reset, zmq_timers_timeout, zmq_timers_execute and a new supporting callback typedef: zmq_timer_fn

Many, many bug fixes. The most important fixes are backported and captured in the 4.1.x and 4.0.x changelogs.

0MQ version 4.2.0 rc1, released on 2016/11/01

Many changes, see ChangeLog.

0MQ version 4.1.6 stable, released on 2016/11/01

Fixed #2051 - getifaddrs can fail with ECONNREFUSED

Fixed #2091 - testutil.hpp fails to build on Windows XP

Fixed #2096 - add tests/CMakeLists.in and version.rc.in to dist tar

Fixed #2107 - zmq_connect with IPv6 "source:port;dest:port" broken

Fixed #2117 - ctx_term assert with inproc zmq_router connect-before-bind

Fixed #2158 - Socket monitor uses internal Pair from multiple threads

Fixed #2161 - messages dropped due to HWM race

Fixed #1325 - alignment issue with zmq_msg_t causes SIGBUS on SPARC and ARM

0MQ version 4.1.5 stable, released on 2016/06/17

Fixed #1673 - CMake on Windows put PDB in wrong directory.

Fixed #1723 - Family is not set when resolving NIC on Android.

Fixed #1608 - Windows 7 TCP slow start issue.

Fixed #1806 - uninitialised read in curve getsockopt.

Fixed #1807 - build broken with GCC 6.

Fixed #1831 - potential assertion failure with latest libsodium.

Fixed #1850 - detection issues with tweetnacl/libsodium.

Fixed #1877 - Avoid terminating connections prematurely

Fixed #1887 - zmq_bind IPv4 fallback still tries IPv6

Fixed #1866 - fails to build on SunOS 5.10 / Solaris 10

Fixed #919 - ZMQ_LINGER (related to #1877)

Fixed #114 - cannot unbind with same endpoint with IPv6 enabled.

Fixed #1952 - CMake scripts not part of release tarballs

Fixed #1542 - Fix a crash on Windows when port 5905 is in use.

Fixed #2021 - Fix building on sparc32.

0MQ version 4.1.4 stable, released on 2015/12/18

Fixed #1315 - socket monitor hangs if bind/setsockopt failed.

Fixed #1399 - assertion failure in tcp.cpp after network reconnect.

Fixed #1632 - build failure using latest libsodium.

Fixed #1644 - assertion failure in msg.cpp:390 on STREAM sockets.

Fixed #1661 - does not handle IPv6 link local addresses.

0MQ version 4.1.3 stable, released on 2015/08/17

Fixed #1532 - getsockopt ZMQ_RCVMORE now resets all bits instead of only 32

Fixed #1445 - zmq::socket_base_t::connect fails on tcp ipv6 address

0MQ version 4.1.2 stable, released on 2015/06/15

Added explicit reference to static link exception in every source file.

Bumped ABI version to 5:0:0 since 4.1.x changed the ABI.

Fixed STDINT event interface macros to work with CZMQ 3.0.

Fixed installation of man pages when BUILD_DOC is not set.

Fixed #1428 - regression on single-socket proxies.

0MQ version 4.1.1 stable, released on 2015/06/02

Fixed #1208 - fix recursion in automake packaging.

Fixed #1224 - crash when processing empty unsubscribe message.

Fixed #1213 - properties files were missing from source packages.

Fixed #1273 - V3 protocol handler vulnerable to downgrade attacks.

Fixed #1347 - lack way to get peer address.

Fixed #1362 - SUB socket sometimes fails to resubscribe properly.

Fixed #1377, #1144 - failed with WSANOTINITIALISED in some cases.

Fixed #1389 - PUB, PUSH sockets had slow memory leak.

Fixed #1382 - zmq_proxy did not terminate if there were no readers.

0MQ version 4.1.0 rc1, released on 2014/10/14

All issues that were fixed in 4.0.x

Improved client reconnection strategy on errors

GSSAPI security mechanism

SOCKS5 support (ZMQ_SOCKS_PROXY)

ZMQ_ROUTER_HANDOVER

ZMQ_TOS

ZMQ_CONNECT_RID

ZMQ_HANDSHAKE_IVL

ZMQ_IDENTITY_FD

ZMQ_XPUB_NODROP

ZMQ_SRCFD and ZMQ_SHARED message options

Message metadata -- zmq_msg_gets ()

Probe library configuration -- zmq_has ()

0MQ version 4.0.8 stable, released on 2016/06/17

Fixed LIBZMQ-949 - zmq_unbind fails for inproc and wildcard endpoints

Fixed #1806 - uninitialised read in curve getsockopt.

Fixed #1807 - build broken with GCC 6.

Fixed #1877 - Avoid terminating connections prematurely

Fixed #1887 - zmq_bind IPv4 fallback still tries IPv6

Fixed #98 - don't require libssp without libsodium on Solaris

Fixed #919 - ZMQ_LINGER (related to #1877)

Fixed #139 - "tempnam" is deprecated.

0MQ version 4.0.7 stable, released on 2015/06/15

Fixed #1428 - regression on single-socket proxies.

0MQ version 4.0.6 stable, released on 2015/06/02

Fixed #1273 - V3 protocol handler vulnerable to downgrade attacks.

Fixed #1362 - SUB socket sometimes fails to resubscribe properly.

Fixed #1377, #1144 - failed with WSANOTINITIALISED in some cases.

Fixed #1389 - PUB, PUSH sockets had slow memory leak.

Fixed #1382 - zmq_proxy did not terminate if there were no readers.

Source code(tar.gz)
Source code(zip)
MD5SUMS(105 bytes)
SHA1SUMS(121 bytes)
zeromq-4.2.0.tar.gz(1021.73 KB)
zeromq-4.2.0.zip(1.45 MB)
v4.2.0-rc1(Nov 1, 2016)

This is the first Release Candidate of libzmq 4.2.0. Go forth and test!

If there are no reports of breakages, the stable 4.2.0 will be tagged and get proper release notes.
Source code(tar.gz)
Source code(zip)
MD5SUMS(113 bytes)
SHA1SUMS(129 bytes)
zeromq-4.2.0-rc1.tar.gz(1016.24 KB)
zeromq-4.2.0-rc1.zip(1.44 MB)

ZeroMQ core engine in C++, implements ZMTP/3.1

Related tags

Overview

ZeroMQ

Welcome

Supported platforms

Supported platforms with primary CI

Supported platforms with secondary CI

Supported platforms with known active users

Supported platforms without known active users

Unsupported platforms

Installation of binary packages

Linux

Latest releases

DEB

RPM

Bleeding edge packages

DEB

RPM

Example: Debian 9 latest release, no DRAFT apis

OSX

Build from sources

Android

Resources

License

Contributing

Comments

Environment

Reproduction

Issue description

Environment

Minimal test code / Steps to reproduce the issue

What's the actual result? (include assertion message & call stack if applicable)

What's the expected result?

Issue description

Environment

Minimal test code / Steps to reproduce the issue

What's the actual result? (include assertion message & call stack if applicable)

What's the expected result?

Issue description

Environment

What's the actual result? (include assertion message & call stack if applicable)

What's the expected result?

Environment

How to reproduce

Issue description

Environment

Minimal test code / Steps to reproduce the issue

What's the actual result? (include assertion message & call stack if applicable)

What's the expected result?

Issue description

Environment

Minimal test code / Steps to reproduce the issue

What's the actual result? (include assertion message & call stack if applicable)

What's the expected result?

Issue description

Environment

Minimal test code / Steps to reproduce the issue

What's the actual result? (include assertion message & call stack if applicable)

What's the expected result?

Issue description

Environment

Issue description

Environment

Minimal test code / Steps to reproduce the issue

What's the actual result? (include assertion message & call stack if applicable)

What's the expected result?

how was this noticed?

Releases(v4.3.4)

v4.3.4(Jan 17, 2021)

0MQ version 4.3.4 stable, released on 2021/01/17

v4.3.3(Sep 7, 2020)

0MQ version 4.3.3 stable, released on 2020/09/07

v4.3.2(Jul 8, 2019)

0MQ version 4.3.2 stable, released on 2019/07/08

v4.3.1(Jan 12, 2019)

0MQ version 4.3.1 stable, released on 2019/01/12

v4.3.0(Nov 28, 2018)

0MQ version 4.3.0 stable, released on 2018/11/28

v4.2.5(Mar 23, 2018)