Thanks Stefano,
Are you saying that James stores in memory a key for every email found
for every user in the entire mail db? Wow... I have to keep the 'spam'
messages around a while (several days at least) for my users to give
them time to check for messages incorrectly flagged as spam. I only
have a couple of hundred users. But with the current spam rate, my
inbox table has 175,000 records in it, even with pruning spam records
after a few days. James is storing 175,000 keys in memory for this?
I'm sure there's a reason for that. But it does seem like it's destined
for hitting a memory heap limit sooner or later. Is there any way to
turn that off? How do JAMES installations with thousands of users
handle the memory problem?
Thanks.
Jerry
Jerry M wrote:
I'm getting a ton of Out of Memory errors in James in the connections
log. (James 2.3.1) I've been running James for about 4 years and am
just now beginning to hit these Out Of Memory errors. I don't see any
significant changes to the traffic patterns for mail, other than the
ever-growing spam count. But spam shouldn't be causing OOMs, should
it? This is not a high-traffic server, relatively speaking. And
there are too many OOMs in the log for it to be related to one
excessively large email, etc. The CPU hangs around 10% most of the time.
But regardless of whether I can identify why I'm getting the OOMs, I
have to fix this. Where do you set the heap space allocation for
James? I'm assuming the 'recommended' value is whatever the default
is set to. But obviously that's not working for me. So what is the
maximum safe value I can set the heap size to?
Thanks for a quick response to this so I can get my users back up and
running.
Jerry
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
