Numerous TIBCO BusinessEvents Backing Store rollbacks occurring in a BE application.
Article ID: KB0094545
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
The rollback is done by the generic connection pool when the connection is returned to the pool. This is done as a safety measure to make sure that the client of the pooled connection does not have an uncommitted transaction or is holding any database locks by the connection object. This is a cleanup measure before making the connection available to the next client. See the attached screen shot for reference. (Filename: DB_Stat_Screenshot_1.png). These rollback calls should not have any impact on performance. This behavior can be disabled with the following cluster level property.
The rollback is done by the generic connection pool when the connection is returned to the pool. This is done as a safety measure to make sure that the client of the pooled connection does not have an uncommitted transaction or is holding any database locks by the connection object. This is a cleanup measure before making the connection available to the next client. See the attached screen shot for reference. (Filename: DB_Stat_Screenshot_1.png). These rollback calls should not have any impact on performance. This behavior can be disabled with the following cluster level property.
be.backingstore.connection.rollbackafterrelease=false (default is true)
Issue/Introduction
Numerous TIBCO BusinessEvents Backing Store rollbacks occurring in a BE application.
Additional Information
BE Engineering
Attachments
Feedback
Yes
No
Powered by
