...
</Connector>
Enable TLS on port 8443
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true">
<SSLHostConfig <SSLHostConfig protocols="TLSv1.2" truststoreFile="conf/cacerts.jks">
<Certificate certificateKeystoreFile="conf/clientcert.jks"
certificateKeystorePassword certificateKeystorePassword="changeit"
type type="RSA" />
</SSLHostConfig>
</Connector>
Note: Set protocols="TLSv1.2" to disable TLSv1.3 since the TCK requires post-handshake authentication and the Java 11 client does not support that.
tomcat-users.xml
Make the following changes:
...
Remove the sections setting the default character encoding for requests and responses to UTF-8.
Test Suite
Download latest nightly buildthe Jakarta Servlet 5.0.0 TCK
httpshttp://download.eclipse.org/ee4j/jakartaee-tck/masterjakartaee9/nightlypromoted/servlet-tck-5.0.0.zip
Extract to SERVLET_TCK_HOME
...
A default 10.0.x build (as of 2020-06-1810.0.0-M10) with the above configuration and the TCK built from source (as of 2020-06-18) triggers 23 test failures5.0.0 TCK triggers 1 test failure with the following JREs:
- Adopt OpenJDK 8u275 b01
- Adopt OpenJDK 11.0.9 b11 (TCK and Tomcat)
1 Expected failures
- 1 x default context path test as Tomcat configuration always overrides this
Fixed TCK bugs
- PR 338
- Incorrect major version (1 failure),
- Using LF rather an CRLF (15 failures)
- Strange /j_security_check test (2 failures)Error page attributes assumed to be unset when spec requires them to be set (3 failures)
- Missing annotation marker in Java 8 signature tests (1 failure)
- Re-do Java 11 signature test based on Java 8
- Fix regression in error page tests (1 failure)
- Java 11 issues with HTTP/2 client