[Building Sakai] URGENT: problem with SCORM 2004 3ed rte in sakai 2.5.4

Neeru Joshi neer.josh25 at gmail.com
Tue Jul 21 22:06:24 PDT 2009




Neeru Joshi wrote:
> 
> Hi,
> 
>    I am attatching the log file which does contains some exception while
> loading the webapp...so that is the culprit alright...but I am hoping that
> can be resolved without building and deploying sakai again. Anyways, owing
> to tight schedule if reqd. I would try builind scorm again. I hope the
> same
> mvn command apply in linux platform too?
> 
> Thanks,
> Neeru
> 
> On Wed, Jul 22, 2009 at 2:18 AM, James Renfro <jlrenfro at ucdavis.edu>
> wrote:
> 
>> I haven't encountered this problem before, but I would suggest that you
>> build sakai (and the scorm player) on the same OS on which you intend to
>> deploy it, using maven.
>>
>> We build and deploy on linux with no issues.
>>
>>
>>
>> Neeru Joshi wrote:
>>
>>> Hi All,
>>>
>>>  I have successfully deployed scorm 2004 3ed rte in sakai 2.5.4 in
>>> windows
>>> platform, but when i take my webapps folder of tomcat & place it in
>>> another
>>> system with linux os, the scorm tool throws an exception. Till now I
>>> have
>>> been trying the same procedure (i.e. copying the webapps folder) in the
>>> target machine, but they all had windows os. Now that I tried the same
>>> on
>>> linux.... sakai works fine but when on clicking the scorm tool in the
>>> side
>>> navigation menubar, i get the following exception in the tool page:
>>>
>>> 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.
>>>
>>> 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:
>>> java.lang.NullPointerException
>>>    at
>>>
>>> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:891)
>>> caused by: java.lang.NullPointerException
>>>    at
>>>
>>> org.sakaiproject.tool.impl.ActiveToolComponent$MyActiveTool.forward(ActiveToolComponent.java:459)
>>>    at
>>>
>>> org.sakaiproject.portal.charon.SkinnableCharonPortal.forwardTool(SkinnableCharonPortal.java:1343)
>>>    at
>>>
>>> org.sakaiproject.portal.charon.handlers.ToolHandler.doTool(ToolHandler.java:163)
>>>    at
>>>
>>> org.sakaiproject.portal.charon.handlers.ToolHandler.doGet(ToolHandler.java:86)
>>>    at
>>>
>>> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:891)
>>>    at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
>>>    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>>>    at
>>>
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>>>    at
>>>
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>>>    at
>>> org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:592)
>>>    at
>>>
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>>>    at
>>>
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>>>    at
>>>
>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>>>    at
>>>
>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
>>>    at
>>>
>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>>>    at
>>>
>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>>>    at
>>>
>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>>>    at
>>>
>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
>>>    at
>>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
>>>    at
>>>
>>> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
>>>    at
>>>
>>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
>>>    at
>>>
>>> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
>>>    at
>>>
>>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
>>>    at java.lang.Thread.run(Thread.java:595)
>>>
>>>
>>> user: admin
>>>
>>> usage-session: cc034c19-b2d9-4721-b2ea-de866e004b6b
>>>
>>> time: Jul 20, 2009 23:17:10
>>>
>>> I am not sure what is going wrong....need some help here..
>>>
>>> Appreciate any help!!
>>> Thanks,
>>> Neeru
>>>
>>>
>>>
>>>
>>
> 
>  
> _______________________________________________
> 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"
> 
http://www.nabble.com/file/p24600131/sakai.log sakai.log 
-- 
View this message in context: http://www.nabble.com/URGENT%3A-problem-with-SCORM-2004-3ed-rte-in-sakai-2.5.4-tp24583565p24600131.html
Sent from the Sakai - Development mailing list archive at Nabble.com.



More information about the sakai-dev mailing list