Hello,
We have been testing the Better Content Archiving app for our Data Center instance of Confluence but we have not yet managed to fix the email notifications. Regardless of the configuration set, no email notifications are being sent to anyone. I’ve tested it on different spaces and pages, including ones that I’ve created. I’ve selected the option to notify different supervisors, but no email is still being sent out. Email notifications are enabled in the app, and the mail server settings are correct, as other emails from Confluence can be received. There is nothing in the mail queue.
I've contacted the Better Content vendor, Midori, for support but their suggestion was to contact Atlassian support for further explanation related to the mail queue handling.
The app is sending the email notifications without any error, but there are mail queue elated errors that are not related to archiving at all, or are related to an earlier archiving process.
2025-10-16 09:22:41,038 INFO [Long running task: Content Archiving] [atlassian.confluence.event.MonitorableCallerRunsPolicy] rejectedExecution Asynchronous queue is full. The task will be processed synchronously in the current thread instead. We'll print this message every 60 seconds until there's enough space in queue to start processing messages asynchronously again. Executor: [java.util.concurrent.ThreadPoolExecutor@483153fc[Running, pool size = 4, active threads = 4, queued tasks = 307, completed tasks = 63780]]
...
2025-10-16 10:56:07,450 INFO [Long running task: Content Archiving] [atlassian.confluence.event.MonitorableCallerRunsPolicy] rejectedExecution Asynchronous queue is full. The task will be processed synchronously in the current thread instead. We'll print this message every 60 seconds until there's enough space in queue to start processing messages asynchronously again. Executor: [java.util.concurrent.ThreadPoolExecutor@483153fc[Running, pool size = 4, active threads = 4, queued tasks = 373, completed tasks = 181631]]
...
2025-11-05 04:00:00,288 INFO [team-calendars-worker-0] [atlassian.confluence.event.MonitorableCallerRunsPolicy] rejectedExecution Asynchronous queue is full. The task will be processed synchronously in the current thread instead. We'll print this message every 60 seconds until there's enough space in queue to start processing messages asynchronously again. Executor: [java.util.concurrent.ThreadPoolExecutor@483153fc[Running, pool size = 4, active threads = 4, queued tasks = 359, completed tasks = 372820]]
...
2025-11-05 04:05:00,226 INFO [team-calendars-worker-1] [atlassian.confluence.event.MonitorableCallerRunsPolicy] rejectedExecution Asynchronous queue is full. The task will be processed synchronously in the current thread instead. We'll print this message every 60 seconds until there's enough space in queue to start processing messages asynchronously again. Executor: [java.util.concurrent.ThreadPoolExecutor@483153fc[Running, pool size = 4, active threads = 4, queued tasks = 366, completed tasks = 373293]]
...
2025-11-19 04:00:00,286 INFO [team-calendars-worker-2] [atlassian.confluence.event.MonitorableCallerRunsPolicy] rejectedExecution Asynchronous queue is full. The task will be processed synchronously in the current thread instead. We'll print this message every 60 seconds until there's enough space in queue to start processing messages asynchronously again. Executor: [java.util.concurrent.ThreadPoolExecutor@483153fc[Running, pool size = 4, active threads = 2, queued tasks = 376, completed tasks = 423090]]
...
2025-11-19 04:05:00,226 INFO [team-calendars-worker-4] [atlassian.confluence.event.MonitorableCallerRunsPolicy] rejectedExecution Asynchronous queue is full. The task will be processed synchronously in the current thread instead. We'll print this message every 60 seconds until there's enough space in queue to start processing messages asynchronously again. Executor: [java.util.concurrent.ThreadPoolExecutor@483153fc[Running, pool size = 4, active threads = 4, queued tasks = 370, completed tasks = 423531]]
...
2025-12-04 04:00:00,267 INFO [team-calendars-worker-1] [atlassian.confluence.event.MonitorableCallerRunsPolicy] rejectedExecution Asynchronous queue is full. The task will be processed synchronously in the current thread instead. We'll print this message every 60 seconds until there's enough space in queue to start processing messages asynchronously again. Executor: [java.util.concurrent.ThreadPoolExecutor@483153fc[Running, pool size = 4, active threads = 4, queued tasks = 364, completed tasks = 472522]]
...
2025-12-04 04:05:00,245 INFO [team-calendars-worker-1] [atlassian.confluence.event.MonitorableCallerRunsPolicy] rejectedExecution Asynchronous queue is full. The task will be processed synchronously in the current thread instead. We'll print this message every 60 seconds until there's enough space in queue to start processing messages asynchronously again. Executor: [java.util.concurrent.ThreadPoolExecutor@483153fc[Running, pool size = 4, active threads = 4, queued tasks = 355, completed tasks = 473041]]
Thank you for your help – I look forward to any suggestions or solutions!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.