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 "OG (JIRA)" <se...@james.apache.org> on 2006/01/16 11:32:20 UTC
[jira] Updated: (JAMES-134) Large emails in the spool cause
SpoolManager to throw OutOfMemoryError
[ http://issues.apache.org/jira/browse/JAMES-134?page=all ]
OG updated JAMES-134:
---------------------
Attachment: JamesMimeMessage.java
Hi,
This file is meant to show what I mean. It is a class called JamesMimeMessage which subclass MimeMessage and make it use a SharedFileInputStream (which has already existed), instead of the byte array that caused problems with big messages. The idea is
to change James classes that use MimeMessage so that they will use this JamesMimeMessage instead.
PS. Stefano, SharedByteArrayInputStreams uses a byte array under it which is in memory and therefor that couldn't have helped. Also,
I am not sure, but I think that one can't change MimeMessage and publish it, because of the copy rights. For that reason I have suggested
a subclass, since such a solution that may be publishable.
> 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.1, 2.1.3, 2.0a3, 2.2.0
> Environment: Operating System: MacOS X
> Platform: Macintosh
> Reporter: Matt Bishop
> Attachments: JamesMimeMessage.java, TestMemRec.java
>
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org