james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxime.LORI...@external.thalesgroup.com
Subject RE: [jira] Resolved: (JAMES-649) error "OutOfMemoryError: JAVA HE AP SPACE" in connections log file when doing a POP TOP for 4000 messages
Date Fri, 06 Oct 2006 08:19:07 GMT

Is it fixed?. In which version of James?.. Have you done a new released candidate?

Actually, Stefano Bagnara (James programmer) asked me to try this code:
     * @see javax.mail.internet.MimeMessage#getRawInputStream()
    public InputStream getRawInputStream() throws MessagingException {
        if (!messageParsed && !isModified() && source != null) {
            InputStream is;
            try {
                is = source.getInputStream();
                // skip the headers.
                new MailHeaders(is);
                return is;
            } catch (IOException e) {
                throw new MessagingException("Unable to read the stream: " + e.getMessage(),
        } else return super.getRawInputStream();
In fact, it works to do a POP TOP with this code but I noticed a bad collateral effect. Actually,
when I launched now 10 000 messages (10 Kos) with NO DELAY between 2 messages, I've got an
error "not possible to listen on port 25" on my program for few of them.

Thank you!

-----Message d'origine-----
De : Norman Maurer (JIRA) [mailto:server-dev@james.apache.org] 
Envoyé : jeudi 5 octobre 2006 21:32
À : maximeloridan@gmail.com
Objet : [jira] Resolved: (JAMES-649) error "OutOfMemoryError: JAVA HEAP SPACE" in connections
log file when doing a POP TOP for 4000 messages

     [ http://issues.apache.org/jira/browse/JAMES-649?page=all ]

Norman Maurer resolved JAMES-649.

    Fix Version/s: Trunk
       Resolution: Fixed

seems to be fixed.

> error "OutOfMemoryError: JAVA HEAP SPACE" in connections log file when doing a POP TOP
for 4000 messages
> --------------------------------------------------------------------------------------------------------
>                 Key: JAMES-649
>                 URL: http://issues.apache.org/jira/browse/JAMES-649
>             Project: James
>          Issue Type: Bug
>          Components: POP3Server
>    Affects Versions: 2.3.0rc4, 2.3.0rc3
>         Environment: Operating system: Windows XP SP2
>            Reporter: maximeloridan
>         Assigned To: Norman Maurer
>            Priority: Critical
>             Fix For: Trunk
> First I reproduced this bug on 2.3.0rc3 and 2.3.0rc4 and it's easy to reproduce it every
> To reproduce it:
> 1/ Start James and create a user "userTest".
> 2/ Send 5000 messages to "userTest"
> 3/ Do a POP TOP to retrieve all the headers of messages from "userTest". To do this,
use a software as Outlook. Configure it to retrieve mail from "userTest" and then click to
retrieve the headers ONLY. DO NOT retrieve all the content of the message, otherwise you will
do a POP RETR which is not a POP TOP! (Nota: the POP RETR is actually working, and I know
that most of the time, people do retrieve all the content of the mail and not only the headers..
But it should work)
> Finally you just have to wait the crash of JAMES. It will appear around the 3500 message...
> The error is written in the log folder in the file connections. The error is OutOfMemoryError:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message