Bug 66261 - JDBC requests in a Transaction Controller not use the same connection。
Summary: JDBC requests in a Transaction Controller not use the same connection。
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: unspecified
Hardware: PC
: P2 normal (vote)
Target Milestone: JMETER_5.5
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-14 02:15 UTC by hdchild
Modified: 2022-09-14 02:15 UTC (History)
0 users


Attachments
the test plan jmx file (14.87 KB, application/xml)
2022-09-14 02:15 UTC, hdchild 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description hdchild 2022-09-14 02:15:28 UTC 
Created attachment 38388 [details]
the test plan jmx file

JDBC requests in a Transaction Controller not use the same connection。

I configure "JDBC connection Configuration" with Auto Commit = False.
I configure some JDBC requests in a Transaction Controller, I found 2 things:
1. each JDBC request in a Transaction Controller may use different connection instead of use the same connection.
2. At the end of test, jmeter will send "rollback" to all related connections.

The jmx file is uploaded
Comment 1 The ASF infrastructure team 2022-09-24 20:38:23 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5703