You can consider turning off PERSISTENTRESTART= which will tell Witango to not load values on startup. You will loose user sessions on restart if you do this, however.
Or you can consider deleting the file(s) in the VariableCache folder after a successful startup, this is where the variables are kept and the .dump file is created on each proper shutdown. Just FYI- your hypothesis of Witango loading an outdated cache file upon crash is valid. I would carefully read through witangoevents.log to see if that was actually the case or not. If it properly shutdown, the cache should've been updated. Robert -----Original Message----- From: Kent Swisher [mailto:[EMAIL PROTECTED] Sent: Thursday, October 11, 2007 1:53 PM To: Witango Talk Subject: Witango-Talk: Domain scope variables and cache files I use domain scoped variables (arrays) to cache frequently used select list values that change infrequently. If I remember correctly, domain scoped variables are saved to a cache file when the server is shut down gracefully. Is this correct? If so, is there a way to update the cache without shutting down the server? We recently had a problem where the domain scoped vars reverted to older values and can't think of any explanation except that the server may have hiccuped and restored the domain variables from an outdated cache. I trap for empty domain var to know when to re-querying the DB to refresh domain variable. Maybe I need to switch to application scope var so I can set a variable timeout? -> Kent Swisher Engineering Tools -> Alcatel-Lucent Application Support Engineer -> Wireline Access Products [EMAIL PROTECTED] -> Petaluma, CA 707-792-7116 (on net 2-855-7116) ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
