"Client has NOT closed socket first" in 2.3.0

General discussions and questions.
Post Reply
selsner
Posts: 37
Joined: Wed Jan 25, 2017 11:20 am

"Client has NOT closed socket first" in 2.3.0

Post by selsner » Tue May 29, 2018 12:53 pm

Hallo,

I am testing the current version 2.3.0 and in the server logs I get a lot:

WARNING Client has NOT closed socket first.

We are not using the web gui and I guess that you progammed the afrender to correctly close the socket. I have tried setting the option for SO_REUSEADDR to 1 according to https://stackoverflow.com/questions/106 ... c#10651048, but it did not help. Maybe you have another idea. I do not get the message when using "epoll". Is the epoll mode stable/better/tested ?

Thank you Sebastian
CGRU 2.2.1 - CentOS 6.6, gcc 4.4.7, Qt 4.6

Sebastian Elsner - Pipeline Technical Director - RISE
www.risefx.com

User avatar
timurhai
Site Admin
Posts: 384
Joined: Sun Jan 15, 2017 8:40 pm
Location: Russia, Korolev
Contact:

Re: "Client has NOT closed socket first" in 2.3.0

Post by timurhai » Tue May 29, 2018 3:00 pm

Hi.
Here is a good description about all this:
https://github.com/CGRU/cgru/blob/maste ... ng.cpp#L18

"WARNING" just warns that client has not closed socket first in your pipeline.
It can be a problem on a huge amount of such clients.
But if you have several web browsers and may be some in-house tools, that communicates with afserver and can hold connection until afserver closes socket, it is not a problem.
You can always check whether your have a problem with it:
https://github.com/CGRU/cgru/blob/maste ... ng.cpp#L35

At work we are using EPOLL since it was implemented (2.2.3 2017.11.02). So i think that it is tested.
But "threaded&blocking" i/o is much more tested as it was from the beginning.
I think that non-blocking should be more effective on a huge amount of clients or networking with delays (not a local network). But it was not tested on such cases too.
Timur Hairulin
CGRU 2.3.0 Debian 9, Ubuntu 18.04LTS, MS Windows 7,10 (client only).

selsner
Posts: 37
Joined: Wed Jan 25, 2017 11:20 am

Re: "Client has NOT closed socket first" in 2.3.0

Post by selsner » Tue May 29, 2018 8:54 pm

Thank you! I will check this and report back.
CGRU 2.2.1 - CentOS 6.6, gcc 4.4.7, Qt 4.6

Sebastian Elsner - Pipeline Technical Director - RISE
www.risefx.com

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests