Bug or еrror Repeater

[Nick_od]

Greetings.
I ran the test Repeater. at 50-100 UltraVNC servers.
Windows server 2003 "repeater webgui 2013"
Found a bug or a programming error.
This problem occurs 1-2 times a day.
The program does not show the error and continues to work.
But realistically, the program is not working properly.

The problem is that the thread is not closed and remains in memory.
The server shows that the connection is broken, but the connection is not physically closed.
The server can not create a new thread, because the previous thread is not complete close.

Here are my pictures I hope you'll understand what I'm trying to show you.
http://imageshack.us/photo/my-images/59/rclq.png/
http://imageshack.us/photo/my-images/29/lq9t.png/

[Rudi De Vos]

I see what i can do, finding threading bug isn't simple to debug.

[Rudi De Vos]

Is it while viewers are connected or while the server is waiting ?

[Rudi De Vos]

300 sec server reset ( indeed there is a reset in the code) set to 3000
initiate shutdown before closesocket, this should send a message to the other site that the socket is closed.
100% cpu spike, some loop while socket is closed but not found yet.

http://www.uvnc.eu/1193/repeater_Okt2013.zip

[Nick_od]

Hi Rudi.
Thanks for the quick response.

Is it while viewers are connected or while the server is waiting ?

This occurred in both cases.

I started testing a new version.

300 sec server reset ( indeed there is a reset in the code) set to 3000
initiate shutdown before closesocket, this should send a message to the other site that the socket is closed.
100% cpu spike, some loop while socket is closed but not found yet.

http://www.uvnc.eu/1193/repeater_Okt2013.zip

You're writing a UltraVNC server connected to 300 sec and and then reconnect. (worked as an older version)

Now, in new version UltraVNC server connected to the Repeater for 3000 sec.
But I'm testing the UltraVNC server connected to Repeater for more than 3 hours, and did not disconnected and then reconnected.
Perhaps there is an error in the timer?
http://imageshack.us/photo/my-images/706/i2y7.png/

This, of course, great, but one reconnection of one hour or 30 min would be even better. (I think so )
I will test the new version until Monday. And then write the results.
Thanks for the quick help.

[Rudi De Vos]

Cleanup is now done
*server/viewer is waiting > 50 minutes
*number of free spots < 100 ( the repeater has 1000 free spots, each server that's connected or waiting use 1 spot)

Yes, the server can be wating for hours if he isn't heavy used and free sots >100

[Nick_od]

Hi Rudi.
I tested Repeater.
Errors or failures occurred.
But seen situations where Repeater does not close the connection Ultravnc server correctly.
Repeater indicates that the Ultravnc server is connected. But in reality it is not.
http://imageshack.us/photo/my-images/824/ep5v.png/

I found a greater number of non-closed connections.
"CLOSE_WAIT"
These connections are more and more...
http://imageshack.us/f/35/6bta.png/
http://imageshack.us/f/266/yd4c.png/

Rudi I need more> 100 slots in repeater
You can increase the amount of up to> 500

thank you

[Rudi De Vos]

It has already 1000 slots.
The <100 free slots trigger the cleanup.

[Nick_od]

It has already 1000 slots.
The <100 free slots trigger the cleanup.

I wanted to say.
I need "The <500 free slots trigger the cleanup"

And what about the "CLOSE_WAIT" this is not normal.