We seem to be having a real issue with Java using CPU cycles and memory. Tonight I did "top" from the command line and a good share of the time Java was the #1 resource hog. Shortly thereafter the system went down so hard that it was taking about two or three MINUTES to respond to commands typed in the command line. Needless to say, the next command I typed was "shutdown -r now" and when it came back from the reboot, it worked fine. My gut is telling me that Java may have a memory leak, at least that's the theory I want to test. But if I disable Java, will everything come crashing down, or anything? By the way, usually the first thing I notice when the system is acting funny is that Openfire went down. I tried the hint in the thread about adding a memory option of some kind to the line that invokes Openfire (can't recall it offhand) and that keeps it from going down nightly but now it seems like after two or three days it goes down. But even after that, it seems the system just keeps acting flakier and flakier, which makes me wonder if it's really Openfire or something else (like Java). How do I disable Java temporarily? Any thoughts as to why this is happening?