https://bz.apache.org/bugzilla/show_bug.cgi?id=68500
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
Reviewing the stack trace and the Java 8_392 source code, there are multiple
things that look wrong here.
1. HttpsClient reads the https.protocols property so something must be setting
that property to a String that includes "TLSv1.1" before the cluster membership
provider starts.
2. "TLSv1.1" is a valid protocol name and will not trigger an exception in
ProtocolVersion.namesOf(). However, see the next point for an explanation of
this.
3. The exception message does not include a space between "Unsupported
protocol" and the name of the protocol. Therefore, the name of the protocol
request is
" TLSv1.1" (note the leading space) which is an invalid protocol name.
Something (not Tomcat) is setting the https.protocols system property to a
value that contains the string " TLSv1.1".
Further, the default TLS protocols for that version of Java when
SSLContext.getInstance("TLS") is used are TLSv1.2 and TLSv1.3.
All the evidence here points to an issue in a component other than Tomcat.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
