Messages per second

[Lapo]

Yep, there seem to be pretty bad problems with persistent connections.
I can suggest a simple experiment if your server is Linux based.
Are you familiar with netcat?

You could use that to listen on a custom TCP port and establish a connection using any client technology.
I'd suggest to use Flash. Simply open an XMLSocket or Socket connection to that port and leave it connected, sending any ping data every once in a while.

Under decent network conditions you should be able to keep up the connection for hours (and days too)

The test would also be useful to report the issue to your bandwidth provider.

Btw, making netcat listen on a port is a simple as this:

Code: Select all

nc -l 5555

where can be any free TCP port number (>1024)

[darnpunk]

Hi Lapo,

Many thanks for the tip. I am using Windows Server 2003 and will try to find the equivalent of the method you mentioned for the experiment. If you have anything similar for Windows, I hope you can share it.

I will try this out and post back a report. Thanks again!

Regards,
darnpunk

[Lapo]

try searching netcat for windows.

[samyphp]

Hi there,

Am also having the same problem. i done all the above and tested,but the user getting logged out automatically. If anybody knows, please help me..

Thanks
Palanisamy

[demofish]

i've got this issue ,too
users alway got disconnected,even the user is still doing something---not an idle user.

[Lapo]

The reasons why a user can get disconnected can be various:

1- sloppy client connection
2- lack of server side bandwidth
3- too many dropped messages for the client (which is a direct consequence of #1)
4- too many messages in too little time. If you're trying to send 50+ messages per second it's easy to get these problems. Since this is impossible, try to avoid bombarding the client and server with an unreal number of messages per second. (Average network lag suggests an average between 10-20 msg/sec)
5- idleness

Based on how frequently this happens you should check that you have enough bandwidth, your messaging frequency and the configuration of the client queues.

[2paul]

On my Serverside I do something like this...

Code: Select all

for (j=0;j<=200;j++){
	_server.sendResponse(res, currentRoomId, null, player, "str");
}

200 messages at once...
I have normal DSL6000, and some other netconnections open and a VPS-Server in the net...

Its a little bit slow (but still Ok), but i doesnt get disconnecet...

Before I do it with 500 messages at once, works fine

[Lapo]

Why in the world would you do that?
That's the best way to obstruct the socket channel between server and client... unless it's a just a test I would totally avoid to use anything like that in production code.

[2paul]

I have a big world for many players (when its ready) and when the game starts I have to send all the places of gold...thats 200...

But you are right, that dosent work, i just work on it, and have comment the trace line, i have in the code above ...

Now i get in my local-network an disconnect, because of too many droped messages.

The trace slows the messages, so there was no problem before...

[Lapo]

I have a big world for many players (when its ready) and when the game starts I have to send all the places of gold...thats 200...

Assemble all those into a single message and send that.
Never use for loops around a sendResponse call, it will hurt the server and clients

[2paul]

Ok, ok, maybe I think to easy

Thx for your tip ...

Its much more work

Code: Select all

for (var a=0;a<user_count_akt;a++){
	player_ID = all_Players[a].getUserId();
	player[0] = all_Players[a];
		
	if (player_ID != uid){
	_server.sendResponse(res, currentRoomId, null, player, "str");
			
	}
}

So you think this is although no good for sending the positions...
In the sendResponse I have only one player ( player[0] ), not an array of users...so I call the sendResponse very often, is this a problem for the server ??
Or it dosent matter ??

[Lapo]

As I said NEVER put a sendResponse inside a for loop
Didn't you notice that you should pass a list of recipients as the fourth argument of sendResponse?

So build the message first, populate a list of recipients next and finally perform ONE call to the sendResponse() method.

[2paul]

Thx again...I will change it...you make a VERY GOOD Job here in the Forum

[sutekin]

Hi,

I have same problem on legacy ElectroServer v3-7-3. I think this problems source is similar on all Java Socket Servers.

By the way is there an automated tool for migration from ES3 or other servers to SFS ?