You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Siegfried Goeschl (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/01/11 16:24:39 UTC
[jira] [Issue Comment Edited] (EMAIL-110)
java.lang.OutOfMemoryError: Java heap space while parsing Mime part
[ https://issues.apache.org/jira/browse/EMAIL-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184121#comment-13184121 ]
Siegfried Goeschl edited comment on EMAIL-110 at 1/11/12 3:23 PM:
------------------------------------------------------------------
Checking the dependency tree using "mvn dependency:tree" allows you to see what is included where. Don't know Abdera but in the past there were known issues when "geronimo-spec-javamail" was included since it did not implement the whole functionality of javamail.
Assuming that Abdera is actually Apache Abdera it includes
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-activation_1.1_spec</artifactId>
<version>1.1</version>
</dependency>
which could cause the problem
was (Author: sgoeschl):
Checking the dependency tree using "mvn dependency:tree" allows you to see what is included where. Don't know Abdera but in the past there were known issues when "geronimo-spec-javamail" was included since it did not implement the whole functionality of javamail
> java.lang.OutOfMemoryError: Java heap space while parsing Mime part
> -------------------------------------------------------------------
>
> Key: EMAIL-110
> URL: https://issues.apache.org/jira/browse/EMAIL-110
> Project: Commons Email
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Windows, Linux
> Reporter: Stephen Kruger
> Assignee: Siegfried Goeschl
> Priority: Blocker
> Attachments: MailBug.zip, crashfix.eml
>
>
> I have a particular eml message which appears to cause a complete memory overflow deep within commons-email.
> A look at the source code does reveal a suspect "while" loop which appears to never exit properly, and should be rewritten so that bad data could not give us this situation.
> The stack trace is :
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:71)
> at javax.mail.internet.MimeMultipart.readTillFirstBoundary(MimeMultipart.java:316)
> at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:186)
> at javax.mail.internet.MimeMultipart.updateHeaders(MimeMultipart.java:130)
> at javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:539)
> at javax.mail.internet.MimeMultipart.updateHeaders(MimeMultipart.java:133)
> at javax.mail.internet.MimeMessage.updateHeaders(MimeMessage.java:1393)
> at javax.mail.internet.MimeMessage.saveChanges(MimeMessage.java:1366)
> at javax.mail.Transport.send(Transport.java:76)
> at javax.mail.Transport.send(Transport.java:48)
> There are many public threads illustrating this same error, but they never pinpoint the code to Commons Email, I'm guessing I'm using the code in a way which exhibits this behaviour :
> http://stackoverflow.com/questions/3177092/uploading-to-blobstore-gives-a-java-heap-outofmemoryerror
> http://stackoverflow.com/questions/2994031/outofmemoryerror-trying-to-upload-to-blobstore-locally
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira