Matthew,
The site seemed to be responsive this morning, so I took a look at things
and have fixed the basic errors that were happening and the home page now
loads properly.
I've done the following.
Implemented an error handler in Application.cfm. So on error a full dump of
the error is shown
Byron, no offense but did you really mean to send this out to the enitre
CF-Talk list?
On Wed, Jul 23, 2014 at 9:14 AM, Byron Mann byronos...@gmail.com wrote:
Matthew,
The site seemed to be responsive this morning, so I took a look at things
and have fixed the basic errors that were
Had a site go down in the early morning hours the last two days -
Coldfusion hangs - requiring a restart to get it back up again.
Running CF 10 on Windows Server 2008 R2
1. No major errors in the log files.
2. Log files are set to relatively small size limits
3. Something seems to be eating a
Apologies to all, result of too many open windows and not enough coffee.
On Wed, Jul 23, 2014 at 9:44 AM, Scott Stewart webmas...@sstwebworks.com
wrote:
Byron, no offense but did you really mean to send this out to the enitre
CF-Talk list?
On Wed, Jul 23, 2014 at 9:14 AM, Byron Mann
'
ok I got the pathing issue sorted. I am having a weird issue with the home
page formatting. I have a br and the page layout it putting the test to
the right, and the two last images are missing. Not sure what is going on.
Please download the latest files before you make any changes, I have
Client purge means that you have client variables turned on in the CF
admin. The purge routine attempts to clear out stored variables either in
the registry or in a database.
If you're not using client variables turn this off, if you are, make sure
that you're not storing them in the registry
Understandable. Mornings can be a bear. No worries.
On Wed, Jul 23, 2014 at 8:54 AM, Byron Mann byronos...@gmail.com wrote:
Apologies to all, result of too many open windows and not enough coffee.
On Wed, Jul 23, 2014 at 9:44 AM, Scott Stewart webmas...@sstwebworks.com
wrote:
Client purge is removing client vars that are too old. If you have client
variables set to default they will be stored in the registery (win) or a big
XML file. The purge process removes them. To fix this:
A) Verify that you need client vars. If you don't adjust your application
settings
Tia,
FYI - storing client vars in the registry and locking up during the purge is
a fairly common trouble spot. I would not be surprised if that is your
problem. It can show up after a while too - because the client vars
persist for 30 days, so you can suddenly see problems 30 days after an
Just read that one again.
30 days? Approx 30 days ago the site was hit with a SQL Injection
attack. Wasn't 2000+ attempts like some of the previous attacks, but
still, a couple hundred hits in a 15 minute period or so.
Don't know if that means anything.
On 7/23/2014 10:03 AM, Mark A Kruger
Are the client variables in a database? If so, I would run a query on the
CF tables to get a count of records. It could be your attack was worse
than you think and have a boat load of records. An attack like that would
likely result in a set of client variables for each request.
The query to
scenario is this. main thread starts a pool of threads to do work.the
result of all threads are combined together to form a big result set and
returned.
however, i'm envisioning that if 1 thread fails, the thread join is still
waiting for the 9 other threads to complete before throwing
12 matches
Mail list logo
