Hi Verena,
Verena Venus wrote:
Hi again,
After looking a bit deeper into this I found out that the problem is due to
the outdated request message format, the perfsonarUI plugin sends.
The behaviour of the BWCTL MP in this case is not correct, there should be an
error message indicating the wrong format for the request message. However,
the main problem is the plugin: If it reqeusts with the new format,
everything will be fine and there is no need for a change in the BWCTL MP
itself (for now, the error message has to be built in, but that's a minor
issue).
Unfortunately, I cannot find the sources of the plugin (and cannot ask Roland
for it as he is away).
Nina, do you by accident have the sources of the plugin?
Not by accident :) The sources are available within perfsonarui tree
at https://svn.perfsonar.net/svn/perfsonar/branches/perfsonarui
For BWCTL plugin look into bwctl folder
(src\org\perfsonar\perfsonarui\bwctl). Please commit updates, when
ready.
BEst regards,
Nina
Sorry for the inconveniences.
Regards
Verena
Am Mittwoch, 21. Mai 2008 10:02:40 schrieb Rodesch Christian:
Hi everyone,
As I could not stop to look for this weird error, I did again some
debugging and I found out the following:
I made two distinct measurement with perfSonar UI. The first was a
measurement with the CARNET bwctl MP service as source and our local
bwctl MP "eomer.restena.lu" as destination. The second measurement was a
fully local one, this means between two hosts of our network, to be
precise with detective.restena.lu as source and eomer.restena.lu as
destination. Both tests were 10 second TCP measurements. I logged the
transmitted XML files using wireshark and here's what I discovered:
The request XML is the same except for the differing IP addresses BUT
the response XML files differ:
Here's the one from the first test:
HTTP/1.1 200 OK
Date: Wed, 21 May 2008 07:34:57 GMT
Server: libwww-perl-daemon/1.36
Content-Length: 1459
Content-Type: text/xml; charset=utf-8
SOAPServer: SOAP::Lite/Perl/0.66
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xsi:type="xsd:anyURI">
<nmwg:message
xmlns="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/"
xmlns:nmtm="http://ggf.org/ns/nmwg/time/2.0/"
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"
xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/"
xmlns:perfsonar="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/"
xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/" id="datarq2-1"
type="SetupDataResponse">
<nmwg:metadata id="meta1">
<perfsonar:subject id="subj1">
<nmwgt:endPointPair>
<nmwgt:src type="ipv4" value="193.198.229.166"/>
<nmwgt:dst type="ipv4" value="158.64.56.218"/>
</nmwgt:endPointPair>
</perfsonar:subject>
<nmwg:eventType>bwctl</nmwg:eventType>
<nmwg:parameters id="param1">
<nmwg:parameter xmlns:nmwg="nmwg" name="protocol"
value="TCP"/></nmwg:parameters>
</nmwg:metadata>
<!-- triggers to indicate head of chains -->
<nmwg:data id="1" metadataIdRef="meta1"><nmwg:datum
numBytesUnits="Bytes" value="257960679" numBytes="327237632"
time="1211355281" valueUnits="bits/sec"
duration="0.0-10.1"/></nmwg:data>
</nmwg:message>
</soap:Body></soap:Envelope>
And here's the one from the second test:
HTTP/1.1 200 OK
Date: Wed, 21 May 2008 07:38:04 GMT
Server: libwww-perl-daemon/5.810
Content-Length: 1303
<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>
<nmwg:message
xmlns="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/"
xmlns:nmtm="http://ggf.org/ns/nmwg/time/2.0/"
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"
xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/"
xmlns:perfsonar="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/"
xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/"
xmlns:nmwg1="nmwg" id="datarq2-1" type="SetupDataResponse">
<nmwg:metadata id="meta1">
<subject id="subj1">
<nmwgt:endPointPair>
<nmwgt:src type="ipv4" value="158.64.56.218"/>
<nmwgt:dst type="ipv4" value="158.64.56.116"/>
</nmwgt:endPointPair>
</subject>
<nmwg:eventType>bwctl</nmwg:eventType>
<nmwg:parameters id="param1">
<nmwg1:parameter xmlns:nmwg="nmwg" name="protocol"
value="TCP"/></nmwg:parameters>
</nmwg:metadata>
<!-- triggers to indicate head of chains -->
<nmwg:data id="1" metadataIdRef="meta1"><datum
numBytesUnits="Bytes" timeType="unix" numBytes="64364544"
value="51300766" valueUnits="bits/sec" duration="0.0-10.0"
timeValue="1211355467"/></nmwg:data>
</nmwg:message></soapenv:Body></soapenv:Envelope>
Now what's weird is that the second XML is differing in many point from
the first one:
- the XML header is totally missing
- the Http header is missing the content type: (Content-Type: text/xml;
charset=utf-8 SOAPServer: SOAP::Lite/Perl/0.6)
- Many xml attributes miss their namespaces or the namespaces differ in
the 2 xml files
- The time attributes are totally different, the one files uses a simple
"time" attribute whereas the other uses "timetype" and "timevalue"
So I think this must be the cause of the problem why perfSONAR UI does
show a blank result screen as the parser does not recognize the XML
format of the response message or looks for the wrong attributes
BTW I have installed the BWCTL MP CPAN modules from this url (
http://wiki.perfsonar.net/jra1-wiki/index.php/BWCTL_and_OWAMP_MP)
I hope anybody can fix this, or point me to a newer version.
Regards,
Christian
|
