Skip to Content.
Sympa Menu

perfsonar-dev - Re: Problem with SQL-MA ( more problems ...)

Subject: perfsonar development work

List archive

Re: Problem with SQL-MA ( more problems ...)


Chronological Thread 
  • From: Roman Lapacz <>
  • To: maxim <>
  • Cc: "'Jeff W. Boote'" <>, "'Loukik Kudarimoti'" <>, "'Asif, Mohammad'" <>, "'Maciej Glowiak'" <>, , "'Li, Yee-Ting'" <>, "'Nicolas Simar'" <>
  • Subject: Re: Problem with SQL-MA ( more problems ...)
  • Date: Tue, 23 Jan 2007 12:54:22 +0100


Hi Maxim,

today I've tested the service using a request similar to yours... and it worked fine. I checked the database and everything looks good.
For my tests I'm using now RC1 of SQL MA v1.0. Could you use the same version (I assume you are using the snaphot-20060907) and try again the same request?

Loukik, could you test SQL MA as well and its store functionality (if it's possible the same kind of store request)?

I have one general comment: although the service supports multiple data elements in the same store request, I suggest to have only one data per request. In the former case the response is difficult to analyze because the metadata of data is not present (there is just the result code). This is something which is on my TODO list: complete metadata in the response that describes the data stored.


Roman



maxim wrote:
Hi roman,
Sorry for late reply, but I was off on Friday. Here is my message:
-----------
<nmwg:message id="msg4"
type="MeasurementArchiveStoreRequest"
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"; xmlns:nmtl2="http://ggf.org/ns/nmwg/topology/l2/3.0/"; xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/";

xmlns:ifevt="http://ggf.org/ns/nmwg/event/status/base/2.0/";>

<nmwg:metadata id="md2">

<nmwg:subject id="sub1">

<nmtl2:link>
<nmtl2:globalName
type="logical">CERN-FERMI-LHCOPN-001</nmtl2:globalName>

</nmtl2:link>
</nmwg:subject>

<nmwg:eventType>Path.Status</nmwg:eventType>

</nmwg:metadata>


<nmwg:metadata id="md3">

<nmwg:subject id="sub2">

<nmtl2:link>

<nmtl2:globalName
type="logical">CERN-FERMI-LHCOPN-002</nmtl2:globalName>

</nmtl2:link>

</nmwg:subject>

<nmwg:eventType>Path.Status</nmwg:eventType>

</nmwg:metadata>
<nmwg:metadata id="md5">

<nmwg:subject id="sub3">

<nmtl2:link>


<nmtl2:globalName
type="logical">FERMI-IN2P3-IGTMD-001</nmtl2:globalName>

</nmtl2:link>

</nmwg:subject>

<nmwg:eventType>Path.Status</nmwg:eventType>
</nmwg:metadata>
<nmwg:metadata id="md6">

<nmwg:subject id="sub4">

<nmtl2:link>
<nmtl2:globalName
type="logical">FERMI-IN2P3-IGTMD-002</nmtl2:globalName>

</nmtl2:link>


</nmwg:subject>


<nmwg:eventType>Path.Status</nmwg:eventType>



</nmwg:metadata>

<nmwg:metadata id="md8">

<nmwg:subject id="sub5">


<nmtl2:link>

<nmtl2:globalName
type="logical">CERN-FERMI-LHCOPN-001</nmtl2:globalName>

</nmtl2:link>


</nmwg:subject>


<nmwg:eventType>Path.Status</nmwg:eventType>


</nmwg:metadata>


<nmwg:metadata id="md9">


<nmwg:subject id="sub6">


<nmtl2:link>


<nmtl2:globalName
type="logical">CERN-FERMI-LHCOPN-002</nmtl2:globalName>



</nmtl2:link>



</nmwg:subject>



<nmwg:eventType>Path.Status</nmwg:eventType>



</nmwg:metadata>


<nmwg:metadata id="md11">



<nmwg:subject id="sub7">



<nmtl2:link>


<nmtl2:globalName
type="logical">CERN-FERMI-LHCOPN-001</nmtl2:globalName>




</nmtl2:link>



</nmwg:subject>

<nmwg:eventType>Path.Status</nmwg:eventType>


</nmwg:metadata>


<nmwg:metadata id="md12">



<nmwg:subject id="sub8">



<nmtl2:link>


<nmtl2:globalName
type="logical">CERN-FERMI-LHCOPN-002</nmtl2:globalName>


</nmtl2:link>



</nmwg:subject>
<nmwg:eventType>Path.Status</nmwg:eventType>



</nmwg:metadata>

<nmwg:data id="d1" metadataIdRef="md9">
<ifevt:datum timeType="unix" timeValue="1169480101">
<ifevt:stateOper>Up</ifevt:stateOper>
<ifevt:stateAdmin>NormalOperation</ifevt:stateAdmin>
</ifevt:datum>
</nmwg:data>
<nmwg:data id="d2" metadataIdRef="md6">
<ifevt:datum timeType="unix" timeValue="1169480101">
<ifevt:stateOper>Up</ifevt:stateOper>
<ifevt:stateAdmin>NormalOperation</ifevt:stateAdmin>
</ifevt:datum>
</nmwg:data>
<nmwg:data id="d3" metadataIdRef="md11">
<ifevt:datum timeType="unix" timeValue="1169480101">
<ifevt:stateOper>Up</ifevt:stateOper>
<ifevt:stateAdmin>NormalOperation</ifevt:stateAdmin>
</ifevt:datum>
</nmwg:data>
<nmwg:data id="d4" metadataIdRef="md2">
<ifevt:datum timeType="unix" timeValue="1169480101">
<ifevt:stateOper>Up</ifevt:stateOper>
<ifevt:stateAdmin>NormalOperation</ifevt:stateAdmin>
</ifevt:datum>
</nmwg:data>
<nmwg:data id="d5" metadataIdRef="md12">
<ifevt:datum timeType="unix" timeValue="1169480101">
<ifevt:stateOper>Up</ifevt:stateOper>
<ifevt:stateAdmin>NormalOperation</ifevt:stateAdmin>
</ifevt:datum>
</nmwg:data>
<nmwg:data id="d6" metadataIdRef="md3">
<ifevt:datum timeType="unix" timeValue="1169480101">
<ifevt:stateOper>Up</ifevt:stateOper>
<ifevt:stateAdmin>NormalOperation</ifevt:stateAdmin>
</ifevt:datum>
</nmwg:data>
<nmwg:data id="d7" metadataIdRef="md5">
<ifevt:datum timeType="unix" timeValue="1169480101">
<ifevt:stateOper>Up</ifevt:stateOper>
<ifevt:stateAdmin>NormalOperation</ifevt:stateAdmin>
</ifevt:datum>
</nmwg:data>
<nmwg:data id="d8" metadataIdRef="md8">
<ifevt:datum timeType="unix" timeValue="1169480101">
<ifevt:stateOper>Up</ifevt:stateOper>
<ifevt:stateAdmin>NormalOperation</ifevt:stateAdmin>
</ifevt:datum>
</nmwg:data>
</nmwg:message>



-----------
---Maxim










-----Original Message-----
From: Roman Lapacz [mailto:] Sent: Friday, January 19, 2007 5:16 AM
To: maxim
Cc: 'Jeff W. Boote'; 'Loukik Kudarimoti'; 'Asif, Mohammad'; 'Maciej Glowiak'; ; 'Li, Yee-Ting'; 'Nicolas Simar'
Subject: Re: Problem with SQL-MA ( more problems ...)


Could you send the request you used?

Roman


maxim wrote:
one more problem I've encountered. I've compiled my XML
file with MA
store request message inside and tried to store it into the
SQL MA DB
( I've configured it to place unix timestamps).
then I run ant and in response I;ve got "success.ma.write".
But in DB
table I;ve got some strange entries.
First of all, it seems like DB doesn't understand from what
datum the
info came from ( means there is no way to query for the
part of the
global link). Then one of my entries got status_admin cut of, see:

+-----------------------+---------------------+-------------+---------
+-----------------------+---------------------+-------------+------
--+--------------+----------+
| id | time | status_oper
| status_admin
| alarm_id_set | comments |

+-----------------------+---------------------+-------------+---------
+-----------------------+---------------------+-------------+------
--+--------------+----------+
| CERN-FERMI-LHCOPN-002 | 2007-01-18 17:46:45 | Up |
NormalOperation | NULL | NULL |
| CERN-FERMI-LHCOPN-001 | 2007-01-18 17:46:45 | Up |
NormalOperation | NULL | NULL |
| CERN-FERMI-LHCOPN-001 | 2007-01-18 17:46:45 | Up |
NormalOperation | NULL | NULL |
| CERN-FERMI-LHCOPN-001 | 2007-01-18 17:46:45 | Up |
NormalOperation | NULL | NULL |
| CERN-FERMI-LHCOPN-002 | 2007-01-18 17:46:45 | Up
| lOperation
| NULL | NULL |
| CERN-FERMI-LHCOPN-002 | 2007-01-18 17:50:01 | Up |
NormalOperation | NULL | NULL |
| CERN-FERMI-LHCOPN-002 | 2007-01-18 17:50:01 | Up |
NormalOperation | NULL | NULL |
| CERN-FERMI-LHCOPN-001 | 2007-01-18 17:50:01 | Up |
NormalOperation | NULL | NULL |
| CERN-FERMI-LHCOPN-001 | 2007-01-18 17:50:01 | Up |
NormalOperation | NULL | NULL |
| CERN-FERMI-LHCOPN-001 | 2007-01-18 17:50:01 | Up |
NormalOperation | NULL | NULL |
| CERN-FERMI-LHCOPN-002 | 2007-01-18 17:50:01 | Up
| lOperation
| NULL | NULL |

+-----------------------+---------------------+-------------+---------
+-----------------------+---------------------+-------------+------
--+--------------+----------+

Thanks,
Maxim.






Archive powered by MHonArc 2.6.16.

Top of Page