I'll try to reproduce the problem - but as I said it is random and is on my live server so its bit difficult. Here is same more info from the client side:
Code: Select all
[SFS - DEBUG] Handling Data: 6861, previous state: 0/-30566
SFS2X - Error sending byte array
Hi
What I have is a game - and the error occurs when spectator joins and ask for the game. So when i send the complete state of the game - sometimes I get the error - sometimes not. But the problem is that every time the spectator joins the game, its a different state of the game so its little bit hard to reproduce.
What I have is a game - and the error occurs when spectator joins and ask for the game. So when i send the complete state of the game - sometimes I get the error - sometimes not. But the problem is that every time the spectator joins the game, its a different state of the game so its little bit hard to reproduce.
It shouldn't be too difficult, but you should store the binary data on disk on the server side so that you can retrieve it later for testing.
Each file should have an ID, a progressive number can be just fine and you should log a simple message every time you send the data, something like "Now sending binary data with ID: xxx"
Try running one spectator in the Flash IDE with the SFS debugging turned on. As soon as you get the error you can go back on the server, grab the binary data and report to us.
We will need the binary file and the transcript of the client debug session
Each file should have an ID, a progressive number can be just fine and you should log a simple message every time you send the data, something like "Now sending binary data with ID: xxx"
Try running one spectator in the Flash IDE with the SFS debugging turned on. As soon as you get the error you can go back on the server, grab the binary data and report to us.
We will need the binary file and the transcript of the client debug session
Hi Lapo
I work with leogesteira, that one with the initial problem.
I have found a problem with certain size messages in SFS2X, and managed to create a Kludge to avoid the problem that leogesteira had.
Would you prefer that I send you an email with the explanation, or should I post here.
PS: I believe that you would create a pacth to solve this problem
I work with leogesteira, that one with the initial problem.
I have found a problem with certain size messages in SFS2X, and managed to create a Kludge to avoid the problem that leogesteira had.
Would you prefer that I send you an email with the explanation, or should I post here.
PS: I believe that you would create a pacth to solve this problem
I think a problem we had is related to yours.
Once one of our SFSObject ByteArrays passed a certain size (on the order of 180kb IIRC) errors were thrown on the client side.
Another symptom was that the server would "freeze" one of the clients (no messages processed) until another client logged in or sent a message.
We worked around both symptoms by sending bulk data over HTTP instead.
Just wanted to say that as this particular bug is not isolated.
Once one of our SFSObject ByteArrays passed a certain size (on the order of 180kb IIRC) errors were thrown on the client side.
Another symptom was that the server would "freeze" one of the clients (no messages processed) until another client logged in or sent a message.
We worked around both symptoms by sending bulk data over HTTP instead.
Just wanted to say that as this particular bug is not isolated.
