ColdFusion MX and Client Variables in the Registry

Yes, even CFMX users should watch out for client vars that are stored in the Registry. In CF5 and earlier this practice would make ColdFusion progressively slower, causing it to often crash. In CFMX the symptom of this is that CFMX will spin the CPU very high at 60 minute intervals.

The first recommendation is that you shouldn't store client variables in the Registry, but should configure a datasource for that purpose instead. However, even after that configuration change is made the server may be left with a very fat Clients key in the Registry which will gradually be purged according to the setting in the CFAdmin. The problem is that there is a bug where unchecking the little Purge checkbox won't stop CFMX from trying to purge the Registry anyway. If there are thousands and thousands of client keys there then CFMX will get stuck temporarily while trying to read through them all when a background thread kicks in every hour to handle purging. The solution could be to manually remove all the client keys from the Clients registry key or call support and ask for the hotfix. The key that may contain the many client subkeys is:


Another Set of Tips for Configuring CFMX For J2EE Servers

There's a been a few items about CFMX for J2EE that I've been meaning to blog, so here's a post just to get them all out of the way... First, here's a link with centralized information as a good starting point: Deploying ColdFusion MX 6.1 on J2EE Application Servers

CFMX / JRun / Clusters - Configuring the ColdFusion Administrator