On 5/20/05, Chris Norloff <[EMAIL PROTECTED]> wrote: > It turns out it was probably an explicit garbage collection call from one of > the applications. As soon as I disabled the ability to explicitly call a GC > (just let the JVM manage its own memory) the GC dropped to once an hour on an > idle server.
I'm sure you're aware that explicitly calling GC is a Bad Thing(tm) since it interferes with the JVM's ability to plan and manage GC on its own schedule. I'd probably go as far as recommending that folks disable explicit GC in general to prevent misguided programmers from tanking your systems! (and even some third party Java code might do this so it doesn't even have to be your own code) -- Sean A Corfield -- http://corfield.org/ Team Fusebox -- http://fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:207273 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
