client sometime doesn't receive the message sent from server

[pk1981]

this is related to http://www.electrotank.com/forums/sh...ge-from-server.

we have 5.3.2, and experienced client missing event from server. client connects to server ports 9899(tcp) or 8989(http). In server admin panel, server also listen to port 10000(udp) beside 9899 and 8989.

when the problem happens, client still able to send plugin message to server and get response from server. So there is still connection between client and server.

We use sendPluginMessagetoRoom() and sendPluginmessageToUser(), and don't use queue.

[chengen]

The client in this case does listen to connection closed event. The client is definitely online because it can still send plugin message to the server and get response from the server. The issue we see is with those server initiated messages (without client request). Those messages are suppose to be sent to everyone that is online, but we noticed sometimes a client may stop receiving those messages. For certain events, the only way to get those again is to logout and log back in again. (not 100% sure this is true for all server initiated events due to limited occurrences.)
I don't think we are using queued message.

[tcarr]

Can you give me a code snippet of the server side code that is generating the messages that not all clients get? There are several different ways to send messages to "everybody on the server", so I need to know exactly how you are doing it.

[pk1981]

here is the code to send message from server to a client
EsObject oEvent = new EsObject();
oEvent.setString("action", actionName);
...other oEvent property

getApi().sendPluginMessageToUser(user, oEvent);

user occasionally misses the message.

[pk1981]

during a game, server constantly sends users game score, and when game ends, server will send won message to the winner(with highest score). occasionally when game ends, the winner sees his score listed as highest, but doesn't receive the won message.

[tcarr]

If it is always the "won" message that sometimes doesn't arrive, then there's a problem with your plugin logic somewhere. Are you sure that the server is sending that message to him? Try logging the message on the server.

If one plugin message doesn't arrive, but the client continues to process other messages from the server, then for some reason that one plugin message just wasn't sent to this client. Since you are using getApi().sendPluginMessageToUser(user, oEvent); we rule out UDP and queued messaging. How large is the oEvent EsObject being sent? The only other thing I know of that can suppress an outgoing message is if it is too large (as configured in ES Admin General Settings).

[pk1981]

the message size is small. It is less than 1KByte. For this won message, we have so far one incident for missing message. We do have missing messages in other cases, but we are not that sure the cause to be es5 issue than this incident. For this one, we are more inclined to believe it is an es5 issue. But as you point out server might send the message to a different one instead of winning user. Since we don't log this event, we can not confirm it is the case. So we will add log to track this message to see if we can get more insight of it and go back this topic again.

[tcarr]

If it helps, when I develop multiplayer games I usually send a message to the entire room giving the final score and the name of the winner.

[pk1981]

I just recall that right before sending won message to winner, we rewarded the winner some virtual items in our database. the database record shows the reward was given to the winner. So it indirectly shows that the message was indeed sent to the winner, not anyone else.

in the course of game, we constantly send message to all user when the highest score owner changes. That is why that user seeing his name listed as highest score owner at the end of game complained he did not receive the won message.

[tcarr]

Is it possible that the database transaction took longer than usual and the "game over" message arrived at the clients before the "you won!" message arrived at the winner, long enough before that the winner's client had started cleaning up?

Unless you need to make sure that the database transaction has indeed finished before telling the winner "you won these items", you may be better off having the database transaction spawned to an async thread and then notifying the winner immediately without waiting for the transaction to finish.