You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/04/21 00:56:00 UTC

[jira] [Work logged] (GOBBLIN-1433) Github Actions Tests break with SSL Handshake error for SQL

     [ https://issues.apache.org/jira/browse/GOBBLIN-1433?focusedWorklogId=586257&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-586257 ]

ASF GitHub Bot logged work on GOBBLIN-1433:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 21/Apr/21 00:55
            Start Date: 21/Apr/21 00:55
    Worklog Time Spent: 10m 
      Work Description: Will-Lo opened a new pull request #3266:
URL: https://github.com/apache/gobblin/pull/3266


   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
   
   
   ### JIRA
   - [x] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1433
   
   
   ### Description
   - [x] Here are some details about my PR, including screenshots (if applicable):
   
   Tests involving SQL break on the latest version of Java 1.8, 1.8.291 which was released April 20, 2021.
   Error is caused by 
   `Caused by:
                       javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
                           at sun.security.ssl.HandshakeContext.<init>(HandshakeContext.java:171)`
                           
   Recommended solution is to bump up SQL connector version to use compatible encryption methods
   
   ### Tests
   -  [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   
   ### Commits
   - [x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 586257)
    Remaining Estimate: 0h
            Time Spent: 10m

> Github Actions Tests break with SSL Handshake error for SQL
> -----------------------------------------------------------
>
>                 Key: GOBBLIN-1433
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1433
>             Project: Apache Gobblin
>          Issue Type: Bug
>    Affects Versions: 0.16.0
>            Reporter: William Lo
>            Priority: Major
>             Fix For: 0.16.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Tests with SQL error out with the following error:
> No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
> This error is caused with a handshake failure in TLS.
> Need to either bump up SQL connector so that it uses the correct handshake protocol, or downgrade java version. Prefer the former solution as it is more long term



--
This message was sent by Atlassian Jira
(v8.3.4#803005)