Peter Doyle - 12/07/06 06:21 PM I was just thinking about this a little more, knowing that the MSN guys run a cluster of machines for the messenger service. I'm curious if maybe this forced disconnect is pretty normal in MSN land. It seems like it would be valuable for them to have built in a transparent reconnect feature into the MSN clients, that way when they need to reboot a server, balance out resources, etc., they could just boot people and have the client transparently connect up again, this time being redirected to another server in the cluster (i.e. by a load balancer or dns). It makes a little sense to me, unless there's another way to signal the client to switch servers. If that were the case, maybe it would be valuable to have the gateway try to automatically reconnect on this error? (java.io.IOException: An existing connection was forcibly closed by the remote host)? Then if it fails, set the logged out state correctly. Wish I knew more about the MSN protocol...

Daniel Henninger - 12/07/06 07:03 PM That's actually an entirely different issue. =) (and by issue I mean, JIRA issue in this tracker, automatic reconnect i think is what it's called!)

Daniel Henninger - 12/18/06 05:09 PM I need to gather more information on this before I can fix it.