I was implemented a simple request-reply architecture with a router using ZeroMQ. This works correctly for PyZMQ version 2.1.11. Unfortunately, when I test it on PyZMQ version 14.0.0, sender (REQ) can send to the router then router received its message and send to receiver (REP) but the receiver does not receive the message! I encounter to this problem when I upgraded PyZMQ from version 2.1.11 to 14.0.0.
REQ <-> ROUTER <-> REP
Here is my code:
sender.py
import zmq
import time
if __name__=='__main__':
context = zmq.Context()
socket = context.socket(zmq.REQ)
socket.setsockopt(zmq.IDENTITY, "S")
socket.connect("tcp://127.0.0.1:6660")
i = 0
while True:
i += 1
socket.send("R", zmq.SNDMORE)
socket.send("", zmq.SNDMORE)
socket.send("Message: %d" % i)
print("Message : %d sent" % i)
fromAddr = socket.recv()
empty = socket.recv()
resp = socket.recv()
print("%s received!" % str(resp))
time.sleep(1)
router.py
import zmq
import time
if __name__=='__main__':
context = zmq.Context()
frontend = context.socket(zmq.ROUTER)
frontend.bind("tcp://*:6660")
poll = zmq.Poller()
poll.register(frontend, zmq.POLLIN)
while True:
sockets = dict(poll.poll(100))
if frontend in sockets:
if sockets[frontend] == zmq.POLLIN:
fromAddr = frontend.recv()
empty = frontend.recv()
toAddr = frontend.recv()
empty = frontend.recv()
msg = frontend.recv()
print("Message received from %s must be send to %s [%s]" % (str$
frontend.send(toAddr, zmq.SNDMORE)
frontend.send("", zmq.SNDMORE)
frontend.send(fromAddr, zmq.SNDMORE)
frontend.send("", zmq.SNDMORE)
frontend.send(msg)
print("Message has been send to %s!" % str(toAddr))
receiver.py
import zmq
import time
if __name__=='__main__':
context = zmq.Context()
socket = context.socket(zmq.REP)
socket.setsockopt(zmq.IDENTITY, "R")
socket.connect("tcp://127.0.0.1:6660")
while True:
print("Wating for request...")
toAddr = socket.recv()
empty = socket.recv()
req = socket.recv()
print("%s received!" % str(req))
socket.send(toAddr, zmq.SNDMORE)
socket.send(empty, zmq.SNDMORE)
socket.send("Reply to %s" % str(req))
When I use this architecture:
The DEALER
does not route to multiple receivers. DEALER
only use round-robin method for sending messages to receivers. If ROUTER
could be used instead of DEALER
, then messages could be routed to specific receivers and will do round-robin between those.
ZeroMQ patterns are implemented by pairs of sockets with matching types. The built-in core ZeroMQ patterns are: Request-reply, which connects a set of clients to a set of services. This is a remote procedure call and task distribution pattern.
ZeroMQ sockets carry messages, like UDP, rather than a stream of bytes as TCP does. A ZeroMQ message is length-specified binary data.
ZeroMQ is an asynchronous network messaging library known for its high performance. It's intended use is for distributed systems as well as concurrent systems. In summary, ZMQ allows you to send messages (binary data, serialized data, simple strings, etc.)
Contexts help manage any sockets that are created as well as the number of threads ZeroMQ uses behind the scenes. Create one when you initialize a process and destroy it as the process is terminated. Contexts can be shared between threads and, in fact, are the only ZeroMQ objects that can safely do this.
A ROUTER to REP socket is an invalid combination as explained here: http://zguide.zeromq.org/page:all#Request-Reply-Combinations
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With