[jira] [Commented] (EMAIL-112) DataSourceFileResolverTest fails under IBM JDK 1.4 and 1.6 running on Windows

[Thomas Pummer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/EMAIL-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184461#comment-13184461
 ] 

Thomas Pummer commented on EMAIL-112:
-

this issue isn't ibm JDK related - within my environment it failed too
Environment:
Windows XPx32
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing)

> DataSourceFileResolverTest fails under IBM JDK 1.4 and 1.6 running on Windows
> -
>
> Key: EMAIL-112
> URL: https://issues.apache.org/jira/browse/EMAIL-112
> Project: Commons Email
>  Issue Type: Bug
>Affects Versions: 1.3
> Environment: Windows 7x64,
> java version "1.7.0"
> Java(TM) SE Runtime Environment (build pwi3270-20110906_01)
> IBM J9 VM (build 2.6, JRE 1.7.0 Windows 7 x86-32 20110810_88604 (JIT enabled, 
> AOT enabled)
> J9VM - R26_Java726_GA_20110810_1208_B88592
>Reporter: Peter Kofler
>Priority: Minor
>  Labels: test
> Attachments: EMAIL-112.patch
>
>
> 
> assertNull(toByteArray(dataSourceResolver.resolve("/images/does-not-exist.gif")));
> fails because IBM JDK under Windows assumes "/xxx" NOT to be absolute.

--
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

[Thomas Pummer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/EMAIL-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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