Setting connection pool properties BusinessEvents performs backing store operations in bursts after each RTC. To tune your system, monitor the total number of threads, garbage collection, heap size, and so on, and adjust the pool size as needed. Using more connections can speed up recovery in the event of a failure, but uses more system resources.Preloading options Some optional properties specify that at startup, some, or none of the objects in the backing store are loaded into the cache, thus controlling the size of the cache. Objects not loaded at startup are loaded on an as-needed basis, when needed during an RTC, when they are not found in the cache.Limited Cache Size An optional pair of properties lets you set a limit to the size of the cache:Entries above the limit are kept in the backing store. The default size is 10000. If you want to use the default, you only need to add the isCacheLimited property.For more details, See Chapter 25, Project Configuration for Backing Store in TIBCO BusinessEvents User’s Guide.
1. In the BE_HOME/bin directory, open any one of the engine properties file you configured for the caching example: cs.tra, agent1.tra, agent2.tra, agent3.tra.
(If you do not add be.oracle.dburi.pool.enforce=true then the pool properties are ignored even if present.
Copyright © TIBCO Software Inc. All Rights Reserved.