|
1:
Lams-Sakai Integration still
|
|
01/05/06 09:22 AM |
|
Hello, i hope you've all had a nice christmas and new year. I'm back at work now after the christmas break so i'm looking to get LAMS working again.
You may remember previously that i was having problems (incorrect java version etc.) but these new errors appear to be different so i have started a new thread.
I have Sakai v2.0.1 working, and LAMS 1.0.2 working, once i deploy the saka-lams-tool and restart tomcat it spews errors into stdout as follows.
INFO: registering tools from resource: /tools/sakai.lams.xml (2006-01-05 15:03:43,390 Thread-1_org.sakaiproject.util.ToolListener)
WARN: Ignored element 'display-name' as child of 'servlet'. (2006-01-05 15:03:45,468 Thread-1_org.apache.myfaces.webapp.webxml.WebXmlParser)
WARN: Ignored element 'display-name' as child of 'servlet'. (2006-01-05 15:03:45,468 Thread-1_org.apache.myfaces.webapp.webxml.WebXmlParser)
WARN: Ignored element 'display-name' as child of 'servlet'. (2006-01-05 15:03:45,468 Thread-1_org.apache.myfaces.webapp.webxml.WebXmlParser)
WARN: Ignored element 'init-param' as child of 'servlet'. (2006-01-05 15:03:45,468 Thread-1_org.apache.myfaces.webapp.webxml.WebXmlParser)
WARN: Ignored element 'init-param' as child of 'servlet'. (2006-01-05 15:03:45,468 Thread-1_org.apache.myfaces.webapp.webxml.WebXmlParser)
WARN: Ignored element 'init-param' as child of 'servlet'. (2006-01-05 15:03:45,468 Thread-1_org.apache.myfaces.webapp.webxml.WebXmlParser)
ERROR: Could not configure datastore from input stream (2006-01-05 15:04:00,593 Thread-1_net.sf.hibernate.cfg.Configuration)
org.dom4j.DocumentException: hibernate.sourceforge.net Nested exception: hibernate.sourceforge.net
at org.dom4j.io.SAXReader.read(SAXReader.java:358)
at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:287)
at org.springframework.orm.hibernate.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.java:448)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1072)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:343)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:260)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:221)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:145)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:285)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:317)
at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:131)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:224)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:150)
at org.sakaiproject.component.kernel.component.ContextLoader.initWebApplicationContext(ContextLoader.java:72)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:48)
at org.sakaiproject.util.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:59)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4127)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:804)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:693)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:680)
at org.apache.catalina.startup.Catalina.start(Catalina.java:536)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
I'm open to any suggestions and will respond to any help with loving new year wishes.
Thanks in advance
Matt
(full stdout attached (hopefully))
Posted by Matt Saunders
|
|
Attachments:
|
|
2:
Re: Lams-Sakai Integration still
|
In response to 1
|
01/05/06 07:21 PM |
|
Hi Matt,
I've looked at your log file and saw the Nested exception.
Nested exception:
java.net.UnknownHostException: hibernate.sourceforge.net
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
It seems to me it's a problem with resolving the DTD file. I could reproduce the same exceptions when I deploy Sakai-LAMS offline.
Is it possible for you to deploy Sakai-LAMS online? In the mean time I'll try to figure how Sakai could be deploy correctly while it's offline.
Cheers
Anthony
Posted by Anthony Xiao
|
|
|
|
3:
Re: Re: Lams-Sakai Integration still
|
In response to 2
|
01/06/06 05:06 AM |
|
Okay, thanks for looking into this for me.
The sever is connected to my network, however it is firewalled to hell (out of my control) so i need to configure access to resolve the DTD file via a proxy server, or somehow get it to refer to a local copy.
I do not know how i could do either of these, so if anyone can give me suggestions i would be very grateful.
Curiously, if i deploy the sakai-lams-tool from the tomcat manager, i get a connection timed out error, rather than error above.
Thanks.
Matt
Posted by Matt Saunders
|
|
|
|
4:
Re: Re: Re: Lams-Sakai Integration still
|
In response to 3
|
01/06/06 06:11 AM |
|
Okay, i looks like i've got it working, (i've got past that error at least) and can see the menubar via mercury and add lams to a site etc. I'm just going to test for more errors now.
I got it to work by configuring java to connect via a proxy using the following java_opts
Dhttp-.proxyHost=proxyhost -Dhttp.proxyPort=proxyport
I will keep you all informed on my progress, and if you would like me to test any setting if you find a different workaround i would be more than happy to oblige you.
Thanks
Matt
Posted by Matt Saunders
|
|
|
|
5:
Re: Lams-Sakai Integration still
|
In response to 1
|
01/06/06 08:40 AM |
|
I've hit another snag now.
When i have added LAMS to a sakai project site, and clicking LAMS -> Create none of the drop down boxes are populated. Clicking "Create a new sequence" causes a popup window to open, but rather than opening the LAMS editor, it reports a tomcat http500 error.
I will attach stdout and Jboss' server log.
Thanks again.
Matt
Posted by Matt Saunders
|
|
Attachments:
|
|
|
|
7:
Re: Re: Lams-Sakai Integration still
|
In response to 5
|
01/08/06 04:59 PM |
|
Looking at stdout_20060106.log it seems like there is a problem with the webservice
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (500)Internal Server Error
faultActor:
faultNode:
faultDetail:
{}:return code: 500
<HTML><HEAD>
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
</HEAD><BODY>
<H2>The requested URL could not be retrieved</H2>
<HR>
<P>
While trying to retrieve the URL:
<A HREF="http://localhost:8888/lams/services/LearningDesignService">http://localhost:8888/lams/services/LearningDesignService</A>;
<P>
The following error was encountered:
<BLOCKQUOTE>
Unable to determine IP address from host name for
<I>localhost</I>
</BLOCKQUOTE>
</UL>
This means that:
<PRE>
The cache was not able to resolve the hostname presented in the URL.
Check if the address is correct.
</PRE>
</P>
It seems like the hostname "localhost" could not be resolved. I assume it's a problem with the new proxy setting you're using.
Anthony
Posted by Anthony Xiao
|
|
|
|
|
|
8:
Re: Re: Lams-Sakai Integration still
|
In response to 6
|
01/08/06 05:10 PM |
|
This LAMS server.log seems normal. The SAXParseException are caused by disabling DTD in some XML file so LAMS can be run offline.
The ServletException near the end should relate to the Web Service problem in Sakai
Posted by Anthony Xiao
|
|
|
|
9:
Re: Lams-Sakai Integration still
|
In response to 1
|
01/08/06 07:11 PM |
|
>The sever is connected to my network, however it is firewalled to hell (out of my control) so i need to configure access to resolve the DTD file via a proxy server, or somehow get it to refer to a local copy.
>I do not know how i could do either of these, so if anyone can give me suggestions i would be very grateful.
If you have the URL of the DTD, you could host it yourself, putting hibernate.sourceforge.net in your hosts file (/etc/hosts or C:\windows\system32\drivers\etc\hosts) and pointing that to localhost. You'd have to have a web server to host it though, and the path to the DTD would have to be the same.
Another way is if you can modify the actual reference to the DTD itself (the reference, not the DTD), and give it a URL where you've hosted the DTD that's accessible from your machine.
Or you could remove the reference to the DTD, and see if it'll still work. I'm not sure of the consequences of this, but that's what we did in 1.0.2 to get it to work offline.
Posted by Jun-Dir Liew
|
|
|
|
10:
Re: Re: Lams-Sakai Integration still
|
In response to 9
|
01/09/06 04:58 AM |
|
Okay, I have hosted the DTD files myself, and removed the proxy config from java variables. This fixes all previous errors but i've got stuck on another error again.
From within Sakai, clicking create on the LAMS main screen, new page loads and i then get a javascript popup saying "Failed to get list of sequences from the LAMS Server".
Clicking "Create new Sequence" causes new window with yet another 500 error with the URL http://localhost:8888/lams/LoginRequest?uid=admin&method=author&ts=1136804275578&sid=lamssvr1&hash=c2d179569b86df7aad2f263bbc44956e34b5a7de which report the following exception
exception
javax.servlet.ServletException: 1
at org.lamsfoundation.ld.security.web.LoginRequestServlet.doGet(LoginRequestServlet.java:167)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.jboss.web.catalina.security.JBossSecurityMgrRealm.invoke(JBossSecurityMgrRealm.java:227)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:494)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.lamsfoundation.ld.security.valve.LoginRequestValve.invoke(LoginRequestValve.java:85)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:534)
root cause
java.lang.ArrayIndexOutOfBoundsException: 1
at com.webmcq.ld.ws.UserManagementServiceDelegate.getUserDataFromExtServer(UserManagementServiceDelegate.java:375)
at com.webmcq.ld.ws.UserManagementServiceDelegate.getUserDataAndCreateUser(UserManagementServiceDelegate.java:297)
at org.lamsfoundation.ld.security.web.LoginRequestServlet.doGet(LoginRequestServlet.java:165)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.jboss.web.catalina.security.JBossSecurityMgrRealm.invoke(JBossSecurityMgrRealm.java:227)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:494)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.lamsfoundation.ld.security.valve.LoginRequestValve.invoke(LoginRequestValve.java:85)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:534)
Posted by Matt Saunders
|
|
|
|
11:
Re: Lams-Sakai Integration still
|
In response to 10
|
01/09/06 05:14 AM |
|
On the sakai side of things, the following error is reported in stdout.
WARN: Variable 'sequence' could not be resolved. (2006-01-09 10:57:33,828 http-8080-Processor24_org.apache.myfaces.el.VariableResolverImpl)
INFO: org.lamsfoundation.ld.integration.sakai.controller.SequenceActionController@133219b.getSequencesVisibleByCurrentSite() (2006-01-09 10:57:33,828 http-8080-Processor24_org.sakaiproject.component.framework.log.CommonsLogger)
WARN: Variable 'sequence' could not be resolved. (2006-01-09 10:57:33,843 http-8080-Processor24_org.apache.myfaces.el.VariableResolverImpl)
INFO: org.lamsfoundation.ld.integration.sakai.controller.SequenceActionController@133219b.getSequencesVisibleByCurrentSite() (2006-01-09 10:57:35,000 http-8080-Processor24_org.sakaiproject.component.framework.log.CommonsLogger)
WARN: Variable 'sequence' could not be resolved. (2006-01-09 10:57:35,015 http-8080-Processor24_org.apache.myfaces.el.VariableResolverImpl)
WARN: Variable 'sequence' could not be resolved. (2006-01-09 10:57:35,015 http-8080-Processor24_org.apache.myfaces.el.VariableResolverImpl)
WARN: Variable 'sequence' could not be resolved. (2006-01-09 10:57:35,015 http-8080-Processor24_org.apache.myfaces.el.VariableResolverImpl)
INFO: org.lamsfoundation.ld.integration.sakai.controller.SequenceActionController@133219b.processGetCreateForm() (2006-01-09 10:57:35,015 http-8080-Processor24_org.sakaiproject.component.framework.log.CommonsLogger)
WARN: (2006-01-09 10:57:35,937 http-8080-Processor24_org.sakaiproject.util.RequestFilter)
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.rmi.RemoteException: 1; nested exception is:
java.lang.ArrayIndexOutOfBoundsException: 1
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:websrv
java.rmi.RemoteException: 1; nested exception is:
java.lang.ArrayIndexOutOfBoundsException: 1
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at lamsws.LearningDesignServiceSoapBindingStub.getAllLearningDesigns(LearningDesignServiceSoapBindingStub.java:170)
at org.lamsfoundation.ld.integration.sakai.LamsServiceUtil.getAllLearningDesign(LamsServiceUtil.java:63)
at org.lamsfoundation.ld.integration.sakai.servlet.LamsLearningDesignListServlet.doGet(LamsLearningDesignListServlet.java:72)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:528)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)
Posted by Matt Saunders
|
|
|
|
12:
Re: Lams-Sakai Integration still
|
In response to 1
|
01/11/06 06:21 PM |
|
I suspect the user wasn't created correctly due to the Web Service error previously.
Try use a different user to log into Sakai or change the prefix in ext_server_org_map table in the LAMS database. Since LAMS automatically create user as prefix+sakai_username
Anthony
Posted by Anthony Xiao
|
|
