Low Issue Summary
When there is/are calendars with no working hours selected and there are SLAs using it, and if that project is being used for creating another one with the option "Create with shared configuration" is causing log spamming in atlassian-servicedesk.log. The below warning is seen whenever any servicedesk projects are accessed irrespective of the fact that the calendar in concern is being used by the project or not.
PS: This might not be a concern on an env with fewer JSM projects however one such calendar could cause a thousands of WARNINGS on a production env as it is writing these whenever ANY JSM project is being accessed. It multiplies if there are multiple such calendars.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Create a servicedesk project
- Go to settings and create a new calendar and do not select any day for working hours
- Map the newly created calendar onto any existing SLA or a new one for the same project
- Create a new project with the option "Create with shared configuration" and select the previous project
- Now, ppen any servicedesk project queues and notice that the log file is being spammed
Expected Results
If these warnings are genuine, then print only when the projects in concern are accessed as the calendars are not global. Also, selecting any day is not mandatory on the UI for creating a calendar.
Actual Results
The below exception is thrown in the file: atlassian-servicedesk.log
2023-02-10 15:09:08,262 http-nio-8080-exec-34 WARN admin 909x1265x2 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.258Z + -28800000 2023-02-10 15:09:08,262 http-nio-8080-exec-34 WARN admin 909x1265x2 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.258Z + -14400000 2023-02-10 15:09:08,271 http-nio-8080-exec-34 WARN admin 909x1265x2 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.269Z + -27000000 2023-02-10 15:09:08,271 http-nio-8080-exec-34 WARN admin 909x1265x2 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.269Z + -12600000 2023-02-10 15:09:08,273 http-nio-8080-exec-34 WARN admin 909x1265x2 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.272Z + -28800000 2023-02-10 15:09:08,274 http-nio-8080-exec-34 WARN admin 909x1265x2 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.272Z + -14400000 2023-02-10 15:09:08,394 http-nio-8080-exec-20 WARN admin 909x1273x6 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.389Z + -28800000 2023-02-10 15:09:08,394 http-nio-8080-exec-20 WARN admin 909x1273x6 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.389Z + -14400000 2023-02-10 15:09:08,404 http-nio-8080-exec-20 WARN admin 909x1273x6 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.401Z + -27000000 2023-02-10 15:09:08,404 http-nio-8080-exec-20 WARN admin 909x1273x6 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.401Z + -12600000 2023-02-10 15:09:08,412 http-nio-8080-exec-20 WARN admin 909x1273x6 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.405Z + -28800000 2023-02-10 15:09:08,413 http-nio-8080-exec-20 WARN admin 909x1273x6 1tzq87c 172.29.189.71,172.50.0.2 /rest/servicedesk/1/REF1/webfragments/sections/sd-queues-nav,servicedesk.agent.queues,servicedesk.agent.queues.ungrouped [internal.sla.searcher.SlaClauseQueryGenerationServiceImpl] Calendar 'problematicCalendar' with id 3 did not return a valid target date for 2023-02-10T15:09:08.405Z + -14400000
Workaround
- Remove this calendar from the SLA
OR - Select any working time for the calendar in concern
- If the project is still a JSM project(and not converted as another type), select any day from the GUI, calendar page
- If the project is no more a JSM one,below SQL should help
update "AO_7A2604_WORKINGTIME" set "DISABLED"='false' where "CALENDAR_ID"='3' and "DAY"='monday';
- PS : Replace the calendar-id(s) from the log file
- mentioned in
-
Page Loading...