geo-data / medin-portal

Implementation of the MEDIN portal
http://portal.oceannet.org
3 stars 1 forks source link

DWS triggers timeouts with some Data Holder queries #41

Open homme opened 10 years ago

homme commented 10 years ago

This is an issue affecting the new DWS: If the DWS does not respond to a portal query within 10 seconds, the portal times out and returns an error to the user. This is happening for certain data holder queries. The following query triggers the timeout whilst looking for all records held by 'British Geological Survey (BGS)':

/search/full/catalogue?dh=1827534157

The SOAP sent to the DWS is as follows (generated by /search/full/catalogue?dh=1827534157&soap=request):

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://discovery.ejb.revitalization.services.ndg/" xmlns:ns2="http://schemas.services.ndg/discovery" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Header/>
  <ns0:Body>
    <ns1:DoSearch>
      <request>
        <ns2:SearchCriteria>
          <ns2:TermSearch id="1">
            <ns2:Term>'''British Geological Survey (BGS)'''</ns2:Term>
            <ns2:TermTarget>DataCustodian</ns2:TermTarget>
          </ns2:TermSearch>
          <ns2:TermSearch id="2" operator="OR">
            <ns2:Term>'''British Geological Survey (BGS)'''</ns2:Term>
            <ns2:TermTarget>DataDistributor</ns2:TermTarget>
          </ns2:TermSearch>
          <ns2:ResourceLocator/>
        </ns2:SearchCriteria>
        <ns2:RetrieveCriteria>
          <ns2:OrderBy>
            <ns2:OrderByField>DatasetMetadataUpdateDate</ns2:OrderByField>
            <ns2:OrderByDirection>descending</ns2:OrderByDirection>
          </ns2:OrderBy>
          <ns2:RecordDetail>DocumentSimple</ns2:RecordDetail>
        </ns2:RetrieveCriteria>
        <ns2:Start>1</ns2:Start>
        <ns2:HowMany>1</ns2:HowMany>
      </request>
    </ns1:DoSearch>
  </ns0:Body>
</SOAP-ENV:Envelope>

@SteveDonegan says this is a database issue that is being investigated.