[Building Sakai] [Building SAKAI] Scheduling Tool - Sakai 2.9.3

Jaques Smith jaques at opencollab.co.za
Fri Apr 4 04:54:59 PDT 2014


Hi All,

Yes we seen this, it is https://jira.sakaiproject.org/browse/SAK-25303.
User select the link in the schedule tool to a assignment that is not open
yet.

Jaques



On 1 April 2014 15:12, Neal Caidin <neal.caidin at apereo.org> wrote:

> If so, that looks like it is fixed in Sakai 10, but no merge flag
> currently set for 2.9.
>
> -- Neal
>
>
>   Matthew Jones <matthew at longsight.com>
>  April 1, 2014 at 8:52 AM
> Looks like possibly
> https://jira.sakaiproject.org/browse/SAK-25303
>
>
>
> _______________________________________________
> 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"
>   Kirschner, Beth <bkirschn at umich.edu>
>  April 1, 2014 at 8:23 AM
>
> The student is getting a permission exception -- meaning he/she does not have permission to view/read the assignment:
>
>
> org.sakaiproject.exception.PermissionException
> user=6baf7802-6bfa-4d9d-a35d-8e86c7a53599 lock=asn.read
>
> resource=/assignment/a/ef8d6163-58d1-4474-8ecc-21bb45ce1081/38a0fd8d-36ca-4345-888c-d8e7a012f332
>
>
> The assignment is being referenced from the calendar (looking at thet traceback). I'd look at whether the assignment is open and whether the student is in any sections/groups that might not have access to this assignment.
>
> - Beth
>
> On Apr 1, 2014, at 7:24 AM, Leon Vergottini <leonv at cornerstone.ac.za> <leonv at cornerstone.ac.za> wrote:
>
>
> Dear Neal
>
> No, I have tried from my side on several different environments with no luck.
>
> I also have tried different users, like the admin account, other student accounts, as well as my own equivalent to a student account on the site that the student is experiencing the problems.
>
> I simply cannot reproduce the problem.  I am trying to get hold of the student for more information with no success at the moment.
>
> Kind Regards
> Leon
>
>
> On 04/01/2014 01:16 PM, Neal Caidin wrote:
>
> Hi Leon,
>
> Do you know how to reproduce the bug in the Scheduling tool that triggers the stack trace?
>
> Thanks,
> Neal
>
>
>
> <compose-unknown-contact.jpg>	Leon Vergottini	April 1, 2014 at 6:50 AM
> Hi
>
> I have a student that complains about the message following below.
> Currently it is only one student that is receiving this messages. Is
> this maybe a browser related issue or is there something more sinister
> brewing?
>
> Also, I am kind if new to Sakai, so if anyone is willing to give me
> pointers on how make sense of error logs, it will be greatly appreciated.
>
> Kind Regards
> Leon
>
> Error
> An unexpected error has occurred.
>
>
> Send a bug report
> To send a bug report, describe what you were doing when the problem
> occurred, in the space below, and press the submit button.
>
>
> ----------------------------------------------------------------------------
> -------------------------------------------Dear Neal
>
> No, I have tried from my side on several different environments with no luck.
>
> I also have tried different users, like the admin account, other student accounts, as well as my own equivalent to a student account on the site that the student is experiencing the problems.
>
> I simply cannot reproduce the problem.---------------------------------
> --------------
>
> Recovery
> To recover from this error without sending in a bug report, please do the
> following:
>
> Press the Logout button above to logout.
> Close your browser to assure a clean start.
> Re-open your browser and start again.
>
>
> Technical Details
> This information will automatically be included in your bug report.
>
> org.sakaiproject.portal.api.PortalHandlerException:
> org.sakaiproject.tool.api.ToolException:
> java.lang.reflect.InvocationTargetException
> at
> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPo
> rtal.java:894)
> caused by: org.sakaiproject.tool.api.ToolException:
> java.lang.reflect.InvocationTargetException
> at org.sakaiproject.cheftool.ToolServlet.doGet(ToolServlet.java:236)
> caused by: java.lang.reflect.InvocationTargetException
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> )
> caused by: java.lang.SecurityException:
> org.sakaiproject.exception.PermissionException
> user=6baf7802-6bfa-4d9d-a35d-8e86c7a53599 lock=asn.read
> resource=/assignment/a/ef8d6163-58d1-4474-8ecc-21bb45ce1081/38a0fd8d-36ca-43
> 45-888c-d8e7a012f332 (rethrown)
> at
> org.sakaiproject.entitybroker.rest.EntityRESTProviderBase.handleCustomAction
> Execution(EntityRESTProviderBase.java:118)
> caused by: java.lang.SecurityException:
> org.sakaiproject.exception.PermissionException
> user=6baf7802-6bfa-4d9d-a35d-8e86c7a53599 lock=asn.read
> resource=/assignment/a/ef8d6163-58d1-4474-8ecc-21bb45ce1081/38a0fd8d-36ca-43
> 45-888c-d8e7a012f332
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> caused by: org.sakaiproject.exception.PermissionException
> user=6baf7802-6bfa-4d9d-a35d-8e86c7a53599 lock=asn.read
> resource=/assignment/a/ef8d6163-58d1-4474-8ecc-21bb45ce1081/38a0fd8d-36ca-43
> 45-888c-d8e7a012f332
> at
> org.sakaiproject.assignment.impl.BaseAssignmentService.checkAssignmentAccess
> ibleForUser(BaseAssignmentService.java:1091)
> at
> org.sakaiproject.assignment.impl.BaseAssignmentService.getAssignment(BaseAss
> ignmentService.java:1014)
> at
> org.sakaiproject.assignment.impl.AssignmentEntityProviderImpl.getAssignmentD
> eepLink(AssignmentEntityProviderImpl.java:680)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> )
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> ..java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.sakaiproject.entitybroker.rest.EntityActionsManager.handleCustomActionEx
> ecution(EntityActionsManager.java:206)
> at
> org.sakaiproject.entitybroker.rest.EntityRESTProviderBase.handleCustomAction
> Execution(EntityRESTProviderBase.java:118)
> at
> org.sakaiproject.entitybroker.impl.EntityBrokerImpl.executeCustomAction(Enti
> tyBrokerImpl.java:389)
> at
> org.sakaiproject.calendar.tool.CalendarAction.buildDescriptionContext(Calend
> arAction.java:2905)
> at
> org.sakaiproject.calendar.tool.CalendarAction.buildMainPanelContext(Calendar
> Action.java:2382)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> )
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> ..java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.sakaiproject.cheftool.VelocityPortletPaneledAction.toolModeDispatch(Velo
> cityPortletPaneledAction.java:441)
> at org.sakaiproject.cheftool.ToolServlet.doGet(ToolServlet.java:236)
> at
> org.sakaiproject.cheftool.VelocityPortletPaneledAction.doGet(VelocityPortlet
> PaneledAction.java:1168)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
> at
> org.sakaiproject.vm.ComponentServlet.service(ComponentServlet.java:56)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
> FilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
> ain.java:210)
> at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:634)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
> FilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
> ain.java:210)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.
> java:749)
> at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDis
> patcher.java:487)
> at
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch
> er.java:379)
> at
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher
> ..java:339)
> at
> org.sakaiproject.tool.impl.ActiveToolComponent$MyActiveTool.forward(ActiveTo
> olComponent.java:511)
> at
> org.sakaiproject.portal.charon.SkinnableCharonPortal.forwardTool(SkinnableCh
> aronPortal.java:1483)
> at
> org.sakaiproject.portal.charon.handlers.ToolHandler.doTool(ToolHandler.java:
> 213)
> at
> org.sakaiproject.portal.charon.handlers.ToolHandler.doGet(ToolHandler.java:9
> 6)
> at
> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPo
> rtal.java:894)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
> FilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
> ain.java:210)
> at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:695)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
> FilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
> ain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve..ja
> va:222)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve..ja
> va:123)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase
> ..java:502)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171
> )
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100
> )
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
> :118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(Abstrac
> tProtocol.java:603)
> at
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:
> 310)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor..ja
> va:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
> 18)
> at java.lang.Thread.run(Thread.java:662)
>
>
> user: 6baf7802-6bfa-4d9d-a35d-8e86c7a53599
>
> usage-session: b1d6dc14-c4f3-4175-882a-f6230f25a4a6
>
> time: Mar 30, 2014 11:33:02
>
> ----------------------------------------------------------------------------
> ----------------------------------------------------------------------------
> --------------
>
> _______________________________________________
> sakai-dev mailing listsakai-dev at collab.sakaiproject.orghttp://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundationneal.caidin at apereo.org
> Skype me! (but let me know in advance for the first interaction) - nealkdin
>
>
> _______________________________________________
> sakai-dev mailing listsakai-dev at collab.sakaiproject.orghttp://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
>   Leon Vergottini <leonv at cornerstone.ac.za>
>  April 1, 2014 at 7:24 AM
>  Dear Neal
>
> No, I have tried from my side on several different environments with no
> luck.
>
> I also have tried different users, like the admin account, other student
> accounts, as well as my own equivalent to a student account on the site
> that the student is experiencing the problems.
>
> I simply cannot reproduce the problem.  I am trying to get hold of the
> student for more information with no success at the moment.
>
> Kind Regards
> Leon
>
>
> On 04/01/2014 01:16 PM, Neal Caidin wrote:
>
>   Neal Caidin <neal.caidin at apereo.org>
>  April 1, 2014 at 7:16 AM
>  Hi Leon,
>
> Do you know how to reproduce the bug in the Scheduling tool that triggers
> the stack trace?
>
> Thanks,
> Neal
>
>
>
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org
> Skype me! (but let me know in advance for the first interaction) - nealkdin
>
>
> _______________________________________________
> 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"
>

-- 

------------------------------
See OpenCollab email disclaimer at 
http://www.opencollab.co.za/email-disclaimer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140404/6069b95e/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140404/6069b95e/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1196 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140404/6069b95e/attachment-0001.jpg 


More information about the sakai-dev mailing list