Hi,

When switching a customers driver to tls 1.2 on MSSQL the driver will
hang on establishing connection.

I updated the JDTS to 1.3.1, even tried one with a later SVN build
patch.

I can use the JDTS.jar from some basic test Java code just fine to
connect to the same database from the same network but in the trace I
see this:

Code:
--------------------
[09/22/16 15:56:57.097]:Osiris-TLS PT:Opening temporary Publisher query file.
[09/22/16 15:56:57.097]:Osiris-TLS PT:Restricting file Permission for ./jdbc_8249d38c-0e11-4aee-fd93-8cd34982110e_1.lg
[09/22/16 15:56:57.098]:Osiris-TLS PT:Restricting file Permission for ./jdbc_8249d38c-0e11-4aee-fd93-8cd34982110e_1.db
[09/22/16 15:56:57.117]:Osiris-TLS PT:File './jdbc_8249d38c-0e11-4aee-fd93-8cd34982110e_1' opened.
[09/22/16 15:56:57.117]:Osiris-TLS PT:Connecting to database...
[09/22/16 15:56:57.118]:Osiris-TLS PT:BEGIN Open connection 'dedicated0'.
[09/22/16 15:56:57.118]:Osiris-TLS PT: BEGIN Instantiate connection.
[09/22/16 15:56:57.118]:Osiris-TLS PT: CALLING DriverManager.getConnection(String, String, String)
[09/22/16 15:56:57.118]:Osiris-TLS PT: WITH PARAM 1: jdbc:jtds:sqlserver://sqlcluster05.customer:1433/niamtls;ssl=true
[09/22/16 15:56:57.118]:Osiris-TLS PT: WITH PARAM 2: tlsniam
[09/22/16 15:56:57.119]:Osiris-TLS PT: WITH PARAM 3: <!-- content suppressed -->
--------------------


And then it just hangs indefinitely.
Same with following URI's:
jdbc:jtds:sqlserver://sqlcluster05.customer:1433/niamtls;ssl=require
jdbc:jtds:sqlserver://sqlcluster05.customer:1433/niamtls;ssl=request

ON the MSSQL side we see the session being authenticated.

Has anyone ever seen this before?

Regards,

Albert-Jan


--
ajstevens
------------------------------------------------------------------------
ajstevens's Profile: https://forums.netiq.com/member.php?userid=3153
View this thread: https://forums.netiq.com/showthread.php?t=56613