How to extend RDNG or DB timeout for long running query?
We have extended an artifact type with 15 artifact attributes and associated attribute data types. A specific query that uses 13 of the attributes (4 attributes are searching for a specific value and 9 are attribute "does not exist" criteria) times out after 2 minutes (120000 ms). Other similar queries process successfully.
Resolving the problem
Increase the query client time-out to resolve the problem or restructure the query as the error message suggests.
This question is not about how to restructure the query. The question is how to extend the timeout.
One answer
To my experience, adjusting these 2 properties usually allow a long running query to complete.
(both are found in rm/admin >Advanced Properties)
1. RM Core Component -- query.client.timeout (Default 30000)
This is for the query itself. Exceeding this time out causes a warning and the query stops finished with incomplete result. Sometimes running this several times will give at the end the full result without warning.
But, if you have increase it to 120000 ms or more you may bump into another a "Connection Timeout".
For this you may also need to increas the value of the property below:
2. RM Client Component --Timeout for DNG WebUI communications (ms) (default 120000)
If this value is exceeded you'll get a 'Connection Timeout' error on the UI
Note that changing this property requires a server restart.
Comments
Diana, thank you for the quick response! I failed to add the we are running v5.0.2 on Linux.
No this property was introduced in 6.0 per https://www-01.ibm.com/support/docview.wss?uid=swg21962999