[ 
http://issues.apache.org/jira/browse/JAMES-134?page=comments#action_63374 ]
     
Stefano Bagnara commented on JAMES-134:
---------------------------------------

OG: you can (must) specify the maximum message size you will accept from james.

Abount the memory "shrink", again: read a book about windows memory management. 
You don't know what you are talking about. Do a simple test: open an 
application that take a lot of memory, look at the task manager, minimize the 
application. You will see the memory that drastically drop from 200-300MB to 
5-6MB: do you really think this mean the application now uses only 5-6MB and 
has "released" that memory? No.

Please stop looking at Task Manager numbers or read something about memory 
usage indicators: e.g: 
http://www.windowsitpro.com/Windows/Article/ArticleID/41095/41095.html

BTW: this is an issue, and we should discuss better behaviour, but this is not 
blocking: james works. I think that more than 99% of mailservers will not 
accept 1GB email.

BTW2: it is possible that some corporate provides commercial javamail 
implementations with better memory management: look around.


> 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

>
> 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]

Reply via email to