Hello Gavin,
Here is another Adobe reference on client variable (I could not find
it before when I posted other and got side tracked).
Details:
Adobe recommends that you do not store client variables in the
registry because it can critically degrade performance of the server.
If you use the regis
Yes, that's right: if it's set to registry (and any code is set to enable
ClientManagement and doesn't specify a different ClientStorage, both settable in
CFAPPLICATION or application.cfc), then yes, the i/o is to a file that
simulates the
registry (called registry.db, which I think is in the [cf]
Hi Gavin,
This Adobe ref says:
Choosing a client variable storage method
By default, ColdFusion stores client variables in the Registry. In
most cases, however, it is more appropriate to store the information
as client cookies or in a SQL database.
ref:
http://livedocs.adobe.com/coldfusion/8/ht
As for the client settings / DSN.
What is the recommendation then?
We have ours set to registry.
Though since we're on linux and we don;t have a registry - I am guessing it
using some sort of text file but it is only a guess!
Gavin "Beau" Baumanis
On 29/11/2010, at 2:39 PM, charlie areh
Well, as far as having the limits because you've not needed to use it, I'm
proposing
that now's the time. :-) And after capturing that data, then look in the JDBC
logs
(which are not enabled by default-again, controlled in the jdbc settings page).
It's
going to be a lot of data, but you can do a
It is looking like a 'death of a thousand cuts' issue as you put it, and we
do have a plan if that is the case :)
We have limits on the JDBC stuff in fusionreactor because we haven't really
needed to use it. Our DBA is fairly certain that there isn't a set of, or a
specific query that is causing a
Barry, I would just wonder if perhaps you're suffering the "death of a thousand
cuts",
where it's not that you have any (or many) long-running (or even moderately
long-running queries), but instead maybe lots (and lots) of small-running
requests.
Just something to consider.
And as for using FR,
Hi
I upgraded a CF server from 9 to 901 (Windows Server 2008 R2)
SOLR was working from http://XX:8983/solr/ prior
But now I just get 'Internet Explorer cannot display the webpage'
If I go local on the box http://localhost:8983/solr/ - the SOLR welcome page
comes up fine
Any ideas?
Bryce :
Tonight, Monday 29th November, 6pm for 6:30 start.
On Tuesday, November 23, 2010, Chris Velevitch
wrote:
> Due circumstances beyond his control, Dale Rankine has had to pull out
> of next Monday's meeting and extends his sincerest apologies.
>
> Instead, we'll have a general open discussion on th
I have my Workspace config set to 'Build automatically' enabled and 'refresh
automatically' and 'save automatically before build' disabled with no
problems like you are reporting.
Something else you can try if performance is not great is set 'Display
Syntax Errors Only on File Save' to enabled (in
Thanks Charlie,
It is SQL running on its own box, I'll get the DBA to check what else is
running (such as antivirus).
I'm pretty sure he checked the event logs and there was nothing odd there,
he pretty much said that the query activity is normal, just that there is a
very high volume of queries c
11 matches
Mail list logo
