You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by bu...@apache.org on 2003/10/18 08:55:55 UTC
DO NOT REPLY [Bug 23906] New: -
Large emails in the spool cause SpoolManager to throw OutOfMemoryError
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23906>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23906
Large emails in the spool cause SpoolManager to throw OutOfMemoryError
Summary: Large emails in the spool cause SpoolManager to throw
OutOfMemoryError
Product: James
Version: 2.1
Platform: Macintosh
OS/Version: MacOS X
Status: NEW
Severity: Normal
Priority: Other
Component: SpoolManager & Processors
AssignedTo: server-dev@james.apache.org
ReportedBy: matt@thebishops.org
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org