JDK-8248486 : SafeThread illegal access to java.lang private fields should be removed
  • Type: Bug
  • Component: xml
  • Sub-Component: javax.xml.parsers
  • Affected Version: 9,11,15,16
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-06-29
  • Updated: 2020-07-21
  • Resolved: 2020-07-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 16
16 b06Fixed
Related Reports
Relates :  
JDK-8056152 - (thread) API to create Threads that do not inherit inheritable thread-local initial values
Relates :  
JDK-8129892 - Cleanup use of reflection in IncrementalSAXSource_Xerces.java
Description
com.sun.org.apache.xml.internal.utils.SafeThread hacks private fields in java.lang.Thread to clear thread locals. The java.base module does not open java.lang to module java.xml so I assume it fails since JDK 9. Can the usages of SafeThread be re-examined? Can these usages be replaced with InnocuousThread?
Comments
URL: https://hg.openjdk.java.net/jdk/jdk/rev/388a0aed4809 User: joehw Date: 2020-07-13 18:20:29 +0000
13-07-2020
InnocuousThread meets all the needs. Unfortunately, it also revokes permissions that the xml parser requires. We can use the new Thread method instead for the SafeThread.
09-07-2020