No Registry Service available

[king93pin]

I am getting the following error message continuously in my cfserver.log file:

01/06 15:54:08 Information [jrpp-121991] - No Registry Service available

Online searches have not produced any information regarding this error. Does anyone have any ideas on what this error is and how I can correct the problem so it will stop creating so many log entries?

Thanks,
Bob Duman
Senior Systems Engineer
Cleantech Group LLC

[Charlie Arehart]

Bob, this is just a guess, but what OS are you on? Is it Linux or OSX, perhaps (or something else other than Windows)? The registry is of course a Windows concept, and it may be that something is trying to write to it when it's not there.

Perhaps our fellow forum reader Jochem will speak up with his experience on Linux systems.

As a guess until then (or someone else does), is this a development or production server? If the former, how about going into the CF Admin page for Client Variables and change it to not use Registry as the default repository.

And even if you do not have it set to registry (which is the default when you install, at least on Windows systems), consider also that this merely sets the default if code doesn't override it. You could have code where someone sets clientstorage="registry" (as either a this.scope variable in application.cfc or in cfapplication in application.cfm or some other page.) Worth double-checking.

[king93pin]

Yes, this is running on Linux. This is a production server, but I've spoken to our developers and they do not use client variables in their programming. What storage method do you recommend for the default to be set to?

Thanks,
Bob Duman
Senior Systems Engineer
Cleantech Group LLC

[Charlie Arehart]

If I had a nickel for every time someone said, "but we don't use client variables". 🙂

It matters not a wit if they ever say CFSET client.somevariable. All that really matters is if any code anywhere says ClientManagement="yes", in the same files I mentioned before about clientstorage. If so, there's a default setting in the client variables admin page for the settings of each repository for "disable global variables", and it's not checked by default, so each visit by a user to each page (that hits that clientmanagement="yes") will trigger an update of the client var repository for 2 variables, hitcount and lastvisit, whether you ever use them or not.

Really quite a tragic thing, this default, and made all the worse when sites are hit by spiders, robots, and load test tools, as they don't remember the cookie CF sets on each visit, and so they cause creation of a new client variable repository entry--an INSERT, rather than an update--on EVERY request for a CF page. It's something I've blogged about here: http://carehart.org/blog/client/index.cfm/2006/10/4/bots_and_spiders_and_poor_CF_performance

(Llet me clarify also that if you go searching for such references to ClientManagement being enabled, be aware that it could also say ClientManagement=yes, or "true", or true, etc. Just search for any reference to ClientManagement at all and eyeball the results.)

As for a better default, well, you can set it to NONE, but that will fail if indeed any code does enable ClientManagement. A better option may be "cookie", which puts the client vars on the browser. Just be aware that doing that will in fact cause loss of connection to the variables in the previous location, if in fact anyone was using them. If they're not, then this may solve your problem.

Hope it helps.

[Guest]

Are there any benefits to having the client variables in, say a local datasource rather than cookies?

Thanks

john