ColdFusion Muse

Choices for Client Vars: Registry Bad, Datasource Good

Client Variables and the Registry

Ask any experienced ColdFusion troubleshooter and he will tell you the same thing, "Don't store client variables in the registry." In fact, when examining a sick server one this is one of the first items I look at. If the customer says "It seems like the server stops about every hour" it's a safe bet that the default storage is set to Registry and the default purge interval has been left alone at 1 hour and 7 minutes (which is kind of an odd interval - probably some Adobe employee's anniversary in binary).

In many cases this is a "hidden" problem waiting to burst onto the scenes and bite some poor site owner in his nether regions. The owner launches his or her site and begins to gather traffic with the default settings for client variables. By default ColdFusion stores 90 days worth of client variables in the Registry - so the site can actually perform well for a few months. But then, out of no where, the server starts to drag and even stop every hour or so. Under the hood the purge operation is starting to find client vars that are 90 days old or more and it is taking quite a long time to delete them. The OS sees the registry keys being deleted and (sometimes) attempts to shrink the registry size. This affects a sort of "locking" on the registry where new keys are not being written - meaning requests are queuing and the server is slowing to a crawl. Now you might think that fixing this is as easy as switching from the registry to a datasource or cookie storage as the default, but there are some nuances to this fix that bear mentioning.

What about Linux

Before moving on let's talk about Linux. Linux, having nothing really like a "registry" uses a file located in /coldfusion8/registry/cf.registry. ColdFusion writes client vars as registry-like entries into this file. In fact you should know that this file is an attempt to mimic the windows registry. The file contents look like this:

1:  HKLM:1
5:  HKLM\SOFTWARE\Macromedia:1
7:  HKLM\SOFTWARE\Macromedia\ColdFusion:1
9:  HKLM\SOFTWARE\Macromedia\ColdFusion\CurrentVersion:1
11: HKLM\SOFTWARE\Macromedia\ColdFusion\CurrentVersion\Clients:1
13: HKLM\SOFTWARE\Macromedia\ColdFusion\CurrentVersion\Clients\338751..
14: cfid:		338751;	REG_SZ
15: cftoken:		CD188FEB-F93F-00EA-FC626B67A1CD00A4;	REG_SZ
16: hitcount:		3;	REG_SZ
17: timecreated:		{ts '2009-10-27 07:35:48'};	REG_SZ
18: lastvisit:		{ts '2009-10-27 07:35:50'};	REG_SZ
19: testSQL::this:		yes;	REG_SZ
20: testSQL::that:		no;	REG_SZ
21: urltoken:		CFID=338751&CFTOKEN=CD188FEB...;	REG_SZ
If you have ever gone poking around in the windows registry it should look familiar to you. Note, I've replaced the string HKEY_LOCAL_MACHINE with HKLM to save space above. When client vars are stored in the "registry" for a Linux box, the values are written in keys like the one at line 13 above. In it's default configuration the Global variables are "on". That means in an application with client vars enabled the "hitcount" and "lastvisit" values are updated with every request. Now ColdFusion actually holds on to vars in memory and flushes them to the file periodically. Additionally, Linux is very good at handling file reads and writes (it runs circles around 32 bit windows). But even so it should be obvious that on a very busy server and with 90 days worth of these variables this file could become the source of I/O bottlenecks as CF and Linux try to negotiate reads and writes to it.

I Don't Think I Use Client Vars

"Ah..." you say, "but I never set any client vars." Well if you set the "clientmanagement" key in your Cfapplication tag (or application.cfc properties) - then you are using client vars whether you know it or not. Even if you don't "set" any specific client variables ColdFusion will still create a token for each user and set the "Hitcount" and "lastvist" variables. In fact, if you make no changes to the default configuration, these 2 values are set still written to with each new page request.

The Fix

Ok, so why belabor the point. Registry bad datasource good - right? Hmmmm.. one thing to keep in mind is that not all datasources are created equal. For example, if you move your client vars to an MS Access DB it is probably better than the keeping them in the registry. But that is sort of like saying Adam Sandler is a better actor than Chevy Chase or Windows ME was better than Windows 98. Do yourself a favor and use a real honest-to-goodness RDBMS for your client vars. MySQL or MSSQL are excellent choices (and there are several others).

The Steps

Before you go into the client vars management app in the ColdFusion Administrator you must first create the datasource to use as your client variable storage DB. This is done through the "datasources" application in the Administrator. We won't go into that here except to note that the datasource must have read, select, insert, update, delete and create permissions enabled in order to set it up initially. After you set it up and the tables are created you can drop the "create" permission.

Next, click on the "client variables" link in the left hand admin menu of the CF Administrator. You will see the default list of places to store client vars. Initially you will see just "cookies" and "registry" with "registry" selected. At the top you will see a list of all the datasources you have setup in ColdFusion including the one you just configured.

Select the datasource you prepped and click "Add". The next screen shows your configuration options options.

This screen has one choice that you should consider carefully - the checkbox for disable global client variables. These are 2 values that are a part of each set of client vars. By default every time the same client (based on the cfid/cftoken or the JsessionID) hits your page the lastUpdate key is reset and the hitcount key is ticked up by one. Disabling this constant barrage of updates can save your DB from a lot of hits. In fact, as a rule of thumb, unless you are actually using hitcount or lastupdate somewhere in your code you should always disable global updates. Why bombard your DB with values you are not going to use? I also usually set the purge value down to 10 days - although this depends greatly on the intended use.

Clicking "submit changes" will create the tables on your DB and take you back to the list. The final step is to select the radio for your new datasource and click Apply.

Why Am I Still Locking Up?

Have you solved your problem? Perhaps not yet. Remember that the list of client storage options represents all the ways that any application on the server can use to store client variables. When ColdFusion goes to purge variables it is going to check out each of the choices on the list (except cookie) and attempt to delete keys that are older than N number of days. Simply moving to a datasource solves the problem of where these vars are stored going forward but if you have had your server in service for a while your registry may still have a gazillion registry entries in the "clients" key. In spite of your fancy pants new database for storage CF still cycles through all of the choices in the list - including the registry. Until all those keys are out of there the server might continue to lag.

At least one solution is to simply delete the clients key from the registry (or delete the cf.registry file and replace it with a blank file). The key is located at HKLM\SOFTWARE\Macromedia\ColdFusion\CurrentVersion\Clients. Under no circumstances should you try to left click on this key to load the sub keys. It could have hundreds of thousands or even millions of values in it. I usually stop ColdFusion and then using regedit I right-click on the word "Clients" and delete it the whole key along with it's sub keys. Even this can take a long time. To be safe I recreate a blank "Clients" key in its place and restart ColdFusion. Now, theoretically, ColdFusion has nothing to purge in the registry.

Hold Your Horses We are Not Done

Recently I fought this client-vars-in-the-registry battle on a Windows 2008 server. The server continued to have problems after I deleted the clients key and moved the client vars to a datasource. I suspected that client vars were not really my problem, but I wanted to eliminate it as a possibility. Windows 2008 server is extremely role and permission conscious and I still suspected that CF's hourly access of the registry was causing problems of some sort. My suspicions were further confirmed when, after setting the purge interval to 18 hours, the server bogged down on cue when the purge operation started (even though there were no values in the registry and no values in the datasource I had created). So I went searching for a way to exclude the registry altogether from the purge operation.

This led me to one of those XML files curiously named by Macromedia developers who can't seem to divest themselves of pop-culture references even at work - the neo-clientstore.xml file (found in Coldfusion8/lib). This file is a WDDX packet containing the list of options for client storage. On careful examination I found this node:

<var name='Registry'>
    <struct type='coldfusion.server.ConfigMap'>
        <var name='timeout'>
        <var name='description'>
            <string>System registry.</string>
        <var name='type'>
        <var name='name'>
        <var name='purge'>
            <boolean value='true'/>
        <var name='disable_globals'>
            <boolean value='false'/>
As an experiment I commented out this node. I also found a node at the bottom that looked like this:
<struct type='coldfusion.server.ConfigMap'>
    <var name='PURGE_INTERVAL'>
    <var name='default'>
    <var name='uuidToken'>
        <boolean value='false'/>
Naturally I had to change the "default" to something other than registry before removing the registry node. I set it to "Cookie". In fact, take care of changing the default to a datasource before you try to editing this file. That way you won't have to fiddle with the ConfigMap node. After removing the Registry node and restarting I logged into the CF Admin. Registry was no longer listed as one of the options. ColdFusion started and ran successfully.

NOTE: If you do this and any (foolish) developer has actually specified "registry" in the cfapplication tag (or the properties of the Application.cfc component) - as in:

<cfapplication name="blah"

...then removing the registry node from the neo-clientstore.xml file will break their code. Also note, I am still testing to see whether this resolves my problem. I suspect that ColdFusion uses this file to determine what datasources (in this case "Registry" is a datasource for client vars) to purge. I am further assuming that without he registry node in this file ColdFusion will not attempt to access the registry at all - at least that is my hope. I am running a test server configured this and I will report with a follow up post if this has no effect, causes other issues or errors, or is otherwise a poor solution.

Meanwhile, if it pans out I might implement it across the board for all servers - especially windows servers.

Rick O's Gravatar 67 is the first useful prime number after 60. (Yes, 61 is a prime, too, but it's too close to 60 to be of use.) Setting timeouts in durations of primes is common because it lessens the likelihood that two timeout sessions will overlap.

Of course, that's completely anecdotal and may not in any way be the reason why they chose 67 minutes, but that's always made sense to me.
# Posted By Rick O | 10/27/09 3:52 PM
mark kruger's Gravatar @Rick,

Ok... so you win the prize for esoteric knowledge :) That is really cool - although one wonders how slow a computer has to be to worry about seconds rather than teraflaps or something smaller (ha).
# Posted By mark kruger | 10/27/09 6:04 PM
Don Blaire's Gravatar Thanks, I never knew what the Disable global client variable updates was for. Now I know when to use it.
# Posted By Don Blaire | 10/29/09 6:14 PM
Matt E's Gravatar If you are running a cluster of ColdFusion servers, should you create a different database for each server to use, or can you just use the same database for all of them?
# Posted By Matt E | 10/27/10 1:44 PM
Mark Kruger's Gravatar @Matt,

That greately depends on your configuration. If you are talking about load balancing (which is not the same as clustering) then One of the advantages of running a single DB for client vars is that they can then persist across the various servers... But if you are using sticky sessions this is probably not necessary (although it is convenient.).

If you are talking about true clustering then you really have only the option of using a single DB since all of the instances in the "cluster" are supposed to be replicating.

Not sure if this answers your question :)
# Posted By Mark Kruger | 10/27/10 1:56 PM
Matt E's Gravatar @Mark,

Yes, we are using load balancing. Right now we have both Sticky Sessions and Session Replication turned on and we are storing sessions in the registry, which is causing the slowdowns that your article addresses. The replication is only on in case one of the servers were to go down.

If we switch to storing sessions in a datasource, would we be able to turn off Sticky Sessions and Session Replication?
# Posted By Matt E | 10/27/10 1:59 PM
Paul's Gravatar Amazing explanation. For some reason we had an app with clientvars on in App.cfc however they were not actually using client vars there were millions of entries on the registry that were "stuck" causing huge CPU spikes. A great help thanks!
# Posted By Paul | 1/31/12 2:08 AM

Blog provided and hosted by CF Webtools. Blog Sofware by Ray Camden.