Description of problem: Currently, each time a connection is requested from the connection pool, the connection is tested by selecting a "select 1;" query to the database. This is redundant, since still the query can fail after it was checked. In addition we should rely on the connection pool itself to give us a "good connection" This "select 1;" is harming database performance since every query executed is actually 2 queries resulting in 2 round-trips to the database to get the results. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Track JDBC queries with JBuilder or any other tool that do the same 2.See that the top most executed query is "select 1;" 3. Actual results: "select 1;" is performed before any query to the database to test the connection. Expected results: We should rely on connection pooling and exception handling for getting a good connection and handling the exception in case that the connection fails to perform the query Additional info:
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
'select 1' in 10s goes from 60 to 2 occurrences verified in ovirt-engine- 4.1.0-0.4.master.20170116141310.gita30debd.el7.centos.noarch