Skip to main content
Participant
December 4, 2006
Question

AppInstances

  • December 4, 2006
  • 3 replies
  • 401 views
Hello,

I have some trouble with the gc of old aplication instances. After the last client's disconnection, the instances keep running. Even in the default server-settings the instances don't get garbage collected. Does anybody know this problem?

greetz

    This topic has been closed for replies.

    3 replies

    December 7, 2006
    Not really.

    But if you reduce the idle timeout from 1200 seconds (20 minutes) in the application.xml settingsfile you can let FMS remove empty instances after say 180 seconds (3 minutes). That's pretty fast. That's our current setting. It doesn't require an application.shutdown(). You could experiment with settings of say 60, 30 or even 10 seconds. See you own PDF docs or open your application.xml and look through the various very interesting settings that can be tweaked.

    Participant
    December 4, 2006
    I 've solved it that way, too. But i thought there would be an diffrent solution.
    Thank you, anyway.
    December 6, 2006
    Thanks, Jay, that helps out something I was facing, too.
    December 4, 2006
    Yup... that's been the case since version 1. I've found that GC tends to kill instances that have been idle for 20 minutes or more, but I've also found that sometimes GC misses instances.

    What I like to do is have my SSAS take care of it by invoking application.shutdown when all of the clients are gone. Typically, I'd do this in the application.onDisconnect handler... something like this:

    application.onDisconnect = function (){
    if (application.clients.length < 1){
    application.shutdown();
    }
    }
    }
    December 6, 2006
    We experienced problems when we used application.shutdown() ; the server would stop loading external data after a random amount of application.shutdown()'s.

    ( FMS v2.0.1 )

    If you use XML.load or loadvars to get external data you are warned.
    December 6, 2006
    Nasty. Did you find a workaround?