You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/10/15 15:16:33 UTC
[jira] Created: (IMAP-223) Fetching of big MessageRange's can lead
to OOM
Fetching of big MessageRange's can lead to OOM
-----------------------------------------------
Key: IMAP-223
URL: https://issues.apache.org/jira/browse/IMAP-223
Project: JAMES Imap
Issue Type: Bug
Affects Versions: 0.1
Reporter: Norman Maurer
Assignee: Norman Maurer
Fix For: 0.2
Eric reported on the mailinglist that using a fetch 1:* on a mailbox with 10000 messages to fetch the message headers result in heavy memory usage. To make it more lightweight we should fetch messages in batches. This will allow to let the GC kick in
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (IMAP-223) Fetching of big MessageRange's can lead
to OOM
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/IMAP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved IMAP-223.
--------------------------------
Resolution: Fixed
done.. This is now handled in the FetchProcessor, maybe the mailbox would be better..
> Fetching of big MessageRange's can lead to OOM
> -----------------------------------------------
>
> Key: IMAP-223
> URL: https://issues.apache.org/jira/browse/IMAP-223
> Project: JAMES Imap
> Issue Type: Bug
> Affects Versions: 0.1
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 0.2
>
>
> Eric reported on the mailinglist that using a fetch 1:* on a mailbox with 10000 messages to fetch the message headers result in heavy memory usage. To make it more lightweight we should fetch messages in batches. This will allow to let the GC kick in
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (IMAP-223) Fetching of big MessageRange's can lead
to OOM
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/IMAP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer updated IMAP-223:
-------------------------------
Fix Version/s: (was: 0.2)
0.2-M1
> Fetching of big MessageRange's can lead to OOM
> -----------------------------------------------
>
> Key: IMAP-223
> URL: https://issues.apache.org/jira/browse/IMAP-223
> Project: JAMES Imap
> Issue Type: Bug
> Affects Versions: 0.1
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 0.2-M1
>
>
> Eric reported on the mailinglist that using a fetch 1:* on a mailbox with 10000 messages to fetch the message headers result in heavy memory usage. To make it more lightweight we should fetch messages in batches. This will allow to let the GC kick in
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org