Michael's email parser stripped out the example included at the end of my
previous message.
But you get the point.
_____
From: Steven Erat [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 29, 2004 4:31 PM
To: CF-Talk
Subject: RE: Debugging CFMX
Brook,
You could generate a thread dump shortly after starting or some other point
in time. A thread dump will show all the ColdFusion requests that came in
via the webserver connector, shown as having a prefix of "jrpp-xx".
http://www.macromedia.com/support/coldfusion/ts/documents/tn18339.htm
<http://www.macromedia.com/support/coldfusion/ts/documents/tn18339.htm>
You could search those individual jrpp stack traces in the thread dump to
see which ones are actively running a cfm template. I typically search for
the string ".cfm:" to match on stack trace lines referencing an active cfm
request. The line number appears just after the colon.
Read the stack trace from that point up to the top line with the jrpp-xx and
then take an educated guess at what's happening in the thread/template by
looking at the classes and methods reported in the stack trace for that
thread. It's a lot of work, but that's how you know what the templates are
doing at any instant. Compare thread dumps taken at short intervals to see
if some jrpp thread id is doing exactly the same thing in each thread dump.
If so, then that's a likely bottleneck.
-------------------------------------------------------------
Example of jrpp threads waiting on a lock:
-------------------------------------------------------------
Sometimes you might see that one or more threads are waiting on lock and
that some other thread actually has the lock.
Snippet of two threads waiting on a lock id 0x1391e818:
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
