http://jira.secondlife.com/browse/SVC-972
Jake Linden commented on SVC-972:
---------------------------------
Ok.
I now know exactly what is going wrong - still a little fuzzy on the why, but I'm zeroing in.
Here's what the problem is.
There's a particular message that gets sent from the originating sim to the client when either a teleport / region crossing has been completed successfully (ie the originating sim has contacted the destination sim, the agent has been passed across and then deleted from the originating sim).
This message contains information for the client to talk to the new sim.
This message is getting dropped.
What happens is that the client already knows a teleport is in transit and dumps out the old region information internally after the teleport times out, but doesn't have replacement region information, in which case it considers you logged out and, well, logs you out.
Thats what is happening.
Now, why is this message getting dropped?
Well, it's going via a new system - an HTTPS driven TCP/IP system that encrypts the information since some of the new server information we send to the client we want to keep encrypted.
This system is dropped the message in one of three possible places.
Either in the Simulator sending the message out to the client, in transport on it's way to the client (which is why when you guys turn off TCP/IP on your routers you get the same error) or in the code on the client that takes the incoming TCP/IP message and then fakes a UDP call so the same code that *used* to talk to the UDP stream is called. We know the actual code that runs when the message is received is not being called because it dumps out text to the logs and all the logs you guys have posted is missing this text - ergo that function is not being called.
I have a suspicion it's in the simulator side - what I need is one of you guys that is seeing this to ping me online if you see me, since I need to watch the logs of the sim you are teleporting from where the failure occurs and look for a specific message. If I see that message, then I know my hunch is correct. If I don't, then we need to look further down the pipe.
I'm going to be online tomorrow (the 26th of Feb) looking for people who are having the teleport fail there and then with this error.
Just wanted you to know that progress is being made.
---------------------------------
Ok.
I now know exactly what is going wrong - still a little fuzzy on the why, but I'm zeroing in.
Here's what the problem is.
There's a particular message that gets sent from the originating sim to the client when either a teleport / region crossing has been completed successfully (ie the originating sim has contacted the destination sim, the agent has been passed across and then deleted from the originating sim).
This message contains information for the client to talk to the new sim.
This message is getting dropped.
What happens is that the client already knows a teleport is in transit and dumps out the old region information internally after the teleport times out, but doesn't have replacement region information, in which case it considers you logged out and, well, logs you out.
Thats what is happening.
Now, why is this message getting dropped?
Well, it's going via a new system - an HTTPS driven TCP/IP system that encrypts the information since some of the new server information we send to the client we want to keep encrypted.
This system is dropped the message in one of three possible places.
Either in the Simulator sending the message out to the client, in transport on it's way to the client (which is why when you guys turn off TCP/IP on your routers you get the same error) or in the code on the client that takes the incoming TCP/IP message and then fakes a UDP call so the same code that *used* to talk to the UDP stream is called. We know the actual code that runs when the message is received is not being called because it dumps out text to the logs and all the logs you guys have posted is missing this text - ergo that function is not being called.
I have a suspicion it's in the simulator side - what I need is one of you guys that is seeing this to ping me online if you see me, since I need to watch the logs of the sim you are teleporting from where the failure occurs and look for a specific message. If I see that message, then I know my hunch is correct. If I don't, then we need to look further down the pipe.
I'm going to be online tomorrow (the 26th of Feb) looking for people who are having the teleport fail there and then with this error.
Just wanted you to know that progress is being made.