Hi Jerry, > I have asked previously about my recurring OutOfMemory errors. I > increased the heap (I think). But I see no change. The following is a > snippit from my connections log (log level set to WARN). I need a brief > education on how James works with these connections. These "IP" > connections and not "DB" connections that it's referring to, right? Is > it normal to be a the max of 30 connections most of the time? Doesn't > seem right to me. I get a lot of inbound spam. But I doubt it's more > than anybody else. I wouldn't think with my small user set that my > inbound mail would certainly be maxing the absolute capability of JAMES. >
I'm not an expert in the internals of James; however I can give some pointers. When a multi-threaded Java app gets an OutOfMemoryError then all bets are off. The only thing you can do is shut it down and start it up again. This is because the thread that ran out of memory isn't necessarily anything to do with the thread that is using big chunks of memory, thus the bit that ran out of memory might not be designed to cope with the error. Therefore you need to adjust the settings so that the OutOfMemoryError never happens. As a starting point: - set a maximum email size - limit the number of threads - ensure that memory size is much bigger than max-email x threads - enable -Dcom.sun.management.jmxremote to allow monitoring via JConsole and see what happens. HTH Martin Filtered by 3BClean from http://www.3bview.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
