Skip to main content
September 6, 2013
Question

unexpected disconnect of clients

  • September 6, 2013
  • 1 reply
  • 1969 views

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)?

This topic has been closed for replies.

1 reply

Adobe Employee
September 6, 2013

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?

September 6, 2013

"Occasionally clients are disconnected" should mean: 99% of clients are disconnecting in usual manner. I am really sure, the 1% of clients don't want to disconnect! The problem is, i can't reproduce it. If it happens, there are only the trace() outputs in application.onDisconnect in the app.logs - but this is not triggered from client/server-side.

swf-verification is not enabled. It is only one swf that connects to the app.

Edit:

For the last 2-3 weeks the flash-player crashes in firefox increased. This is e.g. an unexpected disconnect. But i am searching for other reasons... any ideas are welcome.

Petro_O__Bochan
Inspiring
September 7, 2013

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.