Oh man why do the good conversations always happen when I'm
holidaying. I've just driven 700kms up to Golburn and it's about
130am.
These quick words aren't well thouht through so I sooologise in
advance for that. And I'm on a mobile phone. I don't really have time
to back track, so please allow
@MrBuzzy, thanks for making the effort to reply. I thought there were
fires near Goulburn? You've explained precisely what I've always
thought has been the problem but as Charlie has rightly suggested I
should get the proof via a monitoring tool to be sure. I'm trying to
get Fusion Reactor
So my quip about clean NSW air was made without any knowledge of fires.
Bummer. I wasn't being sarcastic. :-(
As for FusionReactor (it's spelled without a space, like CF), the 2.0
version will work. But you can upgrade to 2.04 to get all the fixes and
enhancements. More, including the steps and
I've got Fusion Reactor 2.0.0 (this is the only licence we have) up
and running and am looking at the Request History. We've not had a
hang yet but I just wanted to get familiar with the tool. I'm looking
at the requests which are taking 45+ seconds and they are all pages
which involve a call to
@Charlie;
1. Sorry I did miss your joke.
2. I'll aim to type FusionReactor correctly from now (these things
annoy me as well especially when you're looking for a CF job and you
have to type Cold Fusion and you end up with jobs like Cold
calling :)).
3. I've already updated to v.2.0.4 (thanks for
No, you can't with FR get any sort of profile of what lines were slowest
within a request. Only the CF8 Server monitor has the depth of insight to
report that. What I had been referring to is if you can catch the request
WHILE it's running, in which case you can get a stack trace by clicking a
No worries. Just a couple of quick replies:
@Charlie;
1. Sorry I did miss your joke.
No, no. The point was I wasn't making a joke (in my reference to clean air
in Goulburn for Matt). When you said to MrB that there were fires, I wanted
to clarify that my earlier comment wasn't a joke. I lived
Hi Charlie,
Out of interest (while I await a hung server) I've configured FR 2.0.4
on my dev PC and run a couple of calls to the web service whilst I
watch them in FR. I was alarmed to see that my single request was
costing 32MB of memory (32,438KB) This snapshot was taken at about
the 30th
Hi guys,
I've installed FR 2.0.4 on my dev machine to show you how the
CFINVOIKE will not time out. I ran the sample code in my original post
(this time with a 6 sec timeout just to be different) but it ran for
57s. Here is the Thread Stack Trace taken at about 25th second:
Thread Stack Trace
Well, before you get too excited, be careful that you're not
misunderstanding the report. The memory reported there is NOT for the
current request, but rather for the entire CF server. So that number alone
isn't too meaningful. But if it ROSE by 32 meg when you ran a request, that
would be
OK, so I just looked a little closer, and I see that while both our stack
traces show being in a socketread0, there's more to the story. When my code
is stuck on the CFINVOKE, I see something different from you.
For one thing, notice that at the bottom of my stack trace (below), I see
the line
11 matches
Mail list logo
