Skip to main content
D
DanielKozimor
Known Participant
July 30, 2007
Question

Unexpected Client Disconnects

  • July 30, 2007
  • 2 replies
  • 991 views
We're running into some odd client disconnects with our appication. It seems that after a period of time (usually 30-45 minutes - but it varies) FMS will boot a client for no apparent reason. On server side, application.onDisconnect gets triggered and, the client gets a "NetConnection.Connect.Closed" event.

It seems like it usually happens to clients that are behind the same router, but at this point, we're just speculating. The networking stuff in FMS is a complete blackbox so I'm not even sure what to debug. Anyone experienced this? Any workarounds? Any logs I can check to figure out why a client would get booted sometimes?

We do have FMS ping all clients regularly (to figure out latency) and all clients call a remote method on FMS on a set interval - this was a possible solution mentioned in some white papers. Clearly, it hasn't helped us.
    This topic has been closed for replies.

    2 replies

    A
    Anonymous
    November 12, 2009

    We have this same problem also.

    Our application is basically a text chat. We have found that anywhere from 10-30 minutes into the session a client is disconnected from the application. It seems to gracefully disconnect because we can see a trace debug message from the onDisconnect event.

    We can't 100% identify the browser but it does seem most prevalent in IE7/8, we haven't observed the problem in other browsers yet.

    It does seem to affect certain people repeatedly while others don't experience any problem. Due to the confidential nature of our application we cannot request very much information from our clients to narrow down the problem.

    We suspected a problem with our code and/or server network connectivity but after reading these posts it seems there could be a problem elsewhere. Has anybody managed to figure out what causes these disconnects?

    T
    techeye
    Participating Frequently
    July 31, 2007
    Here are a couple of things to explore:
    -The application logs should provide you more information logs\_defaultVHost_\YOURAPP\...

    -If it is one particular router that is causing the issue it might be network related.

    - Try adding debug traces to your application.

    - What version & OS are you running?
    D
    DanielKozimorAuthor
    Known Participant
    July 31, 2007
    quote:

    -The application logs should provide you more information logs\_defaultVHost_\YOURAPP\...


    It doesn't help. About the only thing I get from the log is that application.onDisconnect is called but thats just an event listener that gets called after FMS already decided to kick the client out.

    quote:
    If it is one particular router that is causing the issue it might be network related.


    At this moment we're speculating this might have something to do with it - maybe its random. We noticed this behavior in a few separate instances. We would have multiple clients connected to FMS and the client that was booted seems to be one of the ones that was behind a router along with another client. I don't know if that has anything to do with it. I'm inclined to say its not simply network related .. 30mins to 1 hour and we're guaranteed a client is booted.

    quote:
    What version & OS are you running?


    Windows Server 2003.

    A
    Anonymous
    June 5, 2008
    Hi Daniel! We have exactly the same problem in our project. Moreover we've noticed that it happens only in internet explorer 7 (in ie6 & firefox it works just fine).. Have you found any solution for that issue?
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices