You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jmeter.apache.org by se...@apache.org on 2016/04/22 01:20:14 UTC

svn commit: r1740426 - /jmeter/trunk/xdocs/changes.xml

Author: sebb
Date: Thu Apr 21 23:20:14 2016
New Revision: 1740426

URL: http://svn.apache.org/viewvc?rev=1740426&view=rev
Log:
Oracle is different ...

Modified:
    jmeter/trunk/xdocs/changes.xml

Modified: jmeter/trunk/xdocs/changes.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/changes.xml?rev=1740426&r1=1740425&r2=1740426&view=diff
==============================================================================
--- jmeter/trunk/xdocs/changes.xml (original)
+++ jmeter/trunk/xdocs/changes.xml Thu Apr 21 23:20:14 2016
@@ -175,6 +175,9 @@ In the screenshot below the 10 seconds t
 <ch_title>JDBC request now uses DBCP2 pool</ch_title>
 <p>JDBC Request and JDBC Connection Configuration have been updated to replace old Excalibur Pool by Apache Commons DBCP2 pool. As a consequence properties have been migrated to equivalent 
 when available and UI has been updated.
+Note that unlike Excalibur, Commons DBCP uses the validation query when creating the pool.
+So make sure the query is valid.
+The default query suits many databases, but not all - for example Oracle requires 'SELECT 1 FROM DUAL' or similar.
 </p>
 <figure width="582" height="434" image="changes/3.0/jdbc_connection_configuration.png" ></figure>
 <ch_category>UX Improvements:</ch_category>