https://bz.apache.org/bugzilla/show_bug.cgi?id=65714
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|REOPENED |RESOLVED
--- Comment #13 from Mark Thomas <ma...@apache.org> ---
This can't be fixed in Tomcat. Even when the security policy has an entry that
is "Allow everything to do everything" the NIO2 code still triggers security
exceptions when running under a SecurityManager. You could try raising a bug
with your JRE vendor but, give the deprecation of the SecurityManager, I
suspect that fixing this will not be a priority.
You have two options to solve this with Tomcat:
- turn off the security manager
- switch to NIO
The security manager has been deprecated in Java 17 and will eventually be
removed. Now might be a good time to start to think about migrating away from
using the SecurityManager.
There is very little between NIO and NIO2 in terms of performance. While
individual benchmarks will demonstrate one is better than the other, the
difference is typically small and in real world usage the different is smaller
still.
--
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
