[zeromq-dev] Can I make sure that contexts are freed and handles released in a fast loop?

[Ian Barber]

On Thu, Feb 23, 2012 at 6:27 AM, Kuba <kubaraczkowski at gmail.com> wrote:

> The function creates a context and a socket, connects to the server, sends
> a message, receives a message, closes the socket, terminates the context
> .... and starts over again.
> This works very well and very fast, though the actual socket handles (or
> file handles) never get released, which causes the program to crash after
> some (thousands) iterations.
> I know that your answer to this problem will probably be: "keep the
> context and the socket open as long as possible", but not doing that is
> exactly the point of my client.
>
> Therefore, the question: is it possible to make sure, within a program,
> that all contexts/sockets/files/handles are properly closed, so that they
> can safely be relaunched ?
>

If you properly close sockets and term the context it will free up any
resources - whether or not it will try and deliver remaining messages, or
wait for how long, is controlled by the ZMQ_LINGER sockopt (this may be the
source of your problems). It may take the kernel some time to make bound
ports available again if you are reopening within a quick loop - there's
nothing much that can be done at that level afaik. If you're seeing
resource not being released at all it sounds like a bug, and I would try to
create a minimal test case.

Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120223/b6c94330/attachment.htm>