-
Notifications
You must be signed in to change notification settings - Fork 435
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
The TDS protocol stream is not valid. Unexpected token TDS_COLMETADATA (0x81). #1274
Comments
Hi @RomainWilbert , |
Thanks for answering. When i update the driver, i get the following error :
|
Do i have to add the Azure Keyvault self-signed certificate to the cacerts file ? |
Updating to openjdk:10-jdk resolved the issue Any idea to resolve this issue with OpenJDK 8 ? I am not sure i can upgrade the JVM on my app. |
Stacktrace indicates your certificate chain is incomplete or invalid, so yes you need to add to cacerts |
Hi @RomainWilbert , |
Hi @ulvii ! |
Hi @RomainWilbert , |
I tried updating to OpenJDK 13 and the issue "PKIX path building failed" is still here. Since i don't want to update evertime Microsoft changes its certificate, is there a way to disable certificate validation ? |
Hi @RomainWilbert , You can disable certificate validation by setting The PR you mentioned is unrelated to your issue. |
@ulvii I just figured out that the SSL issue was caused by my corporate proxy...everything works fine running on Azure...sorry for the noise !! |
Driver version
8.2.1.jre8
SQL Server version
Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)
Client Operating System
Windows
JAVA/JVM version
OpenJDK 8
Problem description
When I activate Column Encryption with Azure Key vault, sometimes when I query tables even with no encrypted column, I get errors from jdbc driver : "The TDS protocol stream is not valid. Unexpected token TDS_COLMETADATA (0x81)."
JDBC trace logs
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TDS protocol stream is not valid. Unexpected token TDS_COLMETADATA (0x81). at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2670) at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2658) at com.microsoft.sqlserver.jdbc.SQLServerConnection.throwInvalidTDSToken(SQLServerConnection.java:2647) at com.microsoft.sqlserver.jdbc.TDSReader.throwInvalidTDSToken(IOBuffer.java:6421) at com.microsoft.sqlserver.jdbc.TDSParser.throwUnexpectedTokenException(tdsparser.java:128) at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onColMetaData(tdsparser.java:230) at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:87) at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:28) at com.microsoft.sqlserver.jdbc.SQLServerConnection$1ConnectionCommand.doExecute(SQLServerConnection.java:2754) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7344) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2713) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectionCommand(SQLServerConnection.java:2759) at com.microsoft.sqlserver.jdbc.SQLServerConnection.rollback(SQLServerConnection.java:2939) at com.zaxxer.hikari.pool.ProxyConnection.rollback(ProxyConnection.java:370) at com.zaxxer.hikari.pool.HikariProxyConnection.rollback(HikariProxyConnection.java) at org.hibernate.resource.jdbc.internal.AbstractLogicalConnectionImplementor.rollback(AbstractLogicalConnectionImplementor.java:116)
The text was updated successfully, but these errors were encountered: