Hello.
I've started seeing this error message in my server log, and since it's an internal xml created by the server and not the user or extension, I thought it would be interesting to know whats it about and what I can do about it:
That's an interesting bug... Can you replicate that error at will? What server version are you running?
It seems the client is sending some wrong xml data to the server... Does it happen only with the same user? Maybe he's trying to use an hacked client...
Will forward this to Lapo
When I say internally created, I mean the flash API creates it, and not my client side code, I don't sent out this xml manually from my code, it's pretty obvious it's a set user variable function being called from the client side to the server, but for some unexplained reason, something mucks it up.
I can reproduce this, as this happens randomly, and with different variables, not just the one shown in this example I posted.
The only time I saw something like this was when we were running tests with a software firewall running on the computer. If I recall correctly it was ZoneAlarm and after scratching my head for quite a long time I discovered that the firewall was messing up the packets.
It wasn't enough to just turn it off, evidently the low-level packet filtering service was still causing problems, we had to uninstall it from the system to get rid of the problem.
In our case we were running a pretty intense test with lots of packets being sent and received very fast. In a more "normal" scenario the problem wouldn't show up.
If you run a personal firewall, try disabling it. A part from this I don't know what else could cause such a problem.
Like all my problems, this happens only on the production server, never locally, so I guess some users using some firewalls will have to find a way to live without some variables...
What is important is the rate at which this happens. If it is < 2-3% than it's just "natural", users can have all sorts of configurations and problems on their local machines so you never know.
I'll try and see if I can think about how to maybe get a statistic on how many of these errors I have, but I'm not sure it's more then 1%, they don't dominate the log, but they do stand out since I've never seen these before I posted my first message.
