Skip to main content
Z
zozew
Inspiring
October 28, 2008
Answered

onDisconnect Major bug (LINUX).

  • October 28, 2008
  • 3 replies
  • 915 views
Hi,

After a lot of google usage i found that there is no real answer. I only found this line on a forum said to have comed from ADOBE "FMS depends on Linux TCP system to detect disconnection". This is supposed to be the problem for the extremely annoying problem that applicatrion.onDisconnect is not triggered when a client disconnects from FMS.

We have developed applications that rely heavily on the onDisconnect, paying solution that need it otherwise we can't offer our service because of it's unreliability. I love Flash and FMS but i've never encountered a bug of this severity.

Can some ADOBE representative please give us a straight answer if we have to port all our FMS installations from Linux to Windows?
    This topic has been closed for replies.
    Correct answer zozew
    Hi everyone,

    I have found a fool proof solution...well until now it hasn't stopped working. By using a simple javascript event "onbeforeunload" and letting that call a function in the flash client that closes the netConnection. By doing that we have eliminated the problems in IE and the stream is not running in the background and FMS does trigger the onDisconnect :) I'm happy.

    I hope this helps someone as i know how frustrated I've been

    /Z

    3 replies

    G
    george_20003
    Participant
    November 3, 2008
    I have found the same issue with all of our FMS apps. I even recorded a video of myself at Yahoo's live FMS apps. Simply put, IE won't disconnect from FMS unless all browser instances are closed. It's not swf object as I've tried on my apps for every case. Google chrome, FF and Opera are fine in every case.

    This is a very serious flaw but I can't figure out if it's the browser or FMS. All I know is if it's not fixed weez all in a big bit o trouble!!

    My fms server runs on windows 2003 server. IE version is 7.0.6001.18000 on Vista. Same IE version on XP runs fine and my work computer using older version of IE 7 on Vista runs fine. Unreal!!
    Z
    zozewAuthorCorrect answer
    Inspiring
    November 18, 2008
    Hi everyone,

    I have found a fool proof solution...well until now it hasn't stopped working. By using a simple javascript event "onbeforeunload" and letting that call a function in the flash client that closes the netConnection. By doing that we have eliminated the problems in IE and the stream is not running in the background and FMS does trigger the onDisconnect :) I'm happy.

    I hope this helps someone as i know how frustrated I've been

    /Z
    T
    techeye
    Participating Frequently
    October 31, 2008
    What version of FMS are you using?

    I don't know what forum you are referring to in your quote. The Linux TCP system probably isn't the problem, It works quite nicely.

    Does your issue occur all the time?
    Z
    zozewAuthor
    Inspiring
    October 31, 2008
    We are using FMS 3 and yes it happens with consistens frequency in Firefox,IE, Google chrome..basically all browsers, FlashComGuru has a thread about it. It was thoght to have something to do with some SWFobject(js) version but it seems not. I have seen many times when closeing a tab with a video streaming the tab closes but the feed keeps streaming. I can't see the stream but i hear it and I can see that im downloading more then just the audio. So i would clasify this as a Major Major bug. that Adobe has to adress ASAP or at least give some advice on.

    /Z
    A
    Anonymous
    October 28, 2008
    The onDisconnect issue has been a problem since FCS 1.0, and it shows up on both windows and linux,so moving to windows won't save you there. The best way (I've found) to handle this is to set up a little client/server function that allows the server to make sure the client is still connected.

    What I like to do is have the server invoke a method on each client every X seconds, and require a response within N seconds. If the client doesn't respond with N seconds, I invoke application.disconnect on the the problem client.

    By the way... this is a user end forum. While some of the FMS team people are spotted here from time to time, this isn't an official outlet for Adobe support. If you really want a response from Adobe, I'd contact them directly.
    Z
    zozewAuthor
    Inspiring
    October 31, 2008
    quote:
    Originally posted by: JayCharles
    The onDisconnect issue has been a problem since FCS 1.0, and it shows up on both windows and linux,so moving to windows won't save you there. The best way (I've found) to handle this is to set up a little client/server function that allows the server to make sure the client is still connected.

    What I like to do is have the server invoke a method on each client every X seconds, and require a response within N seconds. If the client doesn't respond with N seconds, I invoke application.disconnect on the the problem client.

    By the way... this is a user end forum. While some of the FMS team people are spotted here from time to time, this isn't an official outlet for Adobe support. If you really want a response from Adobe, I'd contact them directly.


    We have a very similar solution using the ping() function and the pingStats. This gives us the advantage of not having a custom function on the client side. We ping and check the latency and set some parameters that if the clients ping is more then 3s over an interval of 4 second three times in a row we'll disconnect that client. But even running that system it fails sometimes.

    Our main problem is that we base our payperview system on the netStream.onStatus events do we really need to ad a JS fix with onBeforeReload() to stop things like this?

    /Z
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices