Posts Tagged ‘FUTURETENSE.INI’


Following are some of the important properties related to PAGE CACHING in FUTURETENSE.INI file.

  1. cs.nocache
  2. cs.pgCacheTimeout
  3. cc.SystemPageCacheCSz
  4. cc.SystemPageCacheTimeout
  5. cs.alwaysusedisk
  6. cs.freezeCache
  7. cs.manage.expired.blob.inventory

We will now have a detailed look about these properties.

cs.nocache

This forcibly disables the adding and serving of pages from cache. Legal values are true and false.

cs.pgCacheTimeout

This is the default lifetime of a cached page, specified in minutes. Specify 0 (zero) to never time pages out from the cache.

Sites that use intelligent page  cache invalidation through CacheManager, including CS Direct sites written using CS Direct 4.0 coding practices and later, will be able to rely on automatic cache invalidation so timeout is not relevant.

Only advanced users should modify the value of this property.  Setting it to a value greater than zero when Satellite Server is used can result in pages that cannot be ever be explicitly removed from the Satellite Server cache.

cc.SystemPageCacheCSz

This is the maximum number of pages that will be cached in memory.  Pages will still be cached to the database but for better performance pages should be cached to memory too.  This property allows you to specify how many pages will live in memory.  Default value is 10,000, reduce if memory is at a premium.  Performance may suffer.

cc.SystemPageCacheTimeout

This is the default lifetime of a cached page in memory.  Cached pages will live in the database until they are set to expire but for performance reasons pages are also cached in memory.  This specifies the timeout (minutes) of the memory cache.  If memory is at a premium you may shrink this value but it is set to 24 hours (1440 minutes) by default.

cs.alwaysusedisk

This specifies the default behavior for page entries in the site catalog that have no specific cache override property. If set to yes, then pages served from the Content Server will be cached unless explicitly specified otherwise in cacheinfo. Though the name indicates that pages are cached to disk, they are in fact cached to the database using url-columns.

Legal values are yes and no.

cs.freezeCache

This controls whether Content Server expires cached pages on a schedule.  Specify yes to prevent the creation of an event to periodically clear the page cache.  No pages whose expiry date has passed will ever be served regardless of this property value because their expiration is checked immediately prior to serving.

Legal values are yes and no.

cs.manage.expired.blob.inventory

This property specifies whether or not blob dependencies will be flushed from the inventory (SystemItemCache table) when the blob times out from cache.

If set to true, then blob inventory items will not be cleared from the inventory table.  This improves the reliability of CacheManager such that blobs can be flushed from SatelliteServer when the blobs have expired from ContentServer.  The cost is increased use of space in the database.  If set to false, then  when a blob expires from the cache, the corresponding inventory entries will also be removed from the database.  If the cache is being actively managed, the blobs should not ever expire from the cache.

The default value is false.

Advertisements

Many a time, while working with Fatwire, we face the problem “CONTENT SERVER TIMEOUT ERROR“.  This problem will be annoying for us if we are working on the ADVANCED/ DASH UI. Check the below screen.

When a session error occurs, any unsaved changes are lost. All other content is saved and can be accessed and reviewed. To gain access to the system, you will need to login again. This is quite annoying.

This is due to the default setting given in FATWIRE’s FUTURETENSE.INI file for the Content Sever’s Timeout activity.

The default timeout for Content Server is 900 Seconds (900/60 = 15 mins)

The solution for getting out of this issue, at least for our specified amount of time) is to hack the FUTURETENSE.INI file.

Open the FUTURETENSE.INI file with PROPERTYEDITOR or normal text editor.

You will be able to find a property called  “cs.timeout”, and a default value assigned to it as “900″. It will look as follows:

cs.timeout=900

Where, 900 is the time set in SECONDS. Since 900/60 = 15 mins, the CS will be timedout every 15 minutes.

Hence, set the time as per which your wish. For example, if you need to set an hour as the default value for timeout activity, then set “3600” (as 3600/60 = 60 mins = 1 hour) as the value instead of “900“. It should look as follows:

cs.timeout=3600

Restart the Content server, for the changes to take effect.

The issue will be resolved.