[
https://issues.apache.org/jira/browse/JAMES-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516641
]
Stefano Bagnara commented on JAMES-134:
---------------------------------------
Currently there is not a complete solution, but the scenario is a bit improved.
We implemented streaming on reading but streaming on writing is still
experimental. In config.xml you can read this:
-------------------
<!-- Set the size threshold for in memory handling of storing
operations -->
<!-- Default is currently 409600000 due to a bug with mysql and
binary stream -->
<!-- currently under investigation. Please change this only if
you know what -->
<!-- you do, this is EXPERIMENTAL -->
<!--
<inMemorySizeLimit>4096</inMemorySizeLimit>
-->
-----------------
You may want to try it with an updated mysql and the latest connector/j then
let us know the result of your tests.
Anyway, as I wrote in the previous comment, there are and there will be cases
of messages fully loaded in memory.
If you use 2.2 you are strongly encouraged to upgrade (even if this bug is not
solved) because of the dozen of bug fixed since 2.2.0.
> 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]
