Forum Problems Installing LAMS: Installation Problem Sakai


 
You may request notification for Installation Problem Sakai.
Search: 

1: Installation Problem Sakai
11/29/05 06:18 PM
[ Reply | Forward ]
I have now installed lams jboss server correctly (I think),
I can log in and I can create an organisation.

I have configured the sakai.propertes as per the installation instructions and

manually added a record into the lams database as per the integration instructions

Once I have added the lams tool via the admin worksite sites tool in sakai, I can access the a lams tool in the mercury worksite.

When I click on the link, after about 2 minutes I see a screen containing some drop downs, which it says are being populated. The my browser says that it cant populate the list.

I get no errors in the LAMS jboss server, but I do see the following error in the catalina.out for sakai

Any Ideas ?






Sakai Catalina.out


WARN: Variable 'sequenceDAO' could not be resolved. (2005-11-29 23:08:00,016 http-8180-Processor4_org.apache.myfaces.el.VariableResolverImpl)
WARN: Variable 'sequence' could not be resolved. (2005-11-29 23:08:00,184 http-8180-Processor4_org.apache.myfaces.el.VariableResolverImpl)
INFO: org.lamsfoundation.ld.integration.sakai.controller.SequenceActionController@11ca33b.getSequencesVisibleByCurrentSite() (2005-11-29 23:08:00,193 http-8180-Processor4_org.sakaiproject.component.framework.log.CommonsLogger)
WARN: Variable 'sequence' could not be resolved. (2005-11-29 23:08:00,263 http-8180-Processor4_org.apache.myfaces.el.VariableResolverImpl)
INFO: org.lamsfoundation.ld.integration.sakai.controller.SequenceActionController@11ca33b.getSequencesVisibleByCurrentSite() (2005-11-29 23:08:19,952 http-8180-Processor5_org.sakaiproject.component.framework.log.CommonsLogger)
WARN: Variable 'sequence' could not be resolved. (2005-11-29 23:08:19,958 http-8180-Processor5_org.apache.myfaces.el.VariableResolverImpl)
WARN: Variable 'sequence' could not be resolved. (2005-11-29 23:08:20,000 http-8180-Processor5_org.apache.myfaces.el.VariableResolverImpl)
WARN: Variable 'sequence' could not be resolved. (2005-11-29 23:08:20,002 http-8180-Processor5_org.apache.myfaces.el.VariableResolverImpl)
INFO: org.lamsfoundation.ld.integration.sakai.controller.SequenceActionController@11ca33b.processGetCreateForm() (2005-11-29 23:08:20,004 http-8180-Processor5_org.sakaiproject.component.framework.log.CommonsLogger)
WARN: (2005-11-29 23:08:28,573 http-8180-Processor4_org.sakaiproject.util.RequestFilter)
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.rmi.RemoteException: Authentication failed!; nested exception is:
org.lamsfoundation.ld.security.AuthenticateException: Authentication failed!
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:bort

java.rmi.RemoteException: Authentication failed!; nested exception is:
org.lamsfoundation.ld.security.AuthenticateException: Authentication failed!
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 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:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
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(Thread.java:534)

Posted by Ian Boston

2: Re: Installation Problem Sakai
In response to 1 11/29/05 06:39 PM
[ Reply | Forward ]
Can you paste the value of lams configuration in your sakai.properties and values of ext_server_org_map in the lams database?

Cheers
Anthony

Posted by Anthony Xiao

3: Re: Installation Problem Sakai
In response to 1 11/29/05 06:45 PM
[ Reply | Forward ]
All is running on the same box called bort

mysql> select * from ext_server_org_map;+-----+---------------+---------------+------------+------------+--------+------------------------------------------------------------------------------------------------------+-------------+----------+-------+
| sid | serverid | serverkey | servername | serverdesc | prefix | userinfo_url | timeout_url | disabled | orgid |
+-----+---------------+---------------+------------+------------+--------+------------------------------------------------------------------------------------------------------+-------------+----------+-------+
| 1 | sakaicamtools | LAMSSERVERKEY | sakai | sakai | sakai | http://bort:8180/sakai-lams-plugin/servlet/UserDataServlet?uid=%username%&ts=%timestamp%&hash=%hash% | 300 | 0 | 0 |
+-----+---------------+---------------+------------+------------+--------+------------------------------------------------------------------------------------------------------+-------------+----------+-------+
1 row in set (0.06 sec)

mysql>

in sakai/sakai.properties

lams.serverId = sakaicamtools
lams.serverKey = LAMSSERVERKEY
lams.serverAddr = http://bort:8280/

Posted by Ian Boston

13: Re: Re: Installation Problem Sakai
In response to 3 11/29/05 07:32 PM
[ Reply | Forward ]
Try remove the extra slash at the end in lams.serverAddr
ie: lams.serverAddr = http://bort:8280

Posted by Anthony Xiao

4: Re: Installation Problem Sakai
In response to 1 11/29/05 06:48 PM
[ Reply | Forward ]
I think I go ordid wrong,

The doc says get it from the user interface when you add it, but I cant find it anywhere on the user interface.....


am I supposed to dig about the db ?

Posted by Ian Boston

6: Re: Installation Problem Sakai
In response to 1 11/29/05 06:56 PM
[ Reply | Forward ]
To get the orgid, see the steps 1-3 at the bottom of post #8 here: http://www.lamscommunity.org/dotlrn/clubs/technicalcommunity/forums/message-view?message%5fid=98924#104867

Posted by Jun-Dir Liew

5: Re: Installation Problem Sakai
In response to 1 11/29/05 06:57 PM
[ Reply | Forward ]
mysql> select * from ext_server_org_map;
+-----+---------------+---------------+------------+------------+--------+------------------------------------------------------------------------------------------------------+-------------+----------+-------+
| sid | serverid | serverkey | servername | serverdesc | prefix | userinfo_url | timeout_url | disabled | orgid |
+-----+---------------+---------------+------------+------------+--------+------------------------------------------------------------------------------------------------------+-------------+----------+-------+
| 1 | sakaicamtools | LAMSSERVERKEY | sakai | sakai | sakai | http://bort:8180/sakai-lams-plugin/servlet/UserDataServlet?uid=%username%&ts=%timestamp%&hash=%hash% | 300 | 0 | 1020 |
+-----+---------------+---------------+------------+------------+--------+------------------------------------------------------------------------------------------------------+-------------+----------+-------+
1 row in set (0.00 sec)

mysql> select * from u_organisation;
+------+-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+----------------+----------------------+---------+
| sid | name | description | parent_org_sid | account_organisation | visible |
+------+-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+----------------+----------------------+---------+
| 1 | All Organisations | This is the root organisation of the home organisation hierarchy. Anyone who really can't belong anywhere else (e.g. admin) belongs here. | NULL | 1 | 1 |
| 2 | Demo Org | Organization for Demonstration | 1 | 1 | 1 |
| 3 | DemoClass | Session Class for Demonstration | NULL | 0 | 1 |
| 1020 | sakaicamtools | Sakai Camtools Test on Bort | NULL | 1 | 1 |



But this still fails.... I have restarted jboss and sakai tomcat just to make certain nothing was cached.

Posted by Ian Boston

9: Re: Re: Installation Problem Sakai
In response to 5 11/29/05 07:12 PM
[ Reply | Forward ]
do you still get the java.rmi.RemoteException or something else?

Posted by Anthony Xiao

12: Re: Re: Re: Installation Problem Sakai
In response to 9 11/29/05 07:27 PM
[ Reply | Forward ]
There are no exceptions anywhere in any of the jboss logs.


If i turn on DEBUG for com.webmcq.ld I get one line in lams.log

2005-11-30 00:20:08,830 [Thread-11] DEBUG com.webmcq.ld.ws.LearningDesignServiceSoapBindingImpl - org.lamsfoundation.ld.security.AuthenticateException: Authentication failed!

Havent tried TRACE yet, does it emit any more debug ? like the url or any of the soap messages

Im doing this over a VPN from home (00:30 at the moment) so debugging the IP level with ethereal is not on at the moment.

Posted by Ian Boston

7: Re: Installation Problem Sakai
In response to 1 11/29/05 06:57 PM
[ Reply | Forward ]
Also, you might want to change your serverid/key now that it's been posted ;)

Posted by Jun-Dir Liew

8: Re: Installation Problem Sakai
In response to 1 11/29/05 07:03 PM
[ Reply | Forward ]
Dont worry, this is a test install behind a firewall, nothing exposed.

Posted by Ian Boston

10: Re: Installation Problem Sakai
In response to 1 11/29/05 07:15 PM
[ Reply | Forward ]
Also Im finding Windows folders being created in the lams jboss folders

eg

D:\jboss-3.0.8_tomcat-4.1.24\server\default\deploy\lams.war\WEB-INF\attachments

has been put in the base directroy where lams home and the jboss folder are. This is where I started the jboss process from.

---- But dont worry about this for the moment,

Posted by Ian Boston

11: Re: Installation Problem Sakai
In response to 1 11/29/05 07:23 PM
[ Reply | Forward ]
I am also getting

10.0.0.197 - - [30/Nov/2005:00:02:04 00] "POST //lams/services/LearningDesignService HTTP/1.0" 500 609
10.0.0.197 - - [30/Nov/2005:00:09:05 00] "POST //lams/services/LearningDesignService HTTP/1.0" 500 609
10.0.0.197 - - [30/Nov/2005:00:09:12 00] "POST //lams/services/LearningDesignService HTTP/1.0" 500 609
10.0.0.197 - - [30/Nov/2005:00:09:14 00] "POST //lams/services/LearningDesignService HTTP/1.0" 500 609

In the Jboss access log file.

Looks like the jboss server is seeing a internal server error when Sakai tries get a list of things from it, not certain what it is trying to get.

I havent added anything to the LAMS server other than the organisation mentioned above.

Posted by Ian Boston

14: Re: Installation Problem Sakai
In response to 1 11/29/05 07:34 PM
[ Reply | Forward ]
TRACE doesnt produce any more information. Even when I turn it on org.apache as well ( I assume that we are using axis in jboss).


Im at a complete loss...

Should I download the source code an manually put debugging statements in ?

Posted by Ian Boston

15: Re: Installation Problem Sakai
In response to 1 11/29/05 07:39 PM
[ Reply | Forward ]
Sorry no


lams.serverId=sakaicamtools
lams.serverKey=LAMSSERVERKEY
lams.serverAddr=http://bort:8280



removing the tailing / has made no difference.

I have to go to sleep, I will pick this up tomorow, If you can think of anything, please post.

Thanks
Ian

Posted by Ian Boston

16: Re: Installation Problem Sakai
In response to 1 11/30/05 01:08 AM
[ Reply | Forward ]
the problem comes from when sakai and LAMS are talking over the webservice. from the log in the first post, LAMS is not authenticating whatever is sent from sakai... the stuff about 'variable "sequence" could not be resolved' is referring to the drop down list of sequences that sakai shows when you click 'create'.

have you tried using 'localhost' or adding the domain name to 'bort' in the configs on both sides?

Posted by Jun-Dir Liew

17: Re: Installation Problem Sakai
In response to 1 11/30/05 03:49 AM
[ Reply | Forward ]
I will try the local host and the full domain name. But this would only be a problem if either side were doing reverse name resolution since the name bort is resolvable and as you can see from the soap traceback, a soap message did make it into the lams server and a soap fault came back.

I will also put ethereal on the box to see what tcp traffic there is between the 2 servers.

If that fails, I will download all the source code and build with extra debugging. Presumably the lams authentication side is fairly obvious ?

Someone from lams foundation asked if they could have remove access to the machine. Unfortunately this is not possible since its behing a firewall and have a restrictive policy on VPN tokens.

I'll post the outcome here as I find out more.

Posted by Ian Boston

19: Re: Re: Installation Problem Sakai
In response to 17 11/30/05 06:30 AM
[ Reply | Forward ]
G'day Ian,

Your ethereal post brought down the LAMS Community! ;-) It seems that the email notifications scripts in .LRN couldnt handle some of the characters and kept hanging .LRN.

At any rate, Tony -the our tech fellow that developed the Sakai integration was the one that contact you today to see if we could get access to your servers and figure out what might be going on.

We'll get into your posting tomorrow morning and try to see if we can come up with some ideas on where this might be failing in your end.

Thanks,

Ernie

Posted by Ernie Ghiglione

22: Re: Re: Re: Installation Problem Sakai
In response to 19 11/30/05 10:23 PM
[ Reply | Forward ]
Ernie,
woops, Im sorry, I didnt mean it to do that, but I couldnt see anywhere obvious to attach the file.

Is the source code avalable for the 1.0.2 lams binary, Im quite happy to investigate the problem and fix it, after all thats what an opensource community is for :)

I cant remember if .LRN cant take inbound email, so I've sent direct as well.

Ian

Posted by Ian Boston

18: Re: Installation Problem Sakai
In response to 1 11/30/05 05:06 AM
[ Reply | Forward ]
Changing from bort to localhost, bort.caret.local makes no difference. They all connect and all get the same 500 internal server error from the Jboss lams server.

Here is a ethereal TCP level dump of the traffic
The important frames are

Frame 1: The browser doing an Ajax Call to the sakai server (btw this doesnt work at all in some browsers)

Frame 2: Sakai contacting Lams
Frame 5: Sakai doing a SOAP post to Lams
Frame 8: Lams responding with Status 500 to sakai
Frame 10: SOAP Fault code from Lams  to Saka (continuation of 8)
Frame 16: Sakai response 200 to browser


It looks like everything is ok as far as the communication is concerned, but the authentication is just not happening.

What Have I got wrong ?

If I am going to fix this myself I am *going* to have to build the lams-jboss server from source.






No.    Time        Source                Destination          Protocol Info
      1 0.000000    172.16.1.1            10.0.0.197            HTTP    GET /sakai-lams-tool/servlet/LamsLearningDesignListServlet?1133343804090 HTTP/1.1

Frame 1 (520 bytes on wire, 520 bytes captured)
Linux cooked capture
Internet Protocol, Src: 172.16.1.1 (172.16.1.1), Dst: 10.0.0.197 (10.0.0.197)
Transmission Control Protocol, Src Port: 64606 (64606), Dst Port: 8180 (8180), Seq: 0, Ack: 0, Len: 452
    Source port: 64606 (64606)
    Destination port: 8180 (8180)
    Sequence number: 0    (relative sequence number)
    Next sequence number: 452    (relative sequence number)
    Acknowledgement number: 0    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0018 (PSH, ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 1... = Push: Set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 65535
    Checksum: 0xc17c [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2774216953, tsecr 2447799749
Hypertext Transfer Protocol
    GET /sakai-lams-tool/servlet/LamsLearningDesignListServlet?1133343804090 HTTP/1.1\r\n
    Host: bort:8180\r\n
    Connection: keep-alive\r\n
    Referer: http://bort:8180/portal/tool/cb78d57e-e72d-43e0-80fd-0999d254c17e/main\r\n
    User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/312.5.1 (KHTML, like Gecko) Safari/312.3.1\r\n
    Accept: */*\r\n
    Accept-Encoding: gzip, deflate\r\n
    Accept-Language: en\r\n
    Cookie: JSESSIONID=80de5675-05b8-489e-0068-7b806fea4ab4.camtools\r\n
    \r\n

No.    Time        Source                Destination          Protocol Info
      2 0.000125    127.0.0.1            127.0.0.1            TCP      57867 > 8280 [SYN] Seq=0 Ack=0 Win=32767 Len=0 MSS=16396 TSV=2447801411 TSER=0 WS=2

Frame 2 (76 bytes on wire, 76 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 57867 (57867), Dst Port: 8280 (8280), Seq: 0, Ack: 0, Len: 0
    Source port: 57867 (57867)
    Destination port: 8280 (8280)
    Sequence number: 0    (relative sequence number)
    Header length: 40 bytes
    Flags: 0x0002 (SYN)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...0 .... = Acknowledgment: Not set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..1. = Syn: Set
        .... ...0 = Fin: Not set
    Window size: 32767
    Checksum: 0x26ae [correct]
    Options: (20 bytes)
        Maximum segment size: 16396 bytes
        SACK permitted
        Time stamp: tsval 2447801411, tsecr 0
        NOP
        Window scale: 2 (multiply by 4)

No.    Time        Source                Destination          Protocol Info
      3 0.000211    127.0.0.1            127.0.0.1            TCP      8280 > 57867 [SYN, ACK] Seq=0 Ack=1 Win=32767 Len=0 MSS=16396 TSV=2447801411 TSER=2447801411 WS=2

Frame 3 (76 bytes on wire, 76 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 8280 (8280), Dst Port: 57867 (57867), Seq: 0, Ack: 1, Len: 0
    Source port: 8280 (8280)
    Destination port: 57867 (57867)
    Sequence number: 0    (relative sequence number)
    Acknowledgement number: 1    (relative ack number)
    Header length: 40 bytes
    Flags: 0x0012 (SYN, ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..1. = Syn: Set
        .... ...0 = Fin: Not set
    Window size: 32767
    Checksum: 0x7804 [correct]
    Options: (20 bytes)
        Maximum segment size: 16396 bytes
        SACK permitted
        Time stamp: tsval 2447801411, tsecr 2447801411
        NOP
        Window scale: 2 (multiply by 4)
    SEQ/ACK analysis
        This is an ACK to the segment in frame: 2
        The RTT to ACK the segment was: 0.000086000 seconds

No.    Time        Source                Destination          Protocol Info
      4 0.000298    127.0.0.1            127.0.0.1            TCP      57867 > 8280 [ACK] Seq=1 Ack=1 Win=32768 Len=0 TSV=2447801411 TSER=2447801411

Frame 4 (68 bytes on wire, 68 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 57867 (57867), Dst Port: 8280 (8280), Seq: 1, Ack: 1, Len: 0
    Source port: 57867 (57867)
    Destination port: 8280 (8280)
    Sequence number: 1    (relative sequence number)
    Acknowledgement number: 1    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0010 (ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 32768 (scaled)
    Checksum: 0x4123 [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447801411, tsecr 2447801411
    SEQ/ACK analysis
        This is an ACK to the segment in frame: 3
        The RTT to ACK the segment was: 0.000087000 seconds

No.    Time        Source                Destination          Protocol Info
      5 0.000387    127.0.0.1            127.0.0.1            HTTP    POST /lams/services/LearningDesignService HTTP/1.0



Frame 5 (1258 bytes on wire, 1258 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 57867 (57867), Dst Port: 8280 (8280), Seq: 1, Ack: 1, Len: 1190
    Source port: 57867 (57867)
    Destination port: 8280 (8280)
    Sequence number: 1    (relative sequence number)
    Next sequence number: 1191    (relative sequence number)
    Acknowledgement number: 1    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0018 (PSH, ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 1... = Push: Set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 32768 (scaled)
    Checksum: 0x02cf [incorrect, should be 0xd363]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447801414, tsecr 2447801411
Hypertext Transfer Protocol
    POST /lams/services/LearningDesignService HTTP/1.0\r\n
    Content-Type: text/xml; charset=utf-8\r\n
    Accept: application/soap+xml, application/dime, multipart/related, text/*\r\n
    User-Agent: Axis/1.3\r\n
    Host: localhost:8280\r\n
    Cache-Control: no-cache\r\n
    Pragma: no-cache\r\n
    SOAPAction: ""\r\n
    Content-Length: 898\r\n
    \r\n
eXtensible Markup Language
    <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <soapenv:Body>
            <ns1:getAllLearningDesigns soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:lamsws">
                <serverId xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
                    sakaicamtools
                    </serverId>
                <datetime xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
                    1133343588745
                    </datetime>
                <hashValue xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
                    ceec19f3e0367001ea8659665aa7db5d26800d0b
                    </hashValue>
                <username xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
                    admin
                    </username>
                </ns1:getAllLearningDesigns>
            </soapenv:Body>
        </soapenv:Envelope>

No.    Time        Source                Destination          Protocol Info
      6 0.000472    127.0.0.1            127.0.0.1            TCP      8280 > 57867 [ACK] Seq=1 Ack=1191 Win=32768 Len=0 TSV=2447801414 TSER=2447801414

Frame 6 (68 bytes on wire, 68 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 8280 (8280), Dst Port: 57867 (57867), Seq: 1, Ack: 1191, Len: 0
    Source port: 8280 (8280)
    Destination port: 57867 (57867)
    Sequence number: 1    (relative sequence number)
    Acknowledgement number: 1191    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0010 (ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 32768 (scaled)
    Checksum: 0x3c77 [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447801414, tsecr 2447801414
    SEQ/ACK analysis
        This is an ACK to the segment in frame: 5
        The RTT to ACK the segment was: 0.000085000 seconds

No.    Time        Source                Destination          Protocol Info
      7 0.000518    10.0.0.197            172.16.1.1            TCP      8180 > 64606 [ACK] Seq=0 Ack=452 Win=2252 Len=0 TSV=2447801415 TSER=2774216953

Frame 7 (68 bytes on wire, 68 bytes captured)
Linux cooked capture
Internet Protocol, Src: 10.0.0.197 (10.0.0.197), Dst: 172.16.1.1 (172.16.1.1)
Transmission Control Protocol, Src Port: 8180 (8180), Dst Port: 64606 (64606), Seq: 0, Ack: 452, Len: 0
    Source port: 8180 (8180)
    Destination port: 64606 (64606)
    Sequence number: 0    (relative sequence number)
    Acknowledgement number: 452    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0010 (ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 2252
    Checksum: 0x67df [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447801415, tsecr 2774216953
    SEQ/ACK analysis
        This is an ACK to the segment in frame: 1
        The RTT to ACK the segment was: 0.000518000 seconds

No.    Time        Source                Destination          Protocol Info
      8 0.742272    127.0.0.1            127.0.0.1            HTTP    HTTP/1.1 500 Internal Server Error

Frame 8 (228 bytes on wire, 228 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 8280 (8280), Dst Port: 57867 (57867), Seq: 1, Ack: 1191, Len: 160
    Source port: 8280 (8280)
    Destination port: 57867 (57867)
    Sequence number: 1    (relative sequence number)
    Next sequence number: 161    (relative sequence number)
    Acknowledgement number: 1191    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0018 (PSH, ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 1... = Push: Set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 32768 (scaled)
    Checksum: 0xfec8 [incorrect, should be 0x428c]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447802575, tsecr 2447801414
Hypertext Transfer Protocol
    HTTP/1.1 500 Internal Server Error\r\n
    Content-Type: text/xml; charset=utf-8\r\n
    Date: Wed, 30 Nov 2005 09:39:49 GMT\r\n
    Server: Apache Coyote/1.0\r\n
    Connection: close\r\n
    \r\n

Frame 9 (68 bytes on wire, 68 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 57867 (57867), Dst Port: 8280 (8280), Seq: 1191, Ack: 161, Len: 0
    Source port: 57867 (57867)
    Destination port: 8280 (8280)
    Sequence number: 1191    (relative sequence number)
    Acknowledgement number: 161    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0010 (ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 32768 (scaled)
    Checksum: 0x32c5 [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447802575, tsecr 2447802575
    SEQ/ACK analysis
        This is an ACK to the segment in frame: 8
        The RTT to ACK the segment was: 0.000052000 seconds

No.    Time        Source                Destination          Protocol Info
    10 0.742467    127.0.0.1            127.0.0.1            HTTP    Continuation or non-HTTP traffic

Frame 10 (677 bytes on wire, 677 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 8280 (8280), Dst Port: 57867 (57867), Seq: 161, Ack: 1191, Len: 609
    Source port: 8280 (8280)
    Destination port: 57867 (57867)
    Sequence number: 161    (relative sequence number)
    Next sequence number: 770    (relative sequence number)
    Acknowledgement number: 1191    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0018 (PSH, ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 1... = Push: Set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 32768 (scaled)
    Checksum: 0x008a [incorrect, should be 0xabb5]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447802576, tsecr 2447802575
Hypertext Transfer Protocol
    Data (609 bytes)

0000  3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31  <?xml version="1
0010  2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74  .0" encoding="ut
0020  66 2d 38 22 3f 3e 3c 73 6f 61 70 65 6e 76 3a 45  f-8"?><soapenv:E
0030  6e 76 65 6c 6f 70 65 20 78 6d 6c 6e 73 3a 73 6f  nvelope xmlns:so
0040  61 70 65 6e 76 3d 22 68 74 74 70 3a 2f 2f 73 63  apenv="http://sc
0050  68 65 6d 61 73 2e 78 6d 6c 73 6f 61 70 2e 6f 72  hemas.xmlsoap.or
0060  67 2f 73 6f 61 70 2f 65 6e 76 65 6c 6f 70 65 2f  g/soap/envelope/
0070  22 20 78 6d 6c 6e 73 3a 78 73 64 3d 22 68 74 74  " xmlns:xsd="htt
0080  70 3a 2f 2f 77 77 77 2e 77 33 2e 6f 72 67 2f 32  p://www.w3.org/2
0090  30 30 31 2f 58 4d 4c 53 63 68 65 6d 61 22 20 78  001/XMLSchema" x
00a0  6d 6c 6e 73 3a 78 73 69 3d 22 68 74 74 70 3a 2f  mlns:xsi="http:/
00b0  2f 77 77 77 2e 77 33 2e 6f 72 67 2f 32 30 30 31  /www.w3.org/2001
00c0  2f 58 4d 4c 53 63 68 65 6d 61 2d 69 6e 73 74 61  /XMLSchema-insta
00d0  6e 63 65 22 3e 3c 73 6f 61 70 65 6e 76 3a 42 6f  nce"><soapenv:Bo
00e0  64 79 3e 3c 73 6f 61 70 65 6e 76 3a 46 61 75 6c  dy><soapenv:Faul
00f0  74 3e 3c 66 61 75 6c 74 63 6f 64 65 3e 73 6f 61  t><faultcode>soa
0100  70 65 6e 76 3a 53 65 72 76 65 72 2e 75 73 65 72  penv:Server.user
0110  45 78 63 65 70 74 69 6f 6e 3c 2f 66 61 75 6c 74  Exception</fault
0120  63 6f 64 65 3e 3c 66 61 75 6c 74 73 74 72 69 6e  code><faultstrin
0130  67 3e 6a 61 76 61 2e 72 6d 69 2e 52 65 6d 6f 74  g>java.rmi.Remot
0140  65 45 78 63 65 70 74 69 6f 6e 3a 20 41 75 74 68  eException: Auth
0150  65 6e 74 69 63 61 74 69 6f 6e 20 66 61 69 6c 65  entication faile
0160  64 21 3b 20 6e 65 73 74 65 64 20 65 78 63 65 70  d!; nested excep
0170  74 69 6f 6e 20 69 73 3a 20 0a 09 6f 72 67 2e 6c  tion is: ..org.l
0180  61 6d 73 66 6f 75 6e 64 61 74 69 6f 6e 2e 6c 64  amsfoundation.ld
0190  2e 73 65 63 75 72 69 74 79 2e 41 75 74 68 65 6e  .security.Authen
01a0  74 69 63 61 74 65 45 78 63 65 70 74 69 6f 6e 3a  ticateException:
01b0  20 41 75 74 68 65 6e 74 69 63 61 74 69 6f 6e 20    Authentication
01c0  66 61 69 6c 65 64 21 3c 2f 66 61 75 6c 74 73 74  failed!</faultst
01d0  72 69 6e 67 3e 3c 64 65 74 61 69 6c 3e 3c 6e 73  ring><detail><ns
01e0  31 3a 68 6f 73 74 6e 61 6d 65 20 78 6d 6c 6e 73  1:hostname xmlns
01f0  3a 6e 73 31 3d 22 68 74 74 70 3a 2f 2f 78 6d 6c  :ns1="http://xml
0200  2e 61 70 61 63 68 65 2e 6f 72 67 2f 61 78 69 73  .apache.org/axis
0210  2f 22 3e 62 6f 72 74 3c 2f 6e 73 31 3a 68 6f 73  /">bort</ns1:hos
0220  74 6e 61 6d 65 3e 3c 2f 64 65 74 61 69 6c 3e 3c  tname></detail><
0230  2f 73 6f 61 70 65 6e 76 3a 46 61 75 6c 74 3e 3c  /soapenv:Fault><
0240  2f 73 6f 61 70 65 6e 76 3a 42 6f 64 79 3e 3c 2f  /soapenv:Body></
0250  73 6f 61 70 65 6e 76 3a 45 6e 76 65 6c 6f 70 65  soapenv:Envelope
0260  3e                                                >

No.    Time        Source                Destination          Protocol Info
    11 0.742492    127.0.0.1            127.0.0.1            TCP      57867 > 8280 [ACK] Seq=1191 Ack=770 Win=32768 Len=0 TSV=2447802576 TSER=2447802576

Frame 11 (68 bytes on wire, 68 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 57867 (57867), Dst Port: 8280 (8280), Seq: 1191, Ack: 770, Len: 0
    Source port: 57867 (57867)
    Destination port: 8280 (8280)
    Sequence number: 1191    (relative sequence number)
    Acknowledgement number: 770    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0010 (ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 32768 (scaled)
    Checksum: 0x3062 [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447802576, tsecr 2447802576
    SEQ/ACK analysis
        This is an ACK to the segment in frame: 10
        The RTT to ACK the segment was: 0.000025000 seconds

No.    Time        Source                Destination          Protocol Info
    12 0.757715    127.0.0.1            127.0.0.1            TCP      8280 > 57867 [FIN, ACK] Seq=770 Ack=1191 Win=32768 Len=0 TSV=2447802591 TSER=2447802576

Frame 12 (68 bytes on wire, 68 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 8280 (8280), Dst Port: 57867 (57867), Seq: 770, Ack: 1191, Len: 0
    Source port: 8280 (8280)
    Destination port: 57867 (57867)
    Sequence number: 770    (relative sequence number)
    Acknowledgement number: 1191    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0011 (FIN, ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...1 = Fin: Set
    Window size: 32768 (scaled)
    Checksum: 0x3052 [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447802591, tsecr 2447802576

No.    Time        Source                Destination          Protocol Info
    13 0.797821    127.0.0.1            127.0.0.1            TCP      57867 > 8280 [ACK] Seq=1191 Ack=771 Win=32768 Len=0 TSV=2447802631 TSER=2447802591


Frame 13 (68 bytes on wire, 68 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 57867 (57867), Dst Port: 8280 (8280), Seq: 1191, Ack: 771, Len: 0
    Source port: 57867 (57867)
    Destination port: 8280 (8280)
    Sequence number: 1191    (relative sequence number)
    Acknowledgement number: 771    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0010 (ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 32768 (scaled)
    Checksum: 0x301b [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447802631, tsecr 2447802591
    SEQ/ACK analysis
        This is an ACK to the segment in frame: 12
        The RTT to ACK the segment was: 0.040106000 seconds

No.    Time        Source                Destination          Protocol Info
    14 0.864615    127.0.0.1            127.0.0.1            TCP      57867 > 8280 [FIN, ACK] Seq=1191 Ack=771 Win=32768 Len=0 TSV=2447802698 TSER=2447802591

Frame 14 (68 bytes on wire, 68 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 57867 (57867), Dst Port: 8280 (8280), Seq: 1191, Ack: 771, Len: 0
    Source port: 57867 (57867)
    Destination port: 8280 (8280)
    Sequence number: 1191    (relative sequence number)
    Acknowledgement number: 771    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0011 (FIN, ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...1 = Fin: Set
    Window size: 32768 (scaled)
    Checksum: 0x2fd7 [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447802698, tsecr 2447802591

No.    Time        Source                Destination          Protocol Info
    15 0.864664    127.0.0.1            127.0.0.1            TCP      8280 > 57867 [ACK] Seq=771 Ack=1192 Win=32768 Len=0 TSV=2447802698 TSER=2447802698
Frame 15 (68 bytes on wire, 68 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 8280 (8280), Dst Port: 57867 (57867), Seq: 771, Ack: 1192, Len: 0
    Source port: 8280 (8280)
    Destination port: 57867 (57867)
    Sequence number: 771    (relative sequence number)
    Acknowledgement number: 1192    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0010 (ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 32768 (scaled)
    Checksum: 0x2f6c [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447802698, tsecr 2447802698
    SEQ/ACK analysis
        This is an ACK to the segment in frame: 14
        The RTT to ACK the segment was: 0.000049000 seconds

No.    Time        Source                Destination          Protocol Info
    16 0.870148    10.0.0.197            172.16.1.1            HTTP    HTTP/1.1 200 OK

Frame 16 (248 bytes on wire, 248 bytes captured)
Linux cooked capture
Internet Protocol, Src: 10.0.0.197 (10.0.0.197), Dst: 172.16.1.1 (172.16.1.1)
Transmission Control Protocol, Src Port: 8180 (8180), Dst Port: 64606 (64606), Seq: 0, Ack: 452, Len: 180
    Source port: 8180 (8180)
    Destination port: 64606 (64606)
    Sequence number: 0    (relative sequence number)
    Next sequence number: 180    (relative sequence number)
    Acknowledgement number: 452    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0018 (PSH, ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 1... = Push: Set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 2252
    Checksum: 0xb8b0 [incorrect, should be 0x5f90]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2447802703, tsecr 2774216953
Hypertext Transfer Protocol
    HTTP/1.1 200 OK\r\n
    Server: Apache-Coyote/1.1\r\n
    Set-Cookie: JSESSIONID=80de5675-05b8-489e-0068-7b806fea4ab4.camtools; Path=/\r\n
    Content-Length: 0\r\n
    Date: Wed, 30 Nov 2005 09:39:50 GMT\r\n
    \r\n


Frame 17 (68 bytes on wire, 68 bytes captured)
Linux cooked capture
Internet Protocol, Src: 172.16.1.1 (172.16.1.1), Dst: 10.0.0.197 (10.0.0.197)
Transmission Control Protocol, Src Port: 64606 (64606), Dst Port: 8180 (8180), Seq: 452, Ack: 180, Len: 0
    Source port: 64606 (64606)
    Destination port: 8180 (8180)
    Sequence number: 452    (relative sequence number)
    Acknowledgement number: 180    (relative ack number)
    Header length: 32 bytes
    Flags: 0x0010 (ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 0... = Push: Not set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 65535
    Checksum: 0x6aec [correct]
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 2774216956, tsecr 2447802703
    SEQ/ACK analysis
        This is an ACK to the segment in frame: 16
        The RTT to ACK the segment was: 0.226718000 seconds

Posted by Ian Boston

20: Re: Re: Installation Problem Sakai
In response to 18 11/30/05 08:48 PM
[ Reply | Forward ]
Hi Ian,

I have found a bug in the Sakai-LAMS plugin. I've drawn up a sequence diagram (see attachment) and realise there is something missing. Between frame 5 and 8 LAMS should invoke the Sakai’s user data callback URL to obtain user data from Sakai. But the url was never invoked. The only reason for this is the hash given to LAMS is wrong.

So I try to verify the hash manually, the hash is constructed as follow;
HASH = SHA1{ lowercase(timestamp + username + serverid + serverkey) }

We can obtain all those variables from the soap call

        <soapenv:Body>
            <ns1:getAllLearningDesigns soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:lamsws">
                <serverId xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
                    sakaicamtools
                    </serverId>
                <datetime xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
                    1133343588745
                    </datetime>
                <hashValue xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
                    ceec19f3e0367001ea8659665aa7db5d26800d0b
                    </hashValue>
                <username xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
                    admin
                    </username>
                </ns1:getAllLearningDesigns>
            </soapenv:Body>
        </soapenv:Envelope>

LAMS will reconstruct the hash value as follow...
SHA1{1133343588745adminsakaicamtoolslamsserverkey} = 2705295bf414faa67056c7e1c732e3a2af7c9d41

But the hash that is sent to LAMS is ceec19f3e0367001ea8659665aa7db5d26800d0b

So the hash generated by the Sakai-LAMS plugin is wrong, it generated the hash as follow...
SHA1{1133343588745adminsakaicamtoolsLAMSSERVERKEY} = ceec19f3e0367001ea8659665aa7db5d26800d0b

The bug is the serverkey wasn’t converted to lowercase.

The good news is, there is a quick fix available simply convert your serverkey to lowercase should fix the problem.

In the mean time we will fix this problem in the plugin.

Sorry for causing you so much trouble.

Posted by Anthony Xiao

Attachments:
21: Re: Re: Installation Problem Sakai
In response to 18 11/30/05 10:09 PM
[ Reply | Forward ]
Ian,

We'll be repackaging the LAMS-Sakai module again to incorporate the changes and make it available shortly. As well as the source code for 1.0.2 since we haven't done that yet.

Thanks,

Ernie

Posted by Ernie Ghiglione

23: Re: Installation Problem Sakai
In response to 1 12/01/05 12:57 AM
[ Reply | Forward ]
The Sakai-LAMS tool has been updated to fix this bug. New versions can be downloaded at http://www.lamsfoundation.org/integration/sakai2/

There was another error in the README.txt file the user data callback URL should be http://<sakai_server>/sakai-lams-tool/servlet/UserDataServlet?uid=%username%&ts=%timestamp%&hash=%hash%

This error is also corrected in the latest README file

So you will need to update the ext_server_org_map in the LAMS database

Anthony

Posted by Anthony Xiao

24: Re: Installation Problem Sakai
In response to 1 12/01/05 05:07 AM
[ Reply | Forward ]
Ok



That has fixed the problem first reported.

1. the server key must be lower case
2. The URL in the readme was incorrect.

For others, here is my sakai.properties and lams db settings
lams is running on http://bort:8280
sakai is running on http://bort:8180

$CATALINA_HOME/sakai/sakai.properties

lams.serverId=sakaicamtools
lams.serverKey=lamsserverkey
lams.serverAddr=http://bort:8280/


mysql> select * from u_organisation;
+------+-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+----------------+----------------------+---------+
| sid | name | description | parent_org_sid | account_organisation | visible |
+------+-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+----------------+----------------------+---------+
| 1 | All Organisations | This is the root organisation of the home organisation hierarchy. Anyone who really can't belong anywhere else (e.g. admin) belongs here. | NULL | 1 | 1 |
| 2 | Demo Org | Organization for Demonstration | 1 | 1 | 1 |
| 3 | DemoClass | Session Class for Demonstration | NULL | 0 | 1 |
| 1020 | sakaicamtools | Sakai Camtools Test on Bort | NULL | 1 | 1 |
+------+-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+----------------+----------------------+---------+
4 rows in set (0.02 sec)

mysql> select * from ext_server_org_map;
+-----+---------------+---------------+------------+------------+--------+----------------------------------------------------------------------------------------------------+-------------+----------+-------+
| sid | serverid | serverkey | servername | serverdesc | prefix | userinfo_url | timeout_url | disabled | orgid |
+-----+---------------+---------------+------------+------------+--------+----------------------------------------------------------------------------------------------------+-------------+----------+-------+
| 1 | sakaicamtools | lamsserverkey | sakai | sakai | sakai | http://bort:8180/sakai-lams-tool/servlet/UserDataServlet?uid=%username%&ts=%timestamp%&hash=%hash% | 300 | 0 | 1020 |
+-----+---------------+---------------+------------+------------+--------+----------------------------------------------------------------------------------------------------+-------------+----------+-------+
1 row in set (0.00 sec)

mysql>



This works :) :) :) Thank you.......


but I've got annother problem now, I'll start a new thread

Posted by Ian Boston

Reply to first post on this page
Back to Problems Installing LAMS