Inspiring

Question

HELP -- Slow and sometime unresponsive CF Server

Forum|Forum|14 years ago
August 19, 2011
2 replies
4375 views

Please download the attached file to view this post

3612063.doc

This topic has been closed for replies.

Charlie Arehart

Adobe Expert

Zamvil, your snapshot below shows that you have the "start memory tracking" and "start profiling" features of the CF Server Monitor enabled. They could very well be the sole explanation for your poor performance. Yes, sad but true. Not always, but quite often, enabling them can cause more trouble than help. Especially memory tracking (though not always: depends on the nature of your app and traffic), but also sometimes profiling (especially if you have a large amount of query processing, whether in terms of number of queries or count or size/number of returned), since profiling monitors every query.

All that said, just try turning them off, and see if the problem goes away. It may well.

Some people mistakenly assume that their impact is only if the monitor is open. That's very false. When you enabled those options in the monitor, they cause CF to start tracking the data. Some have turned them on, yawned that they were not learning much, closed the monitor, and assumed there was no further impact. Again, very false. They cause impact as long as CF is running. (And in fact, in CF 9.0.1, Adobe added buttons in the CF Admin "Server Monitor Settings" page just so that one could turn them off even if they could not get into the monitor, which sometimes happens when the server is under stress.)

Hope all that's helpful. I will say that it's entirely possible that your problem has some other explanation, too. But that's simple enough to try for now. Let us know how it goes.

/charlie arehart

charlie@carehart.org

Providing fast, remote, on-demand troubleshooting services for CF (and CFBuilder)

More at http://www.carehart.org/consulting

PS The fact that you shared with us the Snapshot below confirms for us you're already using the CF Server Monitor (and Enteprise or Developer). Since Carl asked about that, I just wanted to share the observation for him or any others who may ever be helping someone who offers that. The snapshot can only be created from the server monitor, which is only in Enterprise or Developer. Since the IP addresses of your requests are all from one address, we can't confirm this way if it's Enterprise or not. Hope that's helpful, too.

/Charlie (troubleshooter, carehart. org)

zamvilAuthor

Inspiring

Yes I turned the CF monitor on to see what happening on the server but I already turn it off.

Thanks Charlie, very helpfull your comments.

Charlie Arehart

Adobe Expert

Great. And thanks for your kind regards. That said, I could still read your reply that you "turned off the monitor" to mean merely that you "closed it". Do you mean indeed that you " stopped the memory tracking"? Because your snapshot showed that it was on. If you have more slowness, perhaps it will help to share a new snapshot.

That said, some problems just can't easily discerned by email. It may be far more expedient (and surprisingly relatively inexpensive) to have someone "look over your shoulder" on a short-term consulting basis. Even 15 minutes may be all that's needed to find and resolve your problem. I keep a list of such troubleshooting consultants (which includes myself) at http://www.cf411.com/cfassist. But if you're not in a hurry, try sharing another snapshot (preferably caught when you're having slowness) and perhaps we may see something else.

Hope that's helpful.

/charlie

/Charlie (troubleshooter, carehart. org)

C

carl type3

Brainiac

Hi,

That is Windows server running CF8. Is that CF8.0.0 or CF8.0.1?

Standard or Enterprise licence (I can see Standard install tho could be either licence)?

In short from the dump looks like threads are getting consumed then some queuing is happening:

8 or more threads are busy for more than 60 seconds

Recommend - I would check these logs for error or warning messages at the time and just before the server goes slow. In your case logs are in:

C:\ColdFusion8\runtime\logs\ coldfusion-event.log and coldfusion-out.log.

All the best with that, Carl.

zamvilAuthor

Inspiring

Thanks for your response.

The server is a Win 2008 Server R2 Enterprise with CF8 Enterprise 8.0.1

System Information
Server Details
Server Product	ColdFusion
Version	8,0,1,195765
Edition	Enterprise
Serial Number
Operating System	Windows Vista
OS Version	6.0
Update Level	/C:/ColdFusion8/lib/updates/hf801-71800.jar
JVM Details
Java Version	1.6.0_04

C

carl type3

Brainiac

Hi,

Windows 08 r2 is 64 bit. Is the CF8 Enterprise and JVM also 64 bit or 32 bit?

I would perhaps expect update level to be:

Update Level /c:/ColdFusion8/lib/updates/chf8010004.jar

ie Cumulative Hotfix 4 or more recent security release hf801-00003.jar.

Java Version is 1.6.0_04 which is fair to say very old. CF officially support

up to 1.6.0_24 and 1.6.0_27 is current (as well as 1.7.0 however Java 7 is a matter

for another thread).

Having said all that I doubt your slowness is going to be fixed

alone by updating CF Hotfix levels or JVM. I still think a clue to

the cause of slowness will be in the runtime\logs previously mentioned.

I expect you know when (date and time) it has been slow, so inspect

these logs at those date time stamps for errors or warnings.

CFMonitor is available to you since you have Enterprise. Run CFMon

while the system is working well, become familiar with what a healthy

CFMon looks like. When the system is slow run CFMon again then perhaps

you can compare differences and provide insight as to slowness.

There are other things you can do to check on CF performance eg

verbose JVM logging, CF Metrics logging and thirdparty products however

I expect with the for mentioned logs and CFMon you may have all the tools

you need for now.

HTH, Carl.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded