Skip to main content
A
ahab_2001
Participant
December 16, 2006
Question

Closing idle connections from FMS

  • December 16, 2006
  • 2 replies
  • 716 views
The FMS management console is showing a number of clients/connections that clearly are not being actively used anymore -- no bytes have been transferred for hours or for several days in one case. I'm guessing that what's happened is that someone paused or stopped the video but left the browser window open, thereby leaving the client alive. (I would have thought that FMS would close inactive connections after some defined period, but this doesn't seem to be happening in these cases, at least.)

Does anyone know if there's a way to use the FMS management console to close these inactive clients? If not, can it be done from the command line?



    This topic has been closed for replies.

    2 replies

    E
    eric_unikname
    Known Participant
    August 31, 2008
    this is a FMS bug.
    FMS3 can not correctly detect client who has disconnect without warning (try to turn off your laptop connexion or modem, you will still appears connected for days).
    A
    Anonymous
    November 12, 2008
    On FMS3 there are settings in the Server.xml, Application.xml, and Vhost.xml config files that allows you to detect idle clients, and then disconnect them. Enabling this setting in the Server.xml file allows the setting server wide, the Application and Vhost files then allow finer control per application. At least that is the theory...my FMS3 install with these settings turned on seems to collect clients that have long since gone.

    Adobe's definition of an idle client is one that has not sent of received streaming data (not control) for the defined period of time in the config files, default is 10 minutes. However I seem to have clients still connected that are idle days after.

    With this in mind I'm filing a bug report as I've checked, and double checked, and what I have should work.
    M
    morharro
    Participant
    December 16, 2006
    From the FMS console you could always unload the app. The when a connection becomes active the app loads once again.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices