Additional properties for tuning Oracle behavior which are undocumented in BusinessEvents 3.0.1
Article ID: KB0086771
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Description:
Abstract:
When a backing store is used and Oracle connection pool size settings are enforced, two properties are enabled in addition to the three properties that set initial, minimum, and maximum number of connections.
These properties were added in BusinessEvents 3.0.1 but were not documented:
be.oracle.dburi.pool.waitTimeout.0
Specifies the number of seconds a thread waits for a connection to become available when none is available in the pool. If a connection does not become available during this time period, and the pool size is less than the max pool size, a new connection is created. If the pool size has reached the max pool size, an exception is thrown.
Default value is 1 second.
be.oracle.dburi.pool.inactivityTimeout.0
Specifies the number of seconds an unused connection remains available (so that other threads can use it). After this period, the connection is closed and removed from the pool.
Default value is 900 seconds.
To use these properties, set the be.oracle.dburi.pool.enforce.0 to true. (They are ignored if this property is not present or is set to false.) Try running with default values. If the behavior is not as desired, add the properties in the TRA file and set values as needed to fine tune the behavior.
Environment:
Applies to all platforms and OSes
Applies to BE 3.0.1 and all it's Service Pack releases.
Abstract:
When a backing store is used and Oracle connection pool size settings are enforced, two properties are enabled in addition to the three properties that set initial, minimum, and maximum number of connections.
These properties were added in BusinessEvents 3.0.1 but were not documented:
be.oracle.dburi.pool.waitTimeout.0
Specifies the number of seconds a thread waits for a connection to become available when none is available in the pool. If a connection does not become available during this time period, and the pool size is less than the max pool size, a new connection is created. If the pool size has reached the max pool size, an exception is thrown.
Default value is 1 second.
be.oracle.dburi.pool.inactivityTimeout.0
Specifies the number of seconds an unused connection remains available (so that other threads can use it). After this period, the connection is closed and removed from the pool.
Default value is 900 seconds.
To use these properties, set the be.oracle.dburi.pool.enforce.0 to true. (They are ignored if this property is not present or is set to false.) Try running with default values. If the behavior is not as desired, add the properties in the TRA file and set values as needed to fine tune the behavior.
Environment:
Applies to all platforms and OSes
Applies to BE 3.0.1 and all it's Service Pack releases.
Issue/Introduction
Additional properties for tuning Oracle behavior which are undocumented in BusinessEvents 3.0.1
Feedback
Yes
No
Powered by
