zeshuai007 commented on pull request #2197: URL: https://github.com/apache/thrift/pull/2197#issuecomment-674345204
Hi @ulidtko I didn't investigate the CORSS run you found on March 22, but in all the compilation builds on Travis, I compared the last successful run log of erlang22 jobs to the last failed run log of erlang23, so I'm sure, this problem is caused by the upgrade to erlang23. Travis-CI: erlang22 - Last successful ([build#6701](https://travis-ci.org/github/apache/thrift/builds/692484717)) https://travis-ci.org/github/apache/thrift/jobs/692484722 erlang23 - First execution failed ([build#6702](https://travis-ci.org/github/apache/thrift/builds/692597055 )) https://travis-ci.org/github/apache/thrift/jobs/692597058 Note that log line 13101 uses jdk11, and JAVA_HOME set in log line 12340 is java-8-oracle (Java JVM running environment, so I think Java8 is used actually). Therefore, erlang-client uses TLS1.3 (Erlang23 supports two TLS versions, which seems to be a feature of the new Erlang version) and Java-server (JDK11/TLS1.3) / (JDK8/TLS1.2). Thank you for your work. If there is no better solution, setting up TLS1.2+TLS1.1 temporarily will look great as setting up Erlang22, but it will require two or more post-maintenance. I saw the ticket you submitted in Erlang, and I look forward to the Erlang expert's investigation. I have plans to learn Erlang recently, and unfortunately for some reason I'm focusing on C, but I'll be back. Cheers, Zezeng Wang ---------------------------------------------------------------- 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: [email protected]
