Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DWS triggers timeouts with some Data Holder queries #41

Open
homme opened this issue Jan 22, 2014 · 0 comments
Open

DWS triggers timeouts with some Data Holder queries #41

homme opened this issue Jan 22, 2014 · 0 comments

Comments

@homme
Copy link
Member

homme commented Jan 22, 2014

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant