XREP+XREP identity issue

[miasscerber]

I connect XREP to XREP. Both of them have identities to let me route messages.
The issue is that socket that binds does not use specified identity, but uses generated UUID.

#include "zhelpers.h"

int main () {
    void *context = zmq_init (1);

    void *worker = zmq_socket (context, ZMQ_XREP);
    zmq_setsockopt (worker, ZMQ_IDENTITY, "worker", 6);
    zmq_bind (worker, "inproc://routing");

    void *server = zmq_socket (context, ZMQ_XREP);
    zmq_setsockopt (server, ZMQ_IDENTITY, "server", 6);
    zmq_connect (server, "inproc://routing");

    s_sendmore (worker, "server");
    s_sendmore (worker, "");
    s_send     (worker, "workload");

    // server gets worker UUID instead of "worker", delimiter, and workload
    // we could remember workers UUID and use it to send messages to it
    s_dump (server);

    zmq_term (context);
    return 0;
}

[hintjens]

Problem confirmed on 2.0.9, maint, and master branches.

[hintjens]

More detail on this issue:

• It only fails with the inproc: transport, ipc and tcp work
• Using tcp or ipc, the program must pause before sending the first message since the identity is not otherwise correctly set-up

See test case at http://gist.github.com/593867.

• Changing endpoint to inproc, and it produces wrong incoming identity.
• Remove sleep(1) and it drops message (wrong outgoing identity).
• Remove sleep(1) and change endpoint to inproc, and it produces wrong incoming identity.

[sustrik]

Ack. Inproc transport doesn't exchange identities. Instead UUIDs are generated. Should be fixed.

[metasync]

I encountered the same issue in 2.1.1 (RC1). Any idea when this issue is going to fix? Thanks a lot!

[sustrik]

Fixed in master (4c74462).

[metasync]

oh, great! thanks a lot sustrik for the quick update! will try out the master branch.