Skip to Content.
Sympa Menu

perfsonar-dev - [Fwd: bug in storage manager?]

Subject: perfsonar development work

List archive

[Fwd: bug in storage manager?]


Chronological Thread 
  • From: Loukik Kudarimoti <>
  • To:
  • Subject: [Fwd: bug in storage manager?]
  • Date: Mon, 31 Jul 2006 10:52:49 +0100


--- Begin Message ---
  • From: Loukik Kudarimoti <>
  • To: Roman Lapcz <>
  • Cc:
  • Subject: bug in storage manager?
  • Date: Mon, 31 Jul 2006 10:50:04 +0100
Hi Roman,

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. 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.

Loukik.





--- End Message ---


  • [Fwd: bug in storage manager?], Loukik Kudarimoti, 07/31/2006

Archive powered by MHonArc 2.6.16.

Top of Page