Skip to Content.
Sympa Menu

perfsonar-user - Re: [I2G2-Proto] No match from MA / MA installation

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [I2G2-Proto] No match from MA / MA installation


Chronological Thread 
  • From: Joe Metzger <>
  • To: Sven Ubik <>
  • Cc: ,
  • Subject: Re: [I2G2-Proto] No match from MA / MA installation
  • Date: Wed, 21 Dec 2005 08:34:52 -0600

Sven Ubik wrote:
Hello Joe,

thanks for testing our MA.


Your server is not behaving like the other EGEE versions.


Could you send me the request, which you tried to send to our MA?



Here is a request I am sending to EGEE java perfsonar MAs:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/1999/XMLSchema";
>
<SOAP-ENV:Body
>
<message timeType="unix" xmlns:nmwg="http://ggf.org/ns/nmwg/"; xmlns="http://perfsonar.org/ns/perfsonar/"; id="egee-version-msg-req1" xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/"; type="MetadataKeyRequest" xmlns:select="http://ggf.org/ns/nmwg/ops/select/";
>
<nmwg:metadata id="meta1"
>
<nmwg:eventType
>utilization</nmwg:eventType>
<perfsonar:subject id="subject1"
>
<nmwgt:interface
>
<nmwgt:direction

>in</nmwgt:direction></nmwgt:interface></perfsonar:subject></nmwg:metadata>
<nmwg:data id="outdata1" metadataIdRef="meta1"/></message></SOAP-ENV:Body></SOAP-ENV:Envelope>


Here is your servers response:

<?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><soapenv:Fault><faultcode>soapenv:Server.userException</faultcode><faultstring>org.xml.sax.SAXParseException: The prefix &quot;perfsonar&quot; for element &quot;perfsonar:subject&quot; is not bound.</faultstring><detail><ns1:hostname xmlns:ns1="http://xml.apache.org/axis/";>perfmon1</ns1:hostname></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>


Then I altered my client to explicitly define the perfsonar namespace
(which the other EGEE servers don't care about either way.)
Here is the request:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/1999/XMLSchema";
>
<SOAP-ENV:Body
>
<message timeType="unix" xmlns:nmwg="http://ggf.org/ns/nmwg/"; xmlns="http://perfsonar.org/ns/perfsonar/"; id="egee-version-msg-req1" xmlns:perfsonar="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/"; xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/"; xmlns:select="http://ggf.org/ns/nmwg/ops/select/"; type="MetadataKeyRequest"
>
<nmwg:metadata id="meta1"
>
<nmwg:eventType
>utilization</nmwg:eventType>
<perfsonar:subject id="subject1"
>
<nmwgt:interface
>
<nmwgt:direction

>in</nmwgt:direction></nmwgt:interface></perfsonar:subject></nmwg:metadata>
<nmwg:data id="outdata1" metadataIdRef="meta1"/></message></SOAP-ENV:Body></SOAP-ENV:Envelope>


And your servers response:<?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><soapenv:Fault><faultcode>soapenv:Server.userException</faultcode><faultstring>java.lang.ClassCastException</faultstring><detail><ns1:hostname xmlns:ns1="http://xml.apache.org/axis/";>perfmon1</ns1:hostname></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>



BTW, I am not asserting that these are 'correct' queries. Only that they
are getting the response I want from the other EGEE servers. The correct
response to these queries is a dump of all the 'input' metadata, or about
1/2 of your MA RRD configuration file.




--Joe Metzger









Archive powered by MHonArc 2.6.16.

Top of Page