My advice to others - beware of running the ASSP beast in a OVZ container.
I suspect the unreliability (due to exceeding memory) while running ASSP in an OpenVZ virtual is due to the way OVZ treats memory requests. If, under OVZ, Java asks for all of memory and then some, it will survive under Linux but not OVZ. OVZ treats the requested poolsize as in use immediately. OVZ doesn't have swap in the virtuals because it uses the swap as extra memory for the virtuals. Running 2.0.1-5.15: The biggest memory hit I see is rebuilding the SpamDB, about 80 Megs (using BerkelyDB). The spamDB is rebuilt within 2 minutes yet the allocation lingers on longer. I've turned off all automatic rebuilding now, to watch for other memory pool leakage. Long run, I'm going to have to migrate to another server or different anti-spam strategy. I really hate spammers. When I think of all antispam work I've had to do because of them over the last ten years. Alan McNeil -- tired sysadmin working too many timezones ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test