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 wrote:
>
>> Dear all,
>>
Hi,
Sorry, I didn't have time to retest it properly. Just close it and I
will reopen it if I can reproduce it against the latest master.
Thanks,
Tomas
On 01/28/2015 10:00 PM, zeromq-dev-requ...@lists.zeromq.org wrote:
> Date: Tue, 27 Jan 2015 11:46:19 -0600
> From: Thomas Rodgers
> Subject: Re:
It's not necessary to close sockets quickly. I was just asking since Colin
mentioned that closing sockets are asynchronous so wanted to know where in
the code of ZeroMQ shows that it is asynchronous.
I will be fixing closing sockets too fast issue soon.
On Wed, Jan 28, 2015 at 2:13 PM, Benjamin
Can you provide some more context? What does closing quickly mean, and
why is it necessary?
This might be a specific JeroMQ issue, which is less in use than
libzmq (hence less edge cases tested).
On Wed, Jan 28, 2015 at 11:01 PM, Check Peck wrote:
> Didn't got any reply so far. Any thoughts on m
Didn't got any reply so far. Any thoughts on my question?
On Tue, Jan 27, 2015 at 9:13 PM, Check Peck wrote:
> And we are using "0.3.4" version of ZeroMQ -
>
>
> org.zeromq
> jeromq
> 0.3.4
>
>
>
> Also, where does in the code of ZeroMQ mentions that closing soc
On 1/28/15, 12:34 PM, "McMillan, Scott A"
wrote:
>If I understand the documentation correctly, ZMQ_LINGER will not help
>because the program itself exits.
Sorry to respond to myself, but I may have just gotten confused by the
documentation on linger.
The zmq-setsockopt documentation says the def
>
> To understand correctly, we don't propagate such failures (as
> exceptions or error returns), and even if we did, it'd be pointless...
My thinly veiled agenda here is -
We are already toast in this case anyway, can we just get rid of the extra
complexity that comes with trying pretend we can
To understand correctly, we don't propagate such failures (as
exceptions or error returns), and even if we did, it'd be pointless...
FWIW we added quite a lot handling in CZMQ to handle memory
exhaustion. I don't particularly like that, as it makes things complex
and it's unclear that there's any
Hi,
I'm successfully using pub-sub (CZMQ 3.0.0-rc1 and ZMQ 4.0.5), but I'm
observing the following problem.
My publisher can sometimes be a short-lived program that does something,
publishes the data, then closes the socket and exits the program. If the
data is sufficiently large*, I can see the
Hello,
Did you ever get this resolved?
On Thu, Jan 8, 2015 at 10:29 PM, Gang Liu wrote:
> 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
10 matches
Mail list logo
