Details
-
Bug
-
Resolution: Fixed
-
Critical
-
10.11.4
-
Unit
-
Unknown
-
N/A
-
N/A
-
Description
This means if new mails are sent faster than this queue is handled it can crush the memory. That's what is happening on myxwiki.org for example where we get a OOM and a 350MB PrepareMailQueueManager when notifications mails kicks in.
Ideally a BlockingQueue should be used with a limited (and probably configurable) size. That way when the queue is full whatever want to send a new mail wait a bit just the time for the queue to have room.
Attachments
Issue Links
- causes
-
XWIKI-20518 "IllegalStateException: Queue full" exception in the logs when too many emails to send
- Closed
-
XWIKI-20520 Mail messages can be dropped without errors in the UI if the prepare thread is full
- Closed
- is related to
-
XWIKI-12108 Make mail threads use less CPU
- Open
-
XWIKI-17917 Allow administrators to choose wether emails should be re-sent synchronously or asynchronously
- Closed
- relates to
-
XWIKI-16317 The mail sender module store a lot of useless data in the prepare queue
- Open
-
XWIKI-17825 Listener DatabaseMailResender is trying to resend the stuck emails at each restart creating an OOM and loop that prevents XWiki to properly restart
- Closed