Skip navigation
tn_mw
Currently Being Moderated

unexpected disconnect of clients

Sep 6, 2013 10:04 AM

Tags: #client #disconnected

Occasionally clients are disconnected without a reason. The client-side-code is not closing the connection.

On server-side only application.onDisconnect is executed - but who done it?

How to check for unforced disconnects (client or server)?

 
Replies
  • Currently Being Moderated
    Sep 6, 2013 11:48 AM   in reply to tn_mw

    Information you provided is very less for us to derive anything out of it. All clients get disconnected? Are you sure no client disconnects on its own say by closing browser? What code do you have in application.onDisconnect? Do you allow any SWF to connect to your application?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 7, 2013 12:51 AM   in reply to tn_mw

    I'd suggest modifying your client code so that when a disconnect happens, reconnect that client and bring it's state back to either original or current. You can't expect network programming behave exctly like client/native one. I'm currently testing an application using AMSP inside an intranet and even in this local setup disconnects happen.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 7, 2013 6:59 AM   in reply to tn_mw

    All disconnects causing a reconnect - except intended disconnects from server-side (and of course client closes connection)?

    Roughly yes, although I can't foresee the need of having a client disconnect on intent.

     

     

    Furthermore Server-side code must tell clients BEFORE disonnecting it: Next disconnect is intended?

    Either use Client.call() - http://help.adobe.com/en_US/adobemediaserver/ssaslr/WS5b3ccc516d4fbf35 1e63e3d11a11afc95e-7ec3SSASLR.2.3.html or some SharedObjects techniques - http://help.adobe.com/en_US/adobemediaserver/ssaslr/WS5b3ccc516d4fbf35 1e63e3d11a11afc95e-7e63SSASLR.2.3.html

     

    I wanted to use less client-side code as possible, looking ahead to http-streaming.

    It is much more advisble having a fat client in this respoect leaving out AMS for streaming, server-side state storage, and some scripting.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 16, 2013 3:00 AM   in reply to tn_mw

    I have the same problem with random disconnect of clients.

    My client is working normally and is getting data from AMS (using client.call() on the server side). After 20+ hours, client stops receiving data, but AMS app is still calling that "client.call()". I can see this from so many logs I added to trace down the problem.

    After couple of minutes, I can see client is disconnected on the server side, BUT it's not getting notification on the client side! I have reconnect mechanism on the client side, which is working if there's a drop in internet connection. But in this case, client didn't even recognize it's being disconnected.

     

    I have disabled "AutoCloseIdleClients" feature.

     

    Adobe staff, please help?

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points