james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danny Angus (JIRA)" <server-...@james.apache.org>
Subject [jira] Updated: (JAMES-134) Large emails in the spool cause SpoolManager to throw OutOfMemoryError
Date Wed, 20 Apr 2005 10:27:23 GMT
     [ http://issues.apache.org/jira/browse/JAMES-134?page=all ]

Danny Angus updated JAMES-134:

       Priority: Major  (was: Blocker)
    Bugzilla Id:   (was: 23906)

This is not a blocker, James is largely at the mercy of JavaMail and JVM for this issue (see
further comments) and there is an effective workaround (increase heap max size) 

> 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
> 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:
For more information on JIRA, see:

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message