It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×6,033
×3,954

question asked: Feb 06 '17, 4:52 p.m.
question was seen: 2,150 times
last updated: Jun 20 '19, 12:46 p.m.

Related questions

How to extend RDNG or DB timeout for long running query?

0
Daniel Senko (17●1●4●11) | asked Feb 06 '17, 4:52 p.m.

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.  


We can create the timeout at the RDNG UI (Browse Artifacts, Filter by Attribute) or via the RM API (the real consumer).  RDNG throws an error in the UI and rm.log and while doing problem determination, we landed at: 

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. 


We have tried multiple tests by incrementally changing RM Advanced properties (with appropriate server restarts) all set to 5 minutes (300000 ms) but the query still times out at 2 minutes. 

Change RM Core Component query.client.timeout to 300000 from 3000 (default)
Change RM Core Component connection.timeout to 300000 from 120000 (default)
Change RM Core Component RDMCacheExpiration to 300000 from 120000 (default)
Change Jazz Foundation Services Default Expiration (millis) to 300000 from 120000 (default)
Change Jazz Foundation Services timeout to 300000 from 120000 (default)

Looking for suggestions on other settings to adjust or root causes. 

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Diana Kraaijeveld (577●2●7) | answered Feb 07 '17, 7:52 a.m.
JAZZ DEVELOPER

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
Daniel Senko commented Feb 07 '17, 8:52 a.m.

Diana, thank you for the quick response!  I failed to add the we are running v5.0.2 on Linux. 


I do not recognize this property below.  Is this available in v5.0.2 and/or under a different property?

2. RM Client Component  --Timeout for DNG WebUI communications (ms)  (default 120000)  


Rosa Naranjo commented Jun 20 '19, 12:46 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

No this property was introduced in 6.0 per https://www-01.ibm.com/support/docview.wss?uid=swg21962999

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.