[
https://issues.apache.org/jira/browse/JAMES-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516569
]
OG commented on JAMES-134:
--------------------------
Hi,
I still work with the 2.2 version I made for myself. I see there is james
version 2.3 now, and I wonder if this bug still exist over there too. Thanks.
> Large emails in the spool cause SpoolManager to throw OutOfMemoryError
> ----------------------------------------------------------------------
>
> Key: JAMES-134
> URL: https://issues.apache.org/jira/browse/JAMES-134
> Project: James
> Issue Type: Bug
> Components: SpoolManager & Processors
> Affects Versions: 2.0a3, 2.1, 2.1.3, 2.2.0
> Environment: Operating System: MacOS X
> Platform: Macintosh
> Reporter: Matt Bishop
> Fix For: Trunk
>
> Attachments: JamesMimeMessage.java, 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
