Project and Portfolio Management Practitioners Forum
cancel

PPM Tip: Significance of TABLE_ENTRY_CACHE_SIZE

Highlighted
banulakshmi
New Member.

PPM Tip: Significance of TABLE_ENTRY_CACHE_SIZE

PPM contains standard request fields (such as text fields, date fields, and lists), complex components (such as attachments, table components), and entity-chooser co mponents (for example, staffing profiles). TABLE_ENTRY_CACHE_SIZE: Specifies the size of the table components cache in number of table components. TABLE_ENTRY_CACHE_TIMEOUT: Timeout for the table components cache, expressed in seconds. When facing scenarios where the table component value is right in the database and not matching the front end,the following can be done Stop PPM Open PPM_Home/conf/tune.conf Update the following parameter to have a value of 0: com.kintana.core.server.TABLE_ENTRY_CACHE_SIZE = 0 Run kUpdateHtml.sh Run kRunCacheManager.sh command from /bin folder with the option to clear all cache within PPM. Start PPM
Banu
PPM Support
1 REPLY
Etienne_Canaud
Micro Focus Expert

Re: PPM Tip: Significance of TABLE_ENTRY_CACHE_SIZE

Note that this tip only applies to PPM 9.30 and earlier. 

 

Since PPM 9.31, all the caches are configured from cache.conf, including table component cache.