DatatypeConverter Error after upgrade to 7.7.3
Getting the following error output after update from 7.3 to 7.7.3
500javax/xml/bind/DatatypeConverterjava.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter
This appears on the Test db connection in the profile and running the query on a page.
Comments (6)
-
-
We have the same issue after upgrading to Confluence version 7.8.1 using version 1.5 of this application.
500javax/xml/bind/DatatypeConverterjava.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:4128)
The cause of this issue is the change from Java 8 to Java 11 in Confluence. the FIX for this is to change a few things.
In the database connector app config (from manage apps in confluence) you need to change the Microsoft SQL CDN URL and may want to pre-stage the driver locally.
The old value for the Microsoft SQL CDN is:
https://repo1.maven.org/maven2/com/microsoft/sqlserver/mssql-jdbc/6.1.0.jre8/mssql-jdbc-6.1.0.jre8.jar
The value to which you should set this to fix this issue is:
https://github.com/microsoft/mssql-jdbc/releases/download/v7.4.1/mssql-jdbc-7.4.1.jre11.jar
You will need to add a folder in the c:\program Files\Atlassian\Confluence directory called “JdbcDrivers” (if you keep it all default).
Then pre-stage the MSSQL JDBC 7.4.1 driver JAR file there.
We did attempt to use the newest version of the JDBC driver (8.4.1) but it still gave an error when we tried, but version 7.4.1 appears to be fully compatible.
-
Thanks for sharing this. We just tried it out, and it worked for us, too. It also works with the 8.4.1 version for the jdbc driver.
But for some reason, we needed to restart confluence for the addon to detect and use the local driver.
-
-
assigned issue to
-
assigned issue to
-
Thanks @H5 IT . I’ve been buried recently, but I hope to carve out some time and bake in your fix so other users don’t stumble on it.
-
- changed status to resolved
the change is made in the source code and will be released soon.
- Log in to comment
We’ve hit the same issue after upgrading to confluence 7.4.5. This renders the addon useless for us.