This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 16%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDM%3C/text%3E%3C/svg%3E)
Recently we have upgrade the SQL JDBC driver from version 4 to version 12.6.2 jre11 as we upgraded to 2022 SQL server. After changing the driver we are facing issue in prepared statement. The same code with 12.6.2 jre8 and java8 returning results . But with java 11 the driver 12.6.2 jre11 is not working .Its returning null at this line "statement = dbConnection.prepareStatement(sql);"
Does this happen with any statement, even the simplest ones? Or is it a specific statement? It certainly helps when asking such questions to related what troubleshooting you have performed.
Its happening in all the statements.
Please ensure that your jar package files have been placed in the lib directory of the web server container.
Hi , @MikeyQiao-MSFT
I have checked the jars are placed in lib directory.
Please refer to this document to check the configuration and confirm that the settings are correctly loaded.
Hi @MikeyQiao-MSFT . Thanks for the reply and document. I have checked the configurations and all were correct. As i mentioned previously its getting error in JDBC12.6.1 JRE11 this driver with JDK11. While using JDBC12.6.1 JRE8 with JDK 8 its working . Could able to get results. The DB connections are happening But the PREPARED STATEMENT is where its returning null. The output is "statement = (org.apache.tomcat.dbcp.dbcp2.DelegatingPreparedStatement) sp_executesql SQL: null"
Hi，Dhamodharan MTo be honest, I'm not an expert in JDBC.I suggest you try using JAVA 21. Moreover, based on the information you've provided, if all your configurations have been loaded correctly and the value passed to PreparedStatement is NULL, it might be that the new version of the JDBC driver has altered the behavior of the execute method, or it has more stringent requirements for the format of the SQL statements being passed in (for instance, they may now need to end with a semicolon). I recommend continuous debugging to see if it's an issue with the driver configuration.