Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Changes to create a repeating event from a single instance not reflected in the dashboard.

Description

To repeat this problem, create an event in the future using the "Schedule" tool. Do not change any of the defaults for frequency: Frequency = Activity occurs once. Click "Save Event". You will now be able to see the event in the Dashboard.

Return to "Schedule" and edit the event so that it repeats Daily and Ends After 3 times. When you return to the Dashboard, the change will not be reflected.

The dashboard seems to be only taking the initial data from the Scheduled event.

Environment

Sakai - TRUNK - Sakai 2.10-SNAPSHOT (Kernel 1.4.0-SNAPSHOT)

Attachments

1

Activity

Show:

Chris Kretler February 14, 2014 at 3:22 PM

Yes, we can create this on ctdev. We see the following error in the log as soon as the event is changed to repeating. It doesn't seem related to the running of the maintenance jobs.

Feb 14 16:18:54 probe [Dashboard Event Processing Thread] WARN org.sakaiproject.dash.dao.impl.DashboardDaoImpl - getRepeatingCalendarItem: Error executing query: class org.springframework.dao.EmptyResultDataAccessException:Incorrect result size: expected 1, actual 0
Feb 14 16:18:54 probe [Dashboard Event Processing Thread] WARN org.sakaiproject.dash.logic.DashboardCommonLogicImpl - Error processing event: EventCopy [context=7a8f7db3-9f4e-45a6-9660-19c2ffb9391f, eventIdentifier=calendar.revise.event.frequency, eventTime=Fri Feb 14 16:18:53 EST 2014, modify=true, priority=2, entityReference=/calendar/event/7a8f7db3-9f4e-45a6-9660-19c2ffb9391f/main/41923549-ba86-40d4-a503-0b8ec35bc5b9, sessionId=4a5369e1-40bf-4384-aaab-4acea4f878ab, userId=b70a79d8-8b43-4f27-ad44-10fb81e74daa]
Feb 14 16:18:54 java.lang.NullPointerException
Feb 14 16:18:54 probe at org.sakaiproject.dash.entity.ScheduleSupport$ScheduleUpdateFrequencyEventProcessor.processEvent(ScheduleSupport.java:853)
Feb 14 16:18:54 probe at org.sakaiproject.dash.logic.DashboardCommonLogicImpl$DashboardEventProcessingThread.run(DashboardCommonLogicImpl.java:735)

Beth Kirschner February 14, 2014 at 2:50 PM

Can we reproduce this?

Chris Kretler January 7, 2014 at 11:47 AM

Confirmed on ctdev. As the original event was not a repeating event, the dashboard did not appear to recognize its changed status when the frequency was modified.

Jim Eng October 13, 2013 at 10:02 AM

Assigning to Zhen for verification of whether the event processor is handling this correctly.

Fixed

Details

Assignee

Reporter

Components

Affects versions

Priority

Created July 10, 2012 at 9:41 AM
Updated November 5, 2014 at 7:34 AM
Resolved February 14, 2014 at 3:24 PM