[zeromq-dev] Message queuing broker for mobile device

[Gang Liu]

You are right. TCP keep alive works now.


regards,
Gang

On Mon, Jan 12, 2015 at 6:12 PM, Pieter Hintjens <ph at 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.lau at gmail.com> wrote:
>> I already tried this way(set
>> ZMQ_TCP_KEEPALIVE/ZMQ_TCP_KEEPALIVE_CNT/ZMQ_TCP_KEEPALIVE_IDLE/ZMQ_TCP_KEEPALIVE_INTVL
>>  at broker front end zsock), it seems these setting don't apply to new
>> incoming connection. I will try again.
>>
>> regards,
>> Gang
>>
>> On Mon, Jan 12, 2015 at 5:57 PM, Pieter Hintjens <ph at 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.lau at gmail.com> wrote:
>>>> After some tracing, I found this case could be repeated when client
>>>> socket in connected state and I power off Wi-Fi router
>>>>  or turn off mobile device 3G DATA signal before zmq client do disconnect.
>>>>
>>>> Is there any way to enable broker's low level client TCP sockets
>>>> KEEP_ALIVE option? I try to setopt at broker front end zsock,
>>>> but don't help much. Yes, I am still thinking in BSD socket way. or do
>>>> I need chose another zeromq pattern to handle clients no reliable inet
>>>> connection?
>>>>
>>>> thanks for your kindly.
>>>>
>>>> regards,
>>>> Gang
>>>>
>>>>
>>>>
>>>> On Mon, Jan 12, 2015 at 5:30 PM, Pieter Hintjens <ph at imatix.com> wrote:
>>>>> These sockets are managed automatically by TCP.
>>>>>
>>>>> On Mon, Jan 12, 2015 at 7:41 AM, Gang Liu <gangban.lau at 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.
>>>>>>             In my testing code, the mobile client is using ZMQ_DEALER
>>>>>> socket to connect to this broker. But after some time, I found there
>>>>>> are more and more connected TCP at  broker server side, all in
>>>>>> ESTABLISHED state. I am sure there are no more than ten clients and
>>>>>> even all apps in closed state.
>>>>>>             Because there are no way to get low level TCP sockets of
>>>>>> broker, so is there any way to clean those "DEAD" TCP connections when
>>>>>> clients at WI-FI or 3G env?
>>>>>>
>>>>>> regards,
>>>>>> Gang
>>>>>> _______________________________________________
>>>>>> zeromq-dev mailing list
>>>>>> zeromq-dev at lists.zeromq.org
>>>>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>>>> _______________________________________________
>>>>> zeromq-dev mailing list
>>>>> zeromq-dev at lists.zeromq.org
>>>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>>> _______________________________________________
>>>> zeromq-dev mailing list
>>>> zeromq-dev at lists.zeromq.org
>>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>> _______________________________________________
>>> zeromq-dev mailing list
>>> zeromq-dev at lists.zeromq.org
>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev