You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2019/12/17 20:43:18 UTC
[Bug 64012] New: Hardcoded enableAutoCommitOnReturn for dataSource
cause failed test suite for some DBs
https://bz.apache.org/bugzilla/show_bug.cgi?id=64012
Bug ID: 64012
Summary: Hardcoded enableAutoCommitOnReturn for dataSource
cause failed test suite for some DBs
Product: JMeter
Version: 5.2.1
Hardware: PC
OS: Mac OS X 10.1
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: sdn.xaoc@gmail.com
Target Milestone: JMETER_5.2
Created attachment 36920
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36920&action=edit
Example JMX
Currently confirmed for Derby DB:
1. Create 2 JDBC Connections: first with autoCommit=true, other with
autoCommit=false
2. Create 2 JDBC Samples with any statements (create table in example jmx file.
change user_define_classpath property in the example)
3. While executing this test suite - exception occurs:
java.sql.SQLException: Cannot create PoolableConnectionFactory (Cannot close a
connection while a transaction is still active.)
Commenting following line of code solves this issue:
org/apache/jmeter/protocol/jdbc/config/DataSourceElement.java:232
dataSource.setEnableAutoCommitOnReturn(false);
(This code was introduced in 3.3 version)
This behavior is hardcoded and there is no way no change this inside Jmeter.
--
You are receiving this mail because:
You are the assignee for the bug.