-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5.6.2: JDBC Sampler initialization failure makes test fail without any visible error #6174
Comments
Please attach the test plan that reproduces the issue |
Please find attached the problematic jmx. |
The root cause is It is sad JMeter does not report errors from
|
Previously, the exceptions from TestStateListener.testStarted might be unnoticed since the UI did not display them. This change is a workaround to surface errors in common cases. See apache#6174
…BCTestElement TestStateListener + TestBean cause issues like in apache#6174, so we should remove empty implementations
Previously, the exceptions from TestStateListener.testStarted might be unnoticed since the UI did not display them. This change is a workaround to surface errors in common cases. See apache#6174
…BCTestElement TestStateListener + TestBean cause issues like in apache#6174, so we should remove empty implementations
…BCTestElement TestStateListener + TestBean cause issues like in apache#6174, so we should remove empty implementations
Indeed that was the issue, but I still wonder why it works on 5.4.3. Thanks for help! |
Expected behavior
I am trying to test different DB with JMeter 5.6.2 and I expect for the test to run without issues.
As example JDBC Connection Configuration for MSSQL is in the attached picture.
![JDBC Connection Configuration 5 6 2](https://private-user-images.githubusercontent.com/4747139/290148553-84921769-b4e0-492e-ac65-540ff985b97f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkyNjA0MDQsIm5iZiI6MTcxOTI2MDEwNCwicGF0aCI6Ii80NzQ3MTM5LzI5MDE0ODU1My04NDkyMTc2OS1iNGUwLTQ5MmUtYWM2NS01NDBmZjk4NWI5N2YucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYyNCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MjRUMjAxNTA0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MmUzZjJhNTBjYjQ2NDJmYWMzNjZhNjlhY2YyMmIyODFkYTJiZjQ2ZWM3ZjQ0ZDk0Njc2MjU2OWM2ODI2M2ZhMyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.SoTLt_pKyw78U0rfw4Teh2_bNa0z6JICNCZ9gkkXAfM)
Actual behavior
When I run the test, nothing happens. No logs are written, nothing seems to be executed, no users are running. But when I try to close jmeter I get an message saying that I cannot do that since there is a test running.
I enabled debug logs for jdbc execution but no extra logs are present.
When doing the same test in Jmeter 5.4.3 (see attached JDBC Connection Configuration for MSSQL) it works.
![JDBC Connection Configuration 5 4 3](https://private-user-images.githubusercontent.com/4747139/290149767-85981f60-3038-4668-ad6f-b4caeb6de4b7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkyNjA0MDQsIm5iZiI6MTcxOTI2MDEwNCwicGF0aCI6Ii80NzQ3MTM5LzI5MDE0OTc2Ny04NTk4MWY2MC0zMDM4LTQ2NjgtYWQ2Zi1iNGNhZWI2ZGU0YjcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYyNCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MjRUMjAxNTA0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjA5ODU0ZDMxY2M3MDk1NTUxYmUxYmViNTYwNDk3YWJlNzhlN2JmMGZjYzFiZmFlNmE3YjYwZTVlM2JiYTVhZiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.zrgxIIy-H65zV8q7qPeFxbCTtdyBD6F-4R_CsAON0wk)
This does not happen for all types of DB. It works for mongodb, mysql, mariadb, but id does not work for postgresql and mssql.
I am using the same jar files for jdbc drivers put in lib folder of both versions of jmeter.
Steps to reproduce the problem
JMeter Version
5.6.2
Java Version
java version 11.0.16.1
OS Version
Microsoft Windows [version 10.0.19044.3693]
The text was updated successfully, but these errors were encountered: