Something else to look at is jConsole. It comes with the Java SDK and will let you look at any java app's memory, thread and cpu usage in detail (you'll need to change jrun's JVM args to have it report those stats). Something like SeeFusion will have some more ColdFusion specific stuff (long running pages, queries, etc), but jConsole gets into the memory side of things in more detail (and it's free).
HTH Dominic 2010/1/20 Mark Mandel <mark.man...@gmail.com> > > On Thu, Jan 21, 2010 at 9:51 AM, Ian Skinner <h...@ilsweb.com> wrote: > > > > First of all - having memory tracking enabled in your production server > > is > > > going to make it crawwwwwl ;o) > > > > > > > Well, this is an Intranet web server that has a minimal load probably > > measured in a dozen or two simultaneous requests at most. So while the > > monitor is definatly a load, I beleive the server has plenty of capacity > > to spare in its normal state. > > > > No seriously - don't use it in production, ever. Ever. Ever. > > The thread dumps are pretty straight forward to read - just ignore most of > the the Java gobbley-de-gook. > > Mark > > -- > E: mark.man...@gmail.com > T: http://www.twitter.com/neurotic > W: www.compoundtheory.com > > Hands-on ColdFusion ORM Training @ cf.Objective() 2010 > www.ColdFusionOrmTraining.com/ > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:329868 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4