James 2.2.0 had a number of memory leak issues. You should upgrade to
2.3.2 or expect to repeatedly restart james 2.2.0 to avoid OOM as much
as possible.

Stefano

2009/12/22 hiroshi satou <[email protected]>:
> Hello all,
> I have James running on my server
> I am working with James 2.2.0.
>
> Email for this server is received via SMTP.
> Spooled once, then processed by spoolmanager.
> Processed email is forwarded via SMTP using RemoteDelivery Mailet.
>
> OutOfMemory exceptions occured when mass amount of emails received.
>
> --- connections-log ---
> ERROR connections: Error handling connection
> java.lang.OutOfMemoryError: Java heap space
> -----------------------
> --- spoolmanager-log ---
> ERROR spoolmanager: Exception in processor <transport>
> java.lang.OutOfMemoryError: Java heap space
> ERROR spoolmanager: An error occurred processing
> Mail1255343041311-17573373 through transport
> ERROR spoolmanager: Result was error
> INFO  spoolmanager: JamesSpoolManager dispose...
> ----------------------
>
> Error occured upon email processing until spoolmanager thread stopped.
> Message "Result was error" or ghost, and "Result was ghost" message
> kept coming out
> in error log until thread stopped.
>
> I was able to contact sender of email from smtpserver-log's mail
> no#(Mail1255343041311-17573373)
> when error or ghost messages were received for particular email.
>
> But I found out I lost some emails which did not show any error or
> ghost message in spoolmanager.
> My assumption is as follows.
> 1.Emails were lost because smtpserver could not spool those particular emails
> 2.Process failed when spoolmanager tried to take emails from spool, resulting
>  to lose emails.
> Looking at what happened in log, I assume 1 is the problem.
>
> I would like to know why emails get lost when JamesSpoolManager is disposed.
> If above problem is considered to be technical error, I would like to know
> if this is fixed in the current version of james,
> if not, then when will this problem be solved.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to