FernandoNaviaB opened a new issue, #6454: URL: https://github.com/apache/jmeter/issues/6454
### Expected behavior When automating scenarios in JMeter that involve establishing database connections and executing SQL statements, it was necessary to add the Microsoft JDBC Driver for SQL Server connector for both Java 8 and Java 11. Running the scenarios locally and in Continuous Integration (Azure) should run without any errors or updates. Regardless of whether the JMeter version used in Continuous Integration is older, a compatible SQL Server JDBC connector must be available to allow the connection to the database and subsequent execution of statements or scripts from JMeter ### Actual behavior Currently, when running scenarios in continuous integration with JMeter 5.4 and the SQL Server JDBC connector version mssql-jdbc-12.6.2.jre11, the following new feature is observed: In a scenario that attempts to establish a database connection and execute two statements to delete a user (Delete), the connection is executed but the connection to the database is not connected, and therefore the statements are not executed. The mssql-jdbc-12.6.2.jre8 connector was changed, and when running it again in Continuous Integration, it is evident that in the aforementioned scenario, the connection to the database is established and the SQL statements are executed, thus deleting the user. However, a scenario that does not use a database connection fails, and upon validation, a 401 Unauthorized error code is received. The failed scenario was verified and it was confirmed that the error is not due to an issue related to its functionality or authentication issues. In fact, this scenario runs an d runs without problems locally, and when launched in Continuous Integration with SQL Server JDBC connectors, but for Java 11. In conclusion: When using SQL Server JDBC connectors of different versions but in Java 8 in JMeter version 5.4, the connection to the database is established correctly and the scripts or SQL statements are executed, but scenarios that were already running are affected, generating a 401 Unauthorized error code. In fact, a test was run by deactivating the scenario initially affected by the 401 error. It was deactivated and the scenarios were re-launched, and another scenario failed for the same reason. That is, if there is a Java 8 connector in the JMeter 5.4 folder and the scenarios are run in CI, one of them will present a 401 error. They are being run in order, so when the first one is deactivated, the second then fails, and so on. NOTE: We cannot currently consider upgrading the JMeter 5.4 version used in CI. Therefore, we have tried using versions of libraries or connectors compatible with this version, but this is the first time we've encountered this type of error. Please let me know what could be causing this behavior, whether it's an incompatibility error or which connector version I should use in JMeter 5.4. ### Steps to reproduce the problem 1. Download JMeter version 5.4 Download the SQL Server JDBC connector for Java 8 (any version; we tested with 12.10.0, 12.8, 12.6.2, versions 9, 8, and 7). 2. Add the connector (jar file) to the JMeter 5.4 "bin" folder. 3. Upload the compressed JMeter folder to the Continuous Integration storage and proceed to provision and run the tests. 4. Verify that only one test fails during execution and that when reviewing the log, several requests appear with error code 401-Unauthorized. 5. Run the scenario that fails in Continuous Integration locally in JMeter or Visual Studio. You can see what's happening; no errors are generated. -Additionally, it is verified that the scenarios that use the database pass because the connector allowed them to connect and execute the SQL statements. 7. If the failing scenario is deactivated and launched again with the same connector, another scenario fails this time with the same error. 8. If the connector is changed to one for Java 11, no scenario fails, but it is observed that one scenario in which Delete statements are executed did not generate a connection to the database and the SQL statements were not executed. However, other scenarios that use Update or Insert To statements did pass and do not present any changes. * We are taking the connectors from the following URL: https://learn.microsoft.com/es-es/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16#previous-releases I am attaching the JMeter zipped folder.     ### JMeter Version 5.4 ### Java Version 1.8.0_211-Java 8 ### OS Version Windows 11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
