HTTP 500 errors from event poller
tracked
animats Resident
Log In
Maestro Linden
tracked
Henri Beauchamp
Just for the sake of correctness, my viewer is the Cool VL Viewer (Black Dragon is NiranV's viewer).
Note also that the 500 errors (500 code in HTTP header) received viewer side are in actuality 502 errors (the body does list 502 as the error code) which header got somehow rewritten on the path between the sim server and the viewer. You can see this by enabling the "EventPoll" and "CoreHttp" debug tags in the Cool VL Viewer ("Advanced" menu -> "Consoles" sub-menu -> "Debug tags"), and increasing the "EventPollTimeoutForSL" debug setting (CTRL ALT S to pop up the floater) to 90 (seconds); this latter setting will be used on next simulator connection (meaning you will need to either TP away or relog).
animats Resident
This is to document a known problem with the event poller, the mechanism by which viewers get certain key information from the sim servers. Monty Linden has confirmed that this is a problem. Henri Beauchamp has seen the problem in his Black Dragon viewer, and I've seen it in my Sharpview experimental viewer.
The basic problem is that the event poller is not a reliable delivery mechanism. It needs to be, because failure to deliver some events will stall out any viewer. This seems to hit the TPV viewers, but some of that may simply be that the TPV viewers have more logging than the SL viewer.
This seems to be at least one of the problems behind connecting to adjacent regions and region crossings. It's probably not the entire problem. But it is a well-defined, easily reproduced problem that causes intermittent trouble.
So, this puts the problem into the new issue system. Thank you.