Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] Re: bug in storage manager?

Subject: perfsonar development work

List archive

Re: [pS-dev] Re: bug in storage manager?


Chronological Thread 
  • From: Roman Lapacz <>
  • To: Loukik Kudarimoti <>
  • Cc:
  • Subject: Re: [pS-dev] Re: bug in storage manager?
  • Date: Mon, 31 Jul 2006 15:19:54 +0200

Roman Lapacz wrote:
Loukik Kudarimoti wrote:
Roman Lapacz wrote:

Loukik Kudarimoti wrote:

Hi Roman,


Hi


The basic installation of SQL MA went ok. I was able to test to retrieve keys using test-1. I then changed the configuration file (xml) and tried to test the service again for test-1.


what exactly you have done and which config file?

I have only replaced the config file in xml db with the attached config file.

I've checked the problem and I see that it happens when the type of xml database connection (see component.ma.xmldb.db_access in conf/service.properties) is http. I've already asked Maciej to check the component responsible for accessing xml database.

The bug is fixed (see svn log email with Maciej's changes). Now http type of xmldb access works fine.

Roman



When you use xmlrpc for component.ma.xmldb.db_access and xmlrpc url for component.ma.xmldb.db_uri then the service works OK.

example:

component.ma.xmldb.db_uri=xmldb:exist://localhost:8087/exist/xmlrpc/db/sqlmaconfig
component.ma.xmldb.db_access=xmlrpc




Maciej and I will try to remove described bug as soon as possible.


Roman



Loukik.



I got the following error message:

<nmwg:data id="resultDescriptionData_for_resultCodeMetadata_0" metadataIdRef="resultCodeMetadata_0">
<nmwg:datum value="MetadataConfigurationStorageManager.fetch: Connection to xml database failed" />
</nmwg:data>

The exception logged was:
2006-07-31 10:42:37,141 DEBUG - MetadataConfigurationStorageManager.fetch: Connection to xml database failed: org.perfsonar.service.commons.exceptions.SystemException: [error.common.storage.xmldb.open]: XQuery by HTTP failed. Could not connect to eXist via pure http, nested exception was: class java.lang.StringIndexOutOfBoundsException : String index out of range: -42

I tried test-2 and same response.

But what surprised me was when I tested using test-3 (just path.status). I get the a success message with the entire xml file!!!!!

Possible reason:
Upon inspection, I noticed that test-1 and test-2 contained messages which would return no matches against the stored xml conifg file. This "no match" will essentially be an empty metadata which might be read by the storage manager as a null pointer caused by db interaction.


If there is no match then you should receive the response with the information that the service does not have needed metadata. I've tested such situation and this should work.


Roman


Loukik.








--

// PSNC, Poland
// phone: (+48 61) 858 20 24
// http://www.man.poznan.pl




Archive powered by MHonArc 2.6.16.

Top of Page