Microsoft jdbc driver 3.0

This caused the getSchemas method not to work in some circumstances. For example, the getSchemas method will not work if the master database is inaccessible, as in SQL Azure, or if there are collation differences between the master database and other databases. After this update is applied, access to the master database is not required.

The getSchemas method will work in SQL Azure and will work if there are collation differences between the master database and other databases.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article.

This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article.

Is this page helpful? Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. View all page feedback. If the server is not installed a certificate, please set encrypt option to false on the connection string. This SSL authentication only behaviour cannot be disabled as far as I know.

That's the part where things go wrong. Also, this problem occurs intermittently. Most connections work normally. Only some newly created connections 'hang' this way. A socket connection has been made, but it seems the loginTimeout parameter in SQL server is used only for timing out on acquiring a socket, but a connection is only useable after successful login, and as such, the loginTimeout should include the authentication process, which it doesn't, and should be considered a bug.

The driver should time this out, but doesn't for exactly the same reason. The socket is acquired, but the authentication step gets into an infinite loop, and should at least be broken out of that by the loginTimeout, resulting in an exception.

But the behavior is not intermittent with me. Most Active Hubs Microsoft Teams. Security, Compliance and Identity. Microsoft Edge Insider. Azure Databases.

Autonomous Systems. Education Sector. Microsoft Localization. Microsoft PnP. Healthcare and Life Sciences. Internet of Things IoT.