[Building Sakai] Dashboard issues

Geng, Kelly gengx at miamioh.edu
Mon Oct 14 11:44:49 PDT 2013


Thanks Zhen!


On Mon, Oct 14, 2013 at 2:42 PM, Zhen Qian <zqian at umich.edu> wrote:

> Hi, Kelly:
>
> After seeing those errors locally in our production, we have disabled
> dashboard usage. There was no degradation of app server performance, but
> the database trace files increased tremendously. I am afraid that there is
> not much to do with this situation, other than restarting the app servers
> with dashboard process disabled.
>
> We are now actively working on diagnosing and fixing those problems.
>  There are a couple of related JIRAs: DASH-285, DASH-282, DASH-275, and
> DASH-283, et al.. Get dashboard tool up and running again is among our top
> priorities here.
>
> Thanks,
>
> - Zhen
>
>
> On Mon, Oct 14, 2013 at 2:31 PM, Geng, Kelly <gengx at miamioh.edu> wrote:
>
>> Hi Omer,
>>
>> Were you able to resolve this issue? We are seeing the same errors.
>>
>> Thanks,
>> Kelly
>>
>>
>> On Sun, Aug 25, 2013 at 12:10 PM, Omer A Piperdi <omer at rice.edu> wrote:
>>
>>> We have installed Dashboard 1.0.2_RC05 in 2.9.x and keep it in stealth
>>> mode. It is not showing any problem but now school is started and we are
>>> seeing all our Sakai front-ends started processing dashboard processes..
>>> seeing lots of message like this
>>>
>>> 2013-08-25 11:05:47,427  WARN Dashboard Event Processing Thread
>>> org.sakaiproject.calendar.impl.BaseCalendarService - getEntity():
>>> org.sakaiproject.exception.IdUnusedException
>>> id=79ccb156-1871-4c39-adee-8f1fe397723f
>>>
>>> and
>>>
>>> Message: PreparedStatementCallback; SQL [update dash_calendar_item set
>>> calendar_time = ?, calendar_time_label_key = ?, title = ?, entity_ref =
>>> ?, subtype = ?, entity_type = ?, context_id = ?, repeating_event_id = ?,
>>> sequence_num = ? where id = ?]; ORA-00060: deadlock detected while
>>> waiting for resource
>>> ; nested exception is java.sql.SQLException: ORA-00060: deadlock
>>> detected while waiting for resource
>>>
>>>
>>> Restarting the dashboard tools on all Sakai VMs does not solve this
>>> problem.. I see 3 tasks in dash_task_lock table and server_id changes
>>> from time to time..
>>> Any idea or suggestion how to stop this, without a Tomcat restart..
>>>
>>> Thanks
>>> Omer
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>> "unsubscribe"
>>>
>>
>>
>>
>> --
>> Kelly
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>


-- 
Kelly
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131014/f72af815/attachment.html 


More information about the sakai-dev mailing list