nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Search service - timeout issue

Kapil_Chaudhari

Hi,

I am getting "Your search has timed out." error while using a search service to get all the children dataids in a folder. I have never received this timeout before. If I re-run the same search again, it returns the results without any problem. Is there a setting to adjust this timeout? Is it happening because of the network issues?

Here is my request-

<tns:Search xmlns:tns="urn:SearchServices.service.livelink.opentext.com">

<tns:queries>

<tns:DataCollectionSpec>"LES Enterprise [All Versions]"</tns:DataCollectionSpec>

<tns:FirstResultToRetrieve>1</tns:FirstResultToRetrieve>

<tns:NumResultsToRetrieve>2000</tns:NumResultsToRetrieve>

<tns:QueryLanguage>Livelink Search API V1</tns:QueryLanguage>

<tns:ResultOrderSpec>sortByRegion=OTModifyDate</tns:ResultOrderSpec>

<tns:ResultSetSpec>where1=[qlregion OTLocation] 1000000&lookfor1=complexquery&boolean2=and&where2=[qlregion OTSubTypeName] Folder&lookfor2=complexquery</tns:ResultSetSpec>

<tns:ResultTransformationSpec>OTModifyTime</tns:ResultTransformationSpec>

<tns:ResultTransformationSpec>OTDataID</tns:ResultTransformationSpec>

<tns:ResultTransformationSpec>OTName</tns:ResultTransformationSpec>

<tns:ResultTransformationSpec>OTModifyDate</tns:ResultTransformationSpec>

<tns:ResultTransformationSpec>OTVersion</tns:ResultTransformationSpec>

<tns:ResultTransformationSpec>OTSubTypeName</tns:ResultTransformationSpec>

<tns:ResultTransformationSpec>OTVerCreatedByName</tns:ResultTransformationSpec>

</tns:queries>

<tns:partitionName>NONE</tns:partitionName>

</tns:Search>

Thanks,

Kapil

Find more posts tagged with

Comments

Guy_Pomerleau

Which version of livelin are you running? How many instances? Are in a cluster envrionnement. How many users? YOu might run out of thread availability.

Kapil_Chaudhari

Which version of livelin are you running? - 9.7.1

How many instances? - 5 front end, 1 admin

Are in a cluster envrionnement. - Yes

How many users? - 7000 added to system

Kyle_Swidrovich

Hi Kapil,

There are various points in the chain from initial request to final response that can register a "timeout" condition. Without seeing logs, it's not possible to tell, for example, if the search federator is timing out or if it's timing out after trying to evaluate permissions on the result set.

I'd recommend opening a support ticket on this, ensuring you capture the timeout condition with the following logging enabled:

[general]
Debug=2

[options]
wantDebugSearch=TRUE

AND

In the Search Federator's specific tab in the GUI, ensuring log level is at "Info" and provide its log.

Thanks,
Kyle

Guy_Pomerleau

Could it be you reach the maximum treads per instance? with 9.7.1, there is a max of 5 thread per instance so may be your servers are too busy, the search request wait for too long for a free thread.