On 09/12/2021 14:27, Christopher Schultz wrote:
On 12/9/21 09:17, Mark Thomas wrote:
<snip/>
Got to the bottom of this at least. JDK differences. It appears to be
differences in the Temurin JDK between MacOS and Linux. Everything is
fine on MacOS which is what I was working on last week when I fixed
this the first time.
Hmm. I wonder if this means we need to test (at least once or twice) on
a variety of JDKs:
- AdoptOpenJDK (just a packaging of OpenJDK?)
- Amazon Coretto
- Azul / Zulu
- IBM (which does still exist, even if only for James Lampert)
- OpenJDK
- Oracle
- SAP
https://dzone.com/articles/an-overview-on-jdk-vendors
I never thought these things would behave differently at their core.
I *think* it is OS differences rather than vendor differences as the
NIO2 code in question is OS specific.
I haven't tested it exhaustively, but at least Oracle (Java 7) and
Temurin (Java 11) failed on Linux and worked on MacOS.
It probably makes sense to do a review of which combinations we are
regularly testing with across the various CI systems and contributors.
On the original issue, I don't think we have any choice but to document
that NIO2 + TLS + SecurityManager may not work. I tried adding a "allow
everything to do everything" permission to the catalina.policy file but
NIO2 + TLS + SecurityManager still failed.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
