james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (JAMES-248) memory management - finalize/nullify after successful delivery of retrieved MailImpl
Date Wed, 14 Apr 2004 10:07:51 GMT
The following comment has been added to this issue:

     Author: Ralf Hauser
    Created: Wed, 14 Apr 2004 3:07 AM
Noel, thx for the insight.
But wouldn't the finalizer immediately be called if the MailImpl object the MailRepository.java's
retrieve() mehtod returns would be actively set to null once it has been transported to the

Perhaps addint the line 
mc = null; 
at the end of the POP3Handler.java's doRETR() method's try-catch block would aready do it?
perhaps do it again in a finally part to this try-catch block?
View this comment:

View the issue:

Here is an overview of the issue:
        Key: JAMES-248
    Summary: memory management - finalize/nullify after successful delivery of retrieved MailImpl
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: James

   Reporter: Ralf Hauser

    Created: Mon, 5 Apr 2004 11:54 AM
    Updated: Wed, 14 Apr 2004 3:07 AM
Environment: Redhat 9

My application required an adaptation of the MailRepository.retrieve() method.
It creates a temporary object on disk and I provided it with a finalize() method for cleaning

The interesting thing is that this finalize is not executed until I shut-down james.
This leads me to the conclusion that even if there was no ties to a disk operation the 
remains in memory long after the MUA has disconnected.

Isn't this kind of a memory leak? After all, attachments to such a MIMEMessage can be 13MB
Shouldn't those objects be null-ed latest after the POP3Handler.doQUIT of a session?

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

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

View raw message