perfsonar-user - Re: perfSONAR HEAD fails with new message format
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Sven Ubik <>
- To: <>
- Subject: Re: perfSONAR HEAD fails with new message format
- Date: Thu, 23 Feb 2006 14:23:10 +0100 (CET)
> It's difficult to say where is the problem. In my opinion sometimes the
> best solution in such situation is to remove perfSONAR (including
> Tomcat/Axis) stuff and install/configure it from scratch (following the
> Installation Guide).
We tried to follow installation instructions exactly. Complete
reinstallation is of course time consuming and I would prefer
to find the cause of this error. Is this Java exception meaningful
to somebody?
Regards,
Sven
> > we tried to upgrade to perfSONAR HEAD Java version. It accepts messages
> > in old format with "perfsonar" namespace, but the same request in the
> > new "nmwg" namespace fails:
> >
> > [java] End point:
> > http://localhost:8080/axis/services/MeasurementArchiveService
> > [java] Request file:
> > /usr/local/sonarHEAD/perfsonar/schema/example-instances/sonar/SetupDataRequest-FilterRRDSelect-Cesnet.xml
> > [java] Response file:
> > /usr/local/sonarHEAD/perfsonar/conf/response.xml
> > [java] SOAPClient.makeRequest: General exception encountered by
> > client
> > [java] AxisFault
> > [java] faultCode:
> > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> > [java] faultSubcode:
> > [java] faultString: java.util.EmptyStackException
> >
> >
> > Both messages are attached as request.xml and request2.xml.
> >
> > Can anybody suggest me where can be the problem?
> >
> > Thanks.
> >
> > Regards,
> >
> > Sven Ubik
> >
> > ------------------------------------------------------------------------
> >
> > <perfsonar:message id="msg4"
> > type="SetupDataRequest"
> > timeValue="1127250480"
> > timeType="unix"
> > xmlns:perfsonar="http://perfsonar.org/ns/perfsonar/"
> > xmlns:nmwg="http://ggf.org/ns/nmwg/"
> > xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/"
> >
> > xmlns:rrdfile="http://perfsonar.org/ns/perfsonar/keys/rrdfile/"
> > xmlns:select="http://ggf.org/ns/nmwg/ops/select/">
> >
> > <perfsonar:metadata id="meta1">
> > <perfsonar:subject id="iusub1">
> > <nmwgt:interface>
> > <nmwgt:direction>in</nmwgt:direction>
> > </nmwgt:interface>
> > </perfsonar:subject>
> > <nmwg:characteristic>utilization</nmwg:characteristic>
> > </perfsonar:metadata>
> >
> > <perfsonar:metadata id="meta2">
> > <perfsonar:subject id="iusub2" metadataIdRef="meta1"/>
> > <nmwg:characteristic>select</nmwg:characteristic>
> > <select:parameters id="param1">
> > <select:parameter name="startTime">1134041680</select:parameter>
> > <select:parameter name="endTime">1134041750</select:parameter>
> > <select:parameter
> > name="consolidationFunction">AVERAGE</select:parameter>
> > <select:parameter name="resolution">5</select:parameter>
> > </select:parameters>
> > </perfsonar:metadata>
> >
> > <perfsonar:data id="data1" metadataIdRef="meta2"/>
> >
> > </perfsonar:message>
> >
> > ------------------------------------------------------------------------
> >
> > <?xml version='1.0' encoding='UTF-8'?>
> >
> > <nmwg:message id="msg3"
> > type="SetupDataRequest"
> >
> > xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/"
> > xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"
> > xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/">
> >
> > <!-- Optional message level parameters -->
> > <nmwg:parameters id="msgparam1">
> > <nmwg:parameter name="authToken">Cesnet</nmwg:parameter>
> > <nmwg:parameter name="timeValue">1127250480</nmwg:parameter>
> > <nmwg:parameter name="timeType">unix</nmwg:parameter>
> > </nmwg:parameters>
> >
> > <nmwg:metadata id="meta1">
> > <nmwg:key>
> > <nmwg:parameters id="param1">
> > <nmwg:parameter
> > name="file">/usr/local/sonar/snmp_rrd/cesnet_gn2.rrd</nmwg:parameter>
> > <nmwg:parameter name="dataSource">bytes_in</nmwg:parameter>
> > </nmwg:parameters>
> > </nmwg:key>
> > </nmwg:metadata>
> >
> > <!-- The second metadata is used to filter the results of the first
> > operation,
> > this basically means our 'subject' is the first metadata block,
> > then we
> > apply a parameter block to limit/transform the resulting data. -->
> > <nmwg:metadata id="meta2">
> > <select:subject id="iusub2" metadataIdRef="meta1"/>
> >
> > <select:parameters id="param1">
> > <nmwg:parameter name="startTime">1134041680</nmwg:parameter>
> > <nmwg:parameter name="endTime">1134041750</nmwg:parameter>
> > <nmwg:parameter
> > name="consolidationFunction">AVERAGE</nmwg:parameter>
> > <nmwg:parameter name="resolution">5</nmwg:parameter>
> > </select:parameters>
> >
> > <nmwg:eventType>select</nmwg:eventType>
> >
> > </nmwg:metadata>
> >
> > <!-- This is the specific data we wish to see -->
> > <nmwg:data id="data1" metadataIdRef="meta2"/>
> >
> > </nmwg:message>
- perfSONAR HEAD fails with new message format, Sven Ubik, 02/22/2006
- Re: [I2G2-Proto] perfSONAR HEAD fails with new message format, Roman Lapacz, 02/23/2006
- Re: perfSONAR HEAD fails with new message format, Sven Ubik, 02/23/2006
- Re: [I2G2-Proto] perfSONAR HEAD fails with new message format, Roman Lapacz, 02/23/2006
Archive powered by MHonArc 2.6.16.