Dain Kaplan ha scritto: > The settings i copied over from the 2.2.0 installation are: -Xms1536m > -Xmx2048m
1.5GB and 2GB ?? what kind of use do you make of JAMES ? I manage almost 1 million mail per day with an Xmx set to 300MB, with 2.3.1.... > The system has 4GB of memory, and James is the only thing running on it. > Using the -client option allowed me to confirm that moving the object > store repositories did not resolve the issue (thanks for that, I was > just about to ask about upgrading the jvm) It is a known java issue that for big memories (2-4GB) it has allocation problems during the hotspot compiler thread. If you search google you will find some reference. > Also, when James 2.3.1 starts up and I try to POP, incredibly old (years > old) messages are fetched. Could this be a symptom of why the mails > don't make it to the mailbox properly? Every time i try switching > between the two versions, I am copying the var/ directories from 2.2.0 > to 2.3.1. This probably depends on your POP3 client. It probably make use of some POP3 welcome message informations and when the server changes its welcome message the pop3 client resets its memory about what it already downloaded in past. This "memory" is on the clients side: pop3 does not have a concept or read and unread messages. (it had, once, but it is deprecated and JAMES never supported it). > Is there anything else missing from the config file? I asked before, > but smtphandlerchainConfig isn't needed? smtphandlerchainConfig is not needed. There is a default handlerchain that is used when that config is not included. Currently I can't really understand why it doesn't work: no one ever had a similar problem when upgraded. Double check your config.xml against the official config.xml to understand if you may have forgot some important piece. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
