[Glass] GsSocket new returns nil
Johan Brichau
johan at yesplan.be
Fri Sep 27 10:48:48 PDT 2013
Hey Dale,
I found out that I was not sending #close to the ZnClient after using it.
I thought #beOneShot was doing that automatically, but it seems that one has to explicitly close the socket.
So, perhaps not really a Zinc issue but something to mind when using Zinc?
Johan
On 27 Sep 2013, at 19:37, "Dale K. Henrichs" <dale.henrichs at gemtalksystems.com> wrote:
> Johan,
>
> there is a limit on the number of open sockets (I think it is a linux kernel setting ... so you can change it) ... let's open an issue on Zinc on the glassdb repository about this so that we can clean up the unclosed sockts ...
>
> Dale
>
> ----- Original Message -----
> | From: "Johan Brichau" <johan at yesplan.be>
> | To: glass at lists.gemtalksystems.com
> | Sent: Thursday, September 26, 2013 7:47:47 AM
> | Subject: [Glass] GsSocket new returns nil
> |
> | Hi,
> |
> | We have a service vm where a Zinc client is initiating http
> | connections.
> |
> | After some time, errors occurs because no new Sockets can be created
> | (GsSocket new returns nil).
> | Restarting the gem solves the problem.
> |
> | I am not sure, but I think this might be because the socket is never
> | closed by Zinc.
> | And: is there a maximum number of sockets that can be opened?
> | (probably determined by the os ?)
> |
> | Johan
> | _______________________________________________
> | Glass mailing list
> | Glass at lists.gemtalksystems.com
> | http://lists.gemtalksystems.com/mailman/listinfo/glass
> |
More information about the Glass
mailing list