Bug 59113 - JDBC Connection Configuration : Transaction Isolation level not correctly set if constant used instead of numerical
Summary: JDBC Connection Configuration : Transaction Isolation level not correctly set...
Status: RESOLVED FIXED
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.13
Hardware: All All
: P2 major (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-04 03:11 UTC by battulga
Modified: 2016-08-02 21:12 UTC (History)
1 user (show)



Attachments
jmeter result (66.77 KB, image/png)
2016-03-07 04:05 UTC, battulga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description battulga 2016-03-04 03:11:31 UTC
i connect to mysql database using jdbc configuration sample.
custom transaction isolation level set on jdbc configuration.
but jdbc sampler not set on jdbc configurtaion isolation level (set on mysql server side default isolation level).

i simple test checked.
add jdbc configuration and custom isolation.
add jdbc sampler using jdbc connection pool query is (show variables like '%isolation%'; or show variables like '%isolation%';)

then check result.
Comment 1 Philippe Mouawad 2016-03-05 15:16:54 UTC
Hello,
What does this sql show:
SELECT @@GLOBAL.tx_isolation, @@tx_isolation;


What MySQL Driver  are you using ?

Can you make a test with nightly build :
https://builds.apache.org/job/JMeter-trunk/lastSuccessfulBuild/artifact/trunk/dist/
Comment 2 battulga 2016-03-07 03:49:59 UTC
mysql jdbc driver:
mysql-connector-java-5.1.38-bin.jar

jmeter version:
2.13 r1665067

mysql server version: 5.6.27

default isolation level: READ-COMMITED
Comment 3 battulga 2016-03-07 04:05:56 UTC
Created attachment 33640 [details]
jmeter result

https://builds.apache.org/job/JMeter-trunk/lastSuccessfulBuild/artifact/trunk/dist/

same result your r1733851 version same r1665067.

result is read-commited as default isolation.

must have read-uncommited.
Comment 4 battulga 2016-03-07 04:06:14 UTC
https://builds.apache.org/job/JMeter-trunk/lastSuccessfulBuild/artifact/trunk/dist/

same result your r1733851 version same r1665067.

result is read-commited as default isolation.

must have read-uncommited.
Comment 5 Philippe Mouawad 2016-03-11 21:20:42 UTC
Hello,
Can you try the code use by JMeter using the same driver that you use in JMeter ?

I am not sure this is a JMeter bug.
Regards
Comment 6 battulga 2016-03-18 04:17:35 UTC
I wrote servlet using jdbc(jndi resource lookup) connect to mysql.
jdbc same driver, same database and isolation level set on jndi resource.
this case no problem. working fine.

I tried JMeter connect JSR sample.
jdbc same driver and same database.
this case same problem a jdbc sampler.
Comment 7 Philippe Mouawad 2016-08-02 21:09:11 UTC
Author: pmouawad
Date: Tue Aug  2 21:07:07 2016
New Revision: 1755003

URL: http://svn.apache.org/viewvc?rev=1755003&view=rev
Log:
Bug 59113 - JDBC Connection Configuration : Transaction Isolation level not correctly set if constant used instead of numerical
Bugzilla Id: 59113

Modified:
    jmeter/trunk/src/protocol/jdbc/org/apache/jmeter/protocol/jdbc/config/DataSourceElementBeanInfo.java
    jmeter/trunk/xdocs/changes.xml
Comment 8 Philippe Mouawad 2016-08-02 21:12:45 UTC
@battulga, 
thanks for report, I finally found the problem.
Could you test nightly build tomorrow using this:
http://jmeter.apache.org/nightly.html

Thank you