Dropping messages

ericheimburg · Post by **ericheimburg** » 22 Jan 2012, 21:09

Hi, I'm having a really hard time figuring out how to proceed debugging this. The client seems to be dropping entire messages -- that is, my EXTENSION_RESPONSE handler isn't getting called. By the time the messages start disappearing, I've already received a hundred or so messages in rapid succession (the start up process sends about 200 messages), and then the client just starts dropping the last few startup messages.

It's not 100% reproducible, and the number of dropped messages varies. It must have to do with timing or buffers or something, but I can't find a way to get (or give you) more information. Turning on SFS debugging doesn't show anything informative. (Except things like "Data Read: Size > 1024, dump omitted".) All I can see is that the messages are sent from the server and then... they vanish.

How can I debug this? Is this something you've heard about? Please help, this is really really frustrating and I've been banging my head against the wall for days.

(I am using the build of the client from the sticky thread above.)
EDIT: and this is with UDP and BlueBox disabled.

ericheimburg · Post by **ericheimburg** » 22 Jan 2012, 22:02

I think I found it... the server was dropping them because <systemControllerRequestQueueSize> is set to 120 by default!

Can I make a request that when the server knowingly drops a message, it generates a warning or informational message? That was really tedious to figure out.

ThomasLund · Post by **ThomasLund** » 24 Jan 2012, 13:17

Hey,

Not sure you can hook into the server side dropping messages. Try to post in the top SFS2X forum to ask there - thats where the server guys hang out.

In the upcoming RC of the server there have been some fixes related to dropping messages too. So that might help you as well once its out.

/T