[jira] [Commented] (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-tabpanelfocusedCommentId=13184121#comment-13184121 ] Siegfried Goeschl commented on EMAIL-110: - 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 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
[jira] [Commented] (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-tabpanelfocusedCommentId=13184124#comment-13184124 ] Siegfried Goeschl commented on EMAIL-110: - One more note - I checked the crashfix.eml using http://tools.ietf.org/tools/msglint/; and http://www.mimevalidator.net/; and both tools are not very happy. While I have never seen an email in the wild passing those tests I still think that something is wrong with the email 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
[jira] [Commented] (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-tabpanelfocusedCommentId=13184333#comment-13184333 ] Thomas Pummer commented on EMAIL-110: - I've checked the RFC 822 http://www.ietf.org/rfc/rfc822.txt In appendix B.2 it is stated that the header has to be seperated from the content by a null line. The eml file given with this issue is missing this seperating line. 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
[jira] [Commented] (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-tabpanelfocusedCommentId=13184396#comment-13184396 ] Sebb commented on EMAIL-110: The current pom no longer depends on abdera or geronimo specs; it depends on javamail and activation. 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
[jira] [Commented] (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-tabpanelfocusedCommentId=13184464#comment-13184464 ] Siegfried Goeschl commented on EMAIL-110: - In order to avoid confusion * commons-email depends on javamail and activation * Stephan Kruger mentioned Abdera dependencies and it could be the Apache Abdera project which uses the geronimo libraries (see http://svn.apache.org/repos/asf/abdera/abdera2/pom.xml) and excludes javamail (see the Axis deps) 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
[jira] [Commented] (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-tabpanelfocusedCommentId=13167074#comment-13167074 ] Maurizio Cucchiara commented on EMAIL-110: -- Honestly, OOME are common in many situations and not necessarily related to commons. Sometimes increase the heap space fixes the problem. But in order to detect your issue, I think it could be helpful if you provide some more details: # what are you trying to achieve? # could you provide a code chunk you are trying to execute? 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 Priority: Blocker Attachments: 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
[jira] [Commented] (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-tabpanelfocusedCommentId=13167119#comment-13167119 ] Stephen Kruger commented on EMAIL-110: -- The test mail I'm trying to send is way too small to warrant increasing heap space. It's definitely a loop termination problem where it's looking for some termination chars which are not there (perhaps erroneously on the part of the test mail). I've attached a simple Eclipse project (Maven based) which recreates the problem entirely. My apologies if the issue turns out to be in one of the other dependencies - since you all use javax.mail it's hard to understand whose implementation is actually being used. 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 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
[jira] [Commented] (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-tabpanelfocusedCommentId=13167148#comment-13167148 ] Maurizio Cucchiara commented on EMAIL-110: -- Good starting point, I can confirm the issue now. But unfortunately, I can also confirm that the issue is not commons-related. In fact reducing the dependencies list, it works as expected. For the sake of completeness, I made a few changes: {code} mail.smtp.host: localhost (Utils.java) mail.smtp.port: 25 To:mcucchiara@localhost (crashfix.eml) {code} Looks like it is abdera-related (removing that dependency make it works) {code:xml|title:pom.xml} dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.10/version scopecompile/scope /dependency dependency groupIdorg.apache.commons/groupId artifactIdcommons-email/artifactId version1.2/version /dependency /dependencies {code} 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 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