[
https://issues.apache.org/jira/browse/BEAM-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566540#comment-16566540
]
Ismaël Mejía commented on BEAM-5045:
------------------------------------
Just for ref, it seems MS SQL server has some magic words in the connection
properties so playing with those may help
https://docs.microsoft.com/en-us/sql/connect/jdbc/connecting-with-ssl-encryption?view=sql-server-2017
> JdbcIO connection issue on version 2.5.0
> ----------------------------------------
>
> Key: BEAM-5045
> URL: https://issues.apache.org/jira/browse/BEAM-5045
> Project: Beam
> Issue Type: Bug
> Components: io-java-jdbc
> Affects Versions: 2.5.0
> Reporter: Liran Agami
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
>
> I have ran into this error: "Cannot create PoolableConnectionFactory (The
> driver could not establish a secure connection to SQL Server by using Secure
> Sockets Layer (SSL) encryption. Error: "Socket is closed". "
> When I try to run the following:
> pipeline.apply(BQTable, JdbcIO.<List<String>>read()
> .withDataSourceConfiguration(JdbcIO.DataSourceConfiguration.create(options.getDriverName(),
> options.getConnectionUrl())
> .withUsername(options.getUserName()).withPassword(options.getPassword())
> .withConnectionProperties("encrypt=false"))
> I have updated the JDBC driver on both the server(6.4 for a Microsoft Server)
> and have updated the beams-sdk-java-io-jdbc to 2.5 as well.
> This error only occurs when I run the pipeline on apache beam 2.5 but not on
> 2.4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
