![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Database Disconnection Situations In the event of a lengthy database disconnection, no events are processed until the database connection is restored. Depending on configuration, event processing may continue for some time to avoid disruption from short disconnections. For example, engine processes are blocked only when the database write queue is full (either the write-behind queue or the cache-aside queue). For more on these options see Database Write Tuning Options for Cache Aside.For backing store configuration, see Chapter 30, JDBC Backing Store Setup in TIBCO BusinessEvents Developer’s Guide.Various options are available for configuring the backing store for your needs, as explained in this chapter. See Managing Storage and Retrieval of Entity Objects for more information about fine grained controls over data storage and retrieval.Writes to the backing store can be done in either of two ways: Cache-aside, in which the inference agent handles all writes simultaneously, and offers transaction control; or write-behind, in which the cache agent handles writes to cache then database.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |