yes. It is ok when set TCP_KEEP_ALIVE settings before connect endpoint.
regards,
Gang
On Wed, Jan 28, 2015 at 10:04 PM, Kenneth Adam Miller
kennethadammil...@gmail.com wrote:
Hello,
Did you ever get this resolved?
On Thu, Jan 8, 2015 at 10:29 PM, Gang Liu gangban@gmail.com wrote
You are right. TCP keep alive works now.
regards,
Gang
On Mon, Jan 12, 2015 at 6:12 PM, Pieter Hintjens p...@imatix.com wrote:
You must set these before doing a bind or connect.
On Mon, Jan 12, 2015 at 11:07 AM, Gang Liu gangban@gmail.com wrote:
I already tried this way(set
:
These sockets are managed automatically by TCP.
On Mon, Jan 12, 2015 at 7:41 AM, Gang Liu gangban@gmail.com wrote:
Dear all,
I am new to zeromq. I have a question about message
queuing broker (msgqueue.c) which use zmq_proxy() forward msgs between
frontend and backend
...@imatix.com wrote:
You can change the TCP socket keep alive setting, yes. See
http://api.zeromq.org/4-2:zmq-setsockopt#toc42
On Mon, Jan 12, 2015 at 10:43 AM, Gang Liu gangban@gmail.com wrote:
After some tracing, I found this case could be repeated when client
socket in connected state and I
Dear all,
I am new to zeromq. I have a question about message
queuing broker (msgqueue.c) which use zmq_proxy() forward msgs between
frontend and backend.
In my testing code, the mobile client is using ZMQ_DEALER
socket to connect to this broker. But after some time, I
Dear all,
I am new to zeromq. I have some questions about message queuing
broker (msgqueue.c) which use zmq_proxy() forward msgs between frontend and
backend.
In my testing code, the mobile client is using ZMQ_DEALER
socket to connect to this broker. But after some time, I
