[ http://issues.apache.org/jira/browse/JAMES-134?page=comments#action_63163 ] Stefano Bagnara commented on JAMES-134: ---------------------------------------
OG "James doesn't give back the RAM that it took.": i think that it is a normal behaviour for the JVM to ask for virtual ram to the OS and never release it. Virtual memory management in modern OS has been implemented in a way that allow this. Windows in particular provides many memory occupation "numbers": what are you looking to? Windows don't provide real RAM usage. It never talks about RAM, instead you will find various "memory" indicators. There are many technical articles on the web that explain how to read those indicators. "It doesn't have to take RAM of the size of the messages that it delivers.": i could agree, but I should say "id depends". If a matcher/mailet has to analyze the message content to manage it then the message will be possibly decoded and more things that will need memory. It is delegated to the OS and the JVM to use the disk when the memory is not enough: the OS does a great job and does not make sense to handle "direct to disk temporary operations" to avoid memory usage. > Large emails in the spool cause SpoolManager to throw OutOfMemoryError > ---------------------------------------------------------------------- > > Key: JAMES-134 > URL: http://issues.apache.org/jira/browse/JAMES-134 > Project: James > Type: Bug > Components: SpoolManager & Processors > Versions: 2.0a3, 2.1, 2.1.3, 2.2.0 > Environment: Operating System: MacOS X > Platform: Macintosh > Reporter: Matt Bishop > Priority: Blocker > > Steps to repro: > 1. Send yourself a very large email (16 megs works for me) > 2. check the SpoolManager log and see this over and over: > ERROR spoolmanager: Exception in JamesSpoolManager.run null > java.lang.OutOfMemoryError > What makes this problem particularly bad is that the spoolmanager doesn't > move on to other > messages but keeps pegging the CPU trying to process this email. To fix it, > I have to shut down > james, delete the email files out of spool and restart. > EXPECTED: email should spool to the user as expected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
