It's all about the answers!

Ask a question

Where is the cache from a REST API query is stored?

Andre Gusmao (802640) | asked May 26 '14, 3:10 p.m.
I developed a simple report using RTC REST API that retrieves a set of work items. Since the report is comprised of several work items, the best way to display the result set is to paginate the work items across several pages. However, after around 5 minutes navigating through the results, it seems that the cache with the result set is purged from the server. Is there a to control how long until cache is purged from the server? What is the default timeout for cache to be purged? Is this a CLM, WAS or IHS configuration?

-- Andre.

Accepted answer

permanent link
Donald Nong (14.5k514) | answered May 26 '14, 9:22 p.m.
You can view and modify most of the timeout settings of CCM in the Application Administration Advanced Properties page (/ccm/admin). I cannot find a timeout that appears to be related to your issue though. You can also have a look there - 5 minutes will be translated to 300 seconds or 300000 milliseconds if you are going to look for numbers.
BTW, what errors/message did you get so that you believed the cache was "purged"?
Andre Gusmao selected this answer as the correct answer

sam detweiler commented May 26 '14, 10:41 p.m.

Is it the query timeout? default 5 minutesĀ 

Andre Gusmao commented May 27 '14, 11:34 a.m.

Thanks Donald and Sam. Actually I did not go deep into the problem yet. I posted this question because a while ago I had a very similar issue when using HP Quality Center API, and after a lot of investigation the solution was to increase a cache expiration property. So I thought RTC could have a similar property to handle cache timeout.
I found the query timeout property and as you said, it is set to 300 sec (5 min). Does this property still apply even when querying through the REST API? Or it is restricted to queries built within RTC?


sam detweiler commented May 27 '14, 11:37 a.m.

far as I know, under the cover of the REST query is a normal query.. its all server side timing.

we had to redesign our java app to fetch and cache all the data up front, before processing to avoid this timeout. (our inline query processing took from 30 minutes to 8 hours.. the fetch and cache took 12 seconds for the same query results)

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.