Issue Summary

Team Calendars has a thread pooling mechanism to deal with asynchronous tasks, such as for Calendar Reminders.
Threads in this pool are created with a generic name, such as pool-37-thread-1.

This makes troubleshooting difficult when you need to identify what created these threads.

Steps to Reproduce

1. Install a vanilla instance of Confluence
2. Take a thread dump while Confluence is running.
   • Threads with the name similar to pool-37-thread-1 aren't there.
3. Install Team Calendars and let Confluence run with it for ~10 minutes.
4. Take a thread dump while Confluence is running.

Expected Results

Team Calendars creates threads using a standard name convention.

Actual Results

Team Calendars creates threads with a generic name, such as pool-37-thread-1.

Notes
Enabling debug of com.atlassian.confluence.extra.calendar3.util.DefaultAsynchronousTaskExecutor may show the following entries confirming these threads are used by TC.

2020-11-10 19:00:00,011 DEBUG [pool-37-thread-3] [extra.calendar3.util.DefaultAsynchronousTaskExecutor] lambda$submit$0 Task com.atlassian.confluence.extra.calendar3.reminder.job.CalendarReminderJob$RemindEventForUserCollector@5134002a spent 0ms in queue

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.