This one is related to Bug #38682 http://issues.apache.org/bugzilla/show_bug.cgi?id=38682 Currently there is no way to benchmark the execution of JDBC PreparedStatements. Even for CallableStatements that are a subclass of PreparedStatements are not fully supported now. Because no "true" parameters ( '?' in the sql statemetns) are allowed then it's not possible to execute RPC to stored procedures in all jdbc drivers. Lots of JDBC drivers doesn't execute a RPC call if the CallableStatement has no parameters. i.e the following statement call s2('id1000') will translate in Sybase ASE to a TDS_LANG query but the following statement call s2(?) will translate to TDS_RPC that is much faster and the preferred way to access the database.
Created attachment 19044 [details] Support for JDBC PreparedStatements and CallableStatements with parameters Adds support for JDBC PreparedStatement. Two boxes in the lower part of the windows allow to enter a comma separated list of parameter values and a comma separated list of parameter types (VARCHAR, INTEGER, etc).
I've created a plugin with a new JDBC Sampler supporting the PreparedStatements. Anyone interested in using it can check it out at http://rubenlaguna.com/wp/2006/12/14/enhanced-jdbc-sampler-for-apache-jmeter/
Version 2.2.1 does not exist (yet)
Thanks for the patch, which has been applied in SVN r528906. I changed the code to set up mapJdbcNameToInt using a static initialiser.
I posted an attachment in Bug #42018 to allow commits and rollback that currently aren't supported in JMeter. (At least not supported in all databases, i.e Apache Derby). (In reply to comment #4) > Thanks for the patch, which has been applied in SVN r528906. > > I changed the code to set up mapJdbcNameToInt using a static initialiser. >
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1817