We are running Jrun version 4. Our plan is to try and tune the JVM -- it needs it. We have folks who specialize in that and will be bringing them on board as soon as they are available.
Immediate problem is whatever is grabbing the memory is not releasing it so the GC can clean it up. Or the GC is ignoring it. Exactly right - uncontrolled queries, etc. can all kill memory. I've been watching the server with FusionReactor, have seen some of those issues, and was able to get them fixed since it was obvious what thread was causing it. Once I know the thread, I can find the developer and get the code changed. What we need is some way to figure out excatly what memory is being allocated where so when the memory pegs and holds (I'm talking forever), we stand a shot at diagnosing the problem -- otherwise it is like finding a needle in a haystick. FusionReactor is SeeFusion on steriods. Problem is that Fusion Reactor monitors memory utilization but does not break it down by individual thread. >From what I've seen of SeeFusion -- i don't think it does either. What I'm trying to accomplish is to enhance our current monitoring capability with another cheap tool so we can identify the immediate issue and possibly prevent it from occuring in the future by making it available on our development instance. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:316910 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
