Glad to help. As for more on the metrics, just google "jrun metrics" and you'll find ample resources. It's just a modification to the jrun.xml file. Of course, be careful with that. Be sure to restart CF after you tinker with it so that if there's a problem, you know right away. Various resources (especially the jrun docs discussion of metrics, and comments on those pages) will show more than just the standard jrpp/web threads. You want to look at as many as you can see.
You can also monitor thread use from the OS perspective (using Task Manager or Perfmon on Windows, or their equivalents in *nix), both to monitor and log thread use over time, all of which can help track down problems related to this. HTH. /charlie > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of BarryC > Sent: Monday, April 12, 2010 5:24 PM > To: cfaussie > Subject: [cfaussie] Re: Coldfusion JRun Max handler threads setting > > Thanks Charlie, > Your point about other things such as datasources creating threads is > a good one, and yes our environment does generate a lot of database > connections. > I don't believe it's limited, and I'll find out what the timeouts etc > are. > We are on Coldfusion version 7.03 with JRun 4 updater 6, using JVM 1.4 > (but this is all soon to be updated). > > I'll see if I can monitor threads, do you have any suggestions on how > best to monitor threads with either FusionReactor or JRun logging? > > Thanks > Barry. -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
