Products | Versions |
---|---|
TIBCO BusinessEvents Enterprise Edition | - |
Not Applicable | - |
Resolution:
Description:
============
What is the usage and functionality of java.property.be.engine.limited.cache.back.size.limit and be.engine.cluster.isCacheLimited properties in TIBCO BusinessEvents (BE) 3.0.1 ?
Environment:
==========
TIBCO BusinessEvents 3.0.1
Resolution:
=========
The be.engine.cluster.isCacheLimited property can be set when using a database as the backing store. This property configures the Cache server to store older cache entries in the database when the limit of entries is reached.
The Cache limit can be set using the Java property
java.property.be.engine.limited.cache.back.size.limit.
This limit is 10000 by default an may be set using the property java.property.be.engine.limited.cache.back.size.limit.
Example:
=======
be.engine.cluster.isCacheLimited=true
java.property.be.engine.limited.cache.back.size.limit=10000
Note
====
The size limit is used to limit the number of objects per concept in the cache and not the total objects in the cache. It means that if their are two concepts in the project ontolgy and if the size limit is set to 100 then 200 (100 each for the two concept) objects will be the size of the cache. You only need to set the size limit if you want to use a size other than the default size.
References:
==========
More information may be found in the BE User Guide Chapter 25 - Project Configuration for Backing Store.