That is correct and good advice. Also storing Client variables in a datasource enables you to access them in a cluster (if all servers are pointing to the same database).
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Firminger Sent: Wednesday, 10 March 2004 2:36 PM To: CFAussie Mailing List Subject: [cfaussie] JRUN Issues Sorry for the new thread, was reading from digest mode. Also apologies if this has been said already as it's difficult to read all in digest mode but I couldn't see any reference to it. I believe the CPU issues people have been discussing are to do with JRUN cleaning out the client variables in the registry. I had this happening for a while before I came across the solution and it stems from the default setting for client variables being "Registry" and "Purge data for clients that remain unvisited for 90 Days". I'm not going to suggest which scenario is best here but I'll bet that changing the settings will fix the issue. I know Geoff had a tutorial on CF Administrator that had great help on these settings. I think the issues are: Decide whether you are actually using client variables Set clientmanagement="No" in Application.cfm if not Set up a data source for storing client variables rather than using the registry (default) setting Lower the purge period to 40 days (means less is held there and purging is faster each day) Check "Disable global client variable updates" Hopefully someone with better knowledge of this will give clearer advice on this issue. Hope this helps. Peter --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
