Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

delete recalcitrant birthday event that finishes before it starts

Vyankatesh January 30, 2019

Every 5 minutes, the Confluence log has an error from a bungled calendar entry, made by heavon only knows whom:

2018-12-07 22:00:00,534 ERROR [team-calendars-worker-2] [extra.calendar3.util.DefaultAsynchronousTaskExecutor] call Exception happens on task execution:
java.lang.IllegalArgumentException: Range start must be before range end
    at net.fortuna.ical4j.model.DateRange.<init>(DateRange.java:71)
    at net.fortuna.ical4j.model.Period.<init>(Period.java:101)

 

Anyone know how to delete the even from DB ? or any suggestion

1 answer

0 votes
Diego
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 4, 2019

Hello there Vyankatesh!

This error has been reported under this bug:

CONFSERVER-57603 | Team Calendar issue while creating Birthday Events

Further, we could try to identify the culprit by doing the following:

  1. Click the Cog Icon > General Configuration
  2. In the left menu bar, search for Logging and profiling
  3. In the class/package name text field enter this: com.atlassian.confluence.extra.calendar3.ical4j
  4. Set it to DEBUG level
  5. After that, wait a bit until the error comes up in the logs
  6. You should be able to retrieve more information about the Calendar Event itself
  7. When you find the Calendar ID, use it with the following query:
    select * from AO_950DC3_TC_REMINDER_SETTINGS where SUB_CALENDAR_ID='calendarID'
  8. Shutdown Confluence
  9. Backup your database, <confluence-home> and <confluence-install> folders
  10. To remove the offending entry, you can try the following:
    delete from AO_950DC3_TC_REMINDER_SETTINGS where SUB_CALENDAR_ID='calendarID'
  11. Start Confluence
  12. Check if the error is still present

IMPORTANT NOTES:

  • If possible, try this procedure on a test environment before applying to Production
  • Always backup your database before changing it
  • Schedule a downtime for your instance before starting this procedure

Also, you can vote and watch for the Bug Report, which is already in the short-term backlog, according to the bug report page. Voting increases the bug visibility and watching will keep you up to date with everything!

Let us know your thoughts!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events