![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
TIBCO BusinessEvents Express This section relates to Cache OM functionality and does not apply to TIBCO BusinessEvents Express edition.
Used only if the Strategy setting (see CDD Cluster Tab Backing Store Settings Reference) is set to oracle.Oracle Database Strategy If the Cluster tab > Backing Store > Strategy field is set to oracle, then Oracle Database strategy settings are used, and this property corresponds to the OracleConnectionCacheManager class property WaitTimeout.Specifies behavior when a connection is requested and there are already Cluster tab > Backing Store > Connection > Max Size connections active. If the be.backingstore.dburi.pool.waitTimeout.0 value is greater than zero (0), each connection request waits for up to the specified number of seconds. If no connection is returned to the pool before the timeout elapses, a No Database Connection available exception is thrown.The waitTimeout and inactivityTimeout properties specify wait periods to minimize the creation and destruction of connections (an expensive operation). Oracle Database Strategy If the Cluster tab > Backing Store > Strategy field is set to oracle, then Oracle Database strategy settings are used, and this property corresponds to the OracleConnectionCacheManager class property InactivityTimeout. Oracle Database Strategy If the Cluster tab > Backing Store > Strategy field is set to oracle, then Oracle Database strategy settings are used, and this property corresponds to the OracleConnectionCacheManager class property ReadTimeout. Used with write-behind strategy only. By default, deleted entities are removed from the backing store automatically at system startup. Set this property to false to disable that behavior. See Handling Entities Deleted from a Write-Behind Backing Store for more details.Default is true. When distributed batch recovery is enabled (be.engine.cluster.recovery.distributed.strategy=batch), the recovery manager divides the target table into many smaller batches and assigns 1-to-n number of these batches to each node (for them to execute recovery).Users can instead define be.engine.cluster.recovery.distributed.batchpernode=2 and prevent that too few, or too many batches are created Note For use with cache aside and only when the parallel operations feature is used.This property has no effect if Agent.AgentClassName.dbOpsBatchSize is set to 1 (see Table 57, CDD Agent Classes Tab Inference Agent and Query Agent Properties).For a guide to usage of this and other related properties, see the section Database Write Tuning Options for Cache Aside in Chapter 10, Threading Models and Tuning in TIBCO BusinessEvents Architect’s Guide.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |