[jira] Commented: (JAMES-134) Large emails in the spool cause SpoolManager to throw OutOfMemoryError

["OG (JIRA)" <se...@james.apache.org>]

    [ https://issues.apache.org/jira/browse/JAMES-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663505#action_12663505 ] 

OG commented on JAMES-134:
--------------------------

Hi.

 I have attached two files today. 

1. A version of the file JamesMimeMessage.java for James  version 2.3.1.  
It is placed at james2.3.1/src/java/org/apache/james/core/JamesMimeMessage.java

2. A script that replace MimeMessage with JamesMimeMessage in src folder, and its subfolders.
it is placed at  james2.3.1/replace.sh, and then you run it , and then you build james. 

That is all. 

Note #1 that it is working in my server for about a month now, and 
Note #2 that I didn't test to much the replace.sh script, so backup 
your source before, and if it work well or not let me know, so I could 
delete this warning or fix the script.


> Large emails in the spool cause SpoolManager to throw OutOfMemoryError
> ----------------------------------------------------------------------
>
>                 Key: JAMES-134
>                 URL: https://issues.apache.org/jira/browse/JAMES-134
>             Project: JAMES Server
>          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, JamesMimeMessage.java, JamesMimeMessage.java, replace.sh, 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org