We’re sorry. We could not find a match for your search.

We suggest you try the following to help find what you’re looking for:

  • Check the spelling of your keyword search.
  • Use synonyms for the keyword you typed, for example, try "application" instead of "software."
  • Start a new search.
Cloud Account Sign in to Cloud
Oracle Account
java

Consolidated JDK 17 Release Notes

Consolidated Release Notes

This page contains all of the release notes for the JDK 17 General Availability (GA) releases:

  • JDK 17.0.5 (GA and BPR builds)
  • JDK 17.0.4.1 (GA and BPR builds)
  • JDK 17.0.4 (GA and BPR builds)
  • JDK 17.0.3.1 (GA and BPR builds)
  • JDK 17.0.3 (GA and BPR builds)
  • JDK 17.0.2 (GA)
  • JDK 17.0.1 (GA)
  • JDK 17 (GA)

Java SE 17.0.5 - Bundled Patch Release (BPR) - Bug Fixes and Updates

The following sections summarize changes made in all Java SE 17.0.5 BPR releases. The BPR releases are listed below in date order, most current BPR first. Note that bug fixes in previous BPRs are also included in the current BPR.

 

Changes in Java SE 17.0.5.0.1

Bug Fixes

BugId Category Subcategory Description
JDK-8291973 install install Java RPMs Are Built with Older RPM and Thus Do Not Contain Some Necessary Hash
JDK-8294357 core-libs java.time (tz) Update Timezone Data to 2022d

Java™ SE Development Kit 17.0.5 (JDK 17.0.5)

October 18, 2022

The full version string for this update release is 17.0.5+9 (where "+" means "build"). The version number is 17.0.5.

 

IANA TZ Data 2022b, 2022c

JDK 17.0.5 contains IANA time zone data 2022b, 2022c.

  • Chile's DST is delayed by a week in September 2022.
  • Iran no longer observes DST after 2022.
  • Rename Europe/Kiev to Europe/Kyiv.
  • New zic -R option
  • Vanguard form now uses %z.
  • Finish moving duplicate-since-1970 zones to 'backzone'.
  • New build option PACKRATLIST.
  • New tailored_tarballs target, replacing rearguard_tarballs.
  • Work around awk bug in FreeBSD, macOS, etc.
  • Improve tzselect on intercontinental Zones.
For more information, refer to Timezone Data Versions in the Java Runtime.

 

Security Baselines

The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 17.0.5 are specified in the following table:

JRE Family Version JRE Security Baseline (Full Version String)
1717.0.5+9
1111.0.17+10
88u351-b10
77u361-b08

 

Keeping the JDK up to Date

Oracle recommends that the JDK is updated with each Critical Patch Update. In order to determine if a release is the latest, the Security Baseline page can be used to determine which is the latest version for each release family.

Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Bulletins. It is not recommended that this JDK (version 17.0.5) be used after the next critical patch update scheduled for January 17, 2023.

 

Other Notes

security-libs/java.security
 Disabled SHA-1 Signed JARs (JDK-8269039)

JARs signed with SHA-1 algorithms are now restricted by default and treated as if they were unsigned. This applies to the algorithms used to digest, sign, and optionally timestamp the JAR. It also applies to the signature and digest algorithms of the certificates in the certificate chain of the code signer and the Timestamp Authority, and any CRLs or OCSP responses that are used to verify if those certificates have been revoked. These restrictions also apply to signed JCE providers.

To reduce the compatibility risk for JARs that have been previously timestamped, there is one exception to this policy:

  • Any JAR signed with SHA-1 algorithms and timestamped prior to January 01, 2019 will not be restricted.

This exception may be removed in a future JDK release. To determine if your signed JARs are affected by this change, run jarsigner -verify -verbose -certs on the signed JAR, and look for instances of "SHA1" or "SHA-1" and "disabled" and a warning that the JAR will be treated as unsigned in the output.

For example:

-  Signed by "CN="Signer""

     Digest algorithm: SHA-1 (disabled)
     Signature algorithm: SHA1withRSA (disabled), 2048-bit key

WARNING: The jar will be treated as unsigned, because it is signed with a weak algorithm that is now disabled by the security property:

  jdk.jar.disabledAlgorithms=MD2, MD5, RSA keySize < 1024, DSA keySize < 1024, SHA1 denyAfter 2019-01-01

JARs affected by these new restrictions should be replaced or re-signed with stronger algorithms.

Users can, at their own risk, remove these restrictions by modifying the java.security configuration file (or override it by using the java.security.properties system property) and removing "SHA1 usage SignedJAR & denyAfter 2019-01-01" from the jdk.certpath.disabledAlgorithms security property and "SHA1 denyAfter 2019-01-01" from the jdk.jar.disabledAlgorithms security property.

core-libs/java.net
 Make HttpURLConnection Default Keep Alive Timeout Configurable (JDK-8278067)

Two system properties have been added which control the keep alive behavior of HttpURLConnection in the case where the server does not specify a keep alive time. Two properties are defined for controlling connections to servers and proxies separately. They are http.keepAlive.time.server and http.keepAlive.time.proxy respectively. More information about them can be found in Networking Properties.

core-libs/java.time
 Update Timezone Data to 2022c (JDK-8294042)

This version includes changes from 2022b that merged multiple regions that have the same timestamp data post-1970 into a single time zone data. All time zone IDs remain the same but the merged time zones will point to a shared zone data.

As a result, pre-1970 data may not be compatible with earlier JDK versions. The affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake, Pacific/Wallis, Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap.

For more details, refer to the announcement of 2022b.

 

Bug Fixes

This release also contains fixes for security vulnerabilities described in the Oracle Critical Patch Update.

Issues fixed in 17.0.5:

# JBS Component Sumary
1JDK-8285686client-libs/2dUpdate FreeType to 2.12.0
2JDK-8264666client-libs/2dChange implementation of safeAdd/safeMult in the LCMSImageLayout class
3JDK-8289853client-libs/2dUpdate HarfBuzz to 4.4.1
4JDK-8290334client-libs/2dUpdate FreeType to 2.12.1
5JDK-8274939client-libs/java.awtIncorrect size of the pixel storage is used by the robot on macOS
6JDK-8273506client-libs/java.awtjava Robot API did the 'm' keypress and caused /awt/event/KeyEvent/KeyCharTest/KeyCharTest.html is timing out on macOS 12
7JDK-8255439client-libs/java.awtSystem Tray icons get corrupted when Windows scaling changes
8JDK-8287740client-libs/javax.accessibilityNSAccessibilityShowMenuAction not working for text editors
9JDK-8284690client-libs/javax.accessibility[macos] VoiceOver : Getting java.lang.IllegalArgumentException: Invalid location on Editable JComboBox
10JDK-8284014client-libs/javax.accessibilityMenu items with submenus in JPopupMenu are not spoken on macOS
11JDK-8277497client-libs/javax.accessibilityLast column cell in the JTable row is read as empty cell
12JDK-8278609client-libs/javax.accessibility[macos] accessibility frame is misplaced on a secondary monitor on macOS
13JDK-8283383client-libs/javax.accessibility[macos] a11y : Screen magnifier shows extra characters (0) at the end JButton accessibility name
14JDK-8286266client-libs/javax.accessibility[macos] VoiceOver : Moving JTable column to be the first column JVM crashes
15JDK-8287917core-libs/java.lang:class_loadingSystem.loadLibrary does not work on Big Sur if JDK is built with macOS SDK 10.15 and earlier
16JDK-8281183core-libs/java.utilRandomGenerator:NextDouble() default behavior partially fixed by JDK-8280950
17JDK-8280950core-libs/java.utilRandomGenerator:NextDouble() default behavior non conformant after JDK-8280550 fix
18JDK-8288769core-libs/java.util.jarRevert unintentional change to deflate.c
19JDK-8283277core-libs/java.util:i18nISO 4217 Amendment 171 Update
20JDK-8289549core-libs/java.util:i18nISO 4217 Amendment 172 Update
21JDK-8276990core-svc/debuggerMemory leak in invoker.c fillInvokeRequest() during JDI operations
22JDK-8281615core-svc/debuggerDeadlock caused by jdwp agent
23JDK-8284094core-svc/debuggerMemory leak in invoker_completeInvokeRequest()
24JDK-8284848hotspot/compilerC2: Compiler blackhole arguments should be treated as globally escaping
25JDK-8282467hotspot/compileradd extra diagnostics for JDK-8268184
26JDK-8284883hotspot/compilerJVM crash: guarantee(sect->end() <= sect->limit()) failed: sanity on AVX512
27JDK-8285923hotspot/compiler[REDO] JDK-8285802 AArch64: Consistently handle offsets in MacroAssembler as 64-bit quantities
28JDK-8282555hotspot/compilerMissing memory edge when spilling MoveF2I, MoveD2L etc
29JDK-8286638hotspot/compilerC2: CmpU needs to do more precise over/underflow analysis
30JDK-8288303hotspot/compilerC1: Miscompilation due to broken Class.getModifiers intrinsic
31JDK-8270090hotspot/compilerC2: LCM may prioritize CheckCastPP nodes over projections
32JDK-8280696hotspot/compilerC2 compilation hits assert(is_dominator(c, n_ctrl)) failed
33JDK-8285820hotspot/compilerC2: LCM prioritizes locally dependent CreateEx nodes over projections after 8270090
34JDK-8287091hotspot/compileraarch64 : guarantee(val < (1ULL << nbits)) failed: Field too big for insn
35JDK-8287396hotspot/compilerLIR_Opr::vreg_number() and data() can return negative number
36JDK-8286625hotspot/compilerC2 fails with assert(!n->is_Store() && !n->is_LoadStore()) failed: no node with a side effect
37JDK-8288467hotspot/compilerremove memory_operand assert for spilled instructions
38JDK-8276546hotspot/compiler[IR Framework] Whitelist and ignore CompileThreshold
39JDK-8279622hotspot/compilerC2: miscompilation of map pattern as a vector reduction
40JDK-8286177hotspot/compilerC2: "failed: non-reduction loop contains reduction nodes" assert failure
41JDK-8284944hotspot/compilerassert(cnt++ < 40) failed: infinite cycle in loop optimization
42JDK-8287223hotspot/compilerC1: Inlining attempt through MH::invokeBasic() with null receiver
43JDK-8272736hotspot/compiler[JVMCI] Add API for reading and writing JVMCI thread locals
44JDK-8284358hotspot/compilerUnreachable loop is not removed from C2 IR, leading to a broken graph
45JDK-8288360hotspot/compilerCI: ciInstanceKlass::implementor() is not consistent for well-known classes
46JDK-8288781hotspot/compilerC1: LIR_OpVisitState::maxNumberOfOperands too small
47JDK-8287432hotspot/compilerC2: assert(tn->in(0) != __null) failed: must have live top node
48JDK-8283441hotspot/compilerC2: segmentation fault in ciMethodBlocks::make_block_at(int)
49JDK-8289127hotspot/compilerApache Lucene triggers: DEBUG MESSAGE: duplicated predicate failed which is impossible
50JDK-8286314hotspot/compilerTrampoline not created for far runtime targets outside small CodeCache
51JDK-8281297hotspot/gcTestStressG1Humongous fails with guarantee(is_range_uncommitted)
52JDK-8283597hotspot/jvmti[REDO] Invalid generic signature for redefined classes
53JDK-8278753hotspot/runtimeRuntime crashes with access violation during JNI_CreateJavaVM call
54JDK-8283469hotspot/runtimeDon't use memset to initialize members in FileMapInfo and fix memory leak
55JDK-8268773hotspot/runtimeImprovements related to: Failed to start thread - pthread_create failed (EAGAIN)
56JDK-8289477hotspot/runtimeMemory corruption with CPU_ALLOC, CPU_FREE on muslc
57JDK-8289799hotspot/runtimeBuild warning in methodData.cpp memset zero-length parameter
58JDK-8290417hotspot/runtimeCDS cannot archive lamda proxy with useImplMethodHandle
59JDK-8287107hotspot/runtimeCgroupSubsystemFactory.setCgroupV2Path asserts with freezer controller
60JDK-8287741hotspot/runtimeFix of JDK-8287107 (unused cgv1 freezer controller) was incomplete
61JDK-8283723infrastructureUpdate Visual Studio 2022 to version 17.1.0 for Oracle builds on Windows
62JDK-8275887security-libs/java.securityjarsigner prints invalid digest/signature algorithm warnings if keysize is weak/disabled
63JDK-8281628security-libs/javax.cryptoKeyAgreement : generateSecret intermittently not resetting
64JDK-8284694security-libs/javax.net.sslAvoid evaluating SSLAlgorithmConstraints twice
65JDK-8286211security-libs/javax.smartcardioUpdate PCSC-Lite for SUSE Linux to 1.9.5
66JDK-8285398security-libs/jdk.securityCache the results of constraint checks
67JDK-8155701tools/javacThe compiler fails with an AssertionError: typeSig ERROR
68JDK-8281316tools/javacjavac performance issues with large number of jars on classpath
69JDK-8282214tools/javadoc(tool)Upgrade JQuery to version 3.6.0
70JDK-8284367tools/javadoc(tool)JQuery UI upgrade from 1.12.1 to 1.13.1
71JDK-8277494tools/jpackage[BACKOUT] JDK-8276150 Quarantined jpackage apps are labeled as "damaged"
72JDK-8284675tools/jpackage"jpackage.exe" creates application launcher without Windows Application Manfiest
73JDK-8276837tools/jpackage[macos]: Error when signing the additional launcher
74JDK-8278311tools/jpackageDebian packaging doesn't work
75JDK-8279370tools/jpackagejdk.jpackage/share/native/applauncher/JvmLauncher.cpp fails to build with GCC 6.3.0
76JDK-8284067tools/jpackagejpackage'd launcher reports non-zero exit codes with error prompt
77JDK-8289486xml/jaxpImprove XSLT XPath operators count efficiency

Java SE 17.0.4.1 - Bundled Patch Release (BPR) - Bug Fixes and Updates

The following sections summarize changes made in all Java SE 17.0.4.1 BPR releases. The BPR releases are listed below in date order, most current BPR first. Note that bug fixes in previous BPRs are also included in the current BPR.

 

Changes in Java SE 17.0.4.1.1

Fixes from the prior BPR are included in this version.


Java™ SE Development Kit 17, Patch 17.0.4.1 (JDK 17.0.4.1)

August 18, 2022

The full version string for this update release is 17.0.4.1+1 (where "+" means "build"). The version number is 17.0.4.1.

 

IANA TZ Data 2022a

For more information, refer to Timezone Data Versions in the JRE Software.

 

Security Baselines

The security baselines are unchanged from the release of JDK 17.0.4.

JRE Family Version JRE Security Baseline (Full Version String)
17 17.0.4+11
11 11.0.16+11
8 8u341-b10
7 7u351-b07

Keeping the JDK up to Date

Oracle recommends that the JDK is updated with each Critical Patch Update. In order to determine if a release is the latest, the Security Baseline page can be used to determine which is the latest version for each release family.

Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Bulletins. It is not recommended that this JDK (version 17.0.4.1) be used after the next critical patch update scheduled for October 18, 2022.

Oracle recommends that all JDK 17 users, even those that have already updated to 17.0.4, uptake the 17.0.4.1 patch release.

 

Changes

hotspot/compiler
 C2 Compilation Errors Unpredictably Crashes JVM

Fixes a regression in the C2 JIT compiler which caused the Java Runtime to crash unpredictably.


Java SE 17.0.4 - Bundled Patch Release (BPR) - Bug Fixes and Updates

The following sections summarize changes made in all Java SE 17.0.4 BPR releases. The BPR releases are listed below in date order, most current BPR first. Note that bug fixes in previous BPRs are also included in the current BPR.

 

Changes in Java SE 17.0.4.0.1

Bug Fixes

BugId Category Subcategory Description
JDK-8255439 client-libs java.awt System Tray icons get corrupted when windows scaling changes

Java™ SE Development Kit 17.0.4 (JDK 17.0.4)

July 19, 2022

The full version string for this update release is 17.0.4+11 (where "+" means "build"). The version number is 17.0.4.

 

IANA TZ Data 2022a

For more information, refer to Timezone Data Versions in the JRE Software.

 

Security Baselines

The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 17.0.4 are specified in the following table:

JRE Family Version JRE Security Baseline (Full Version String)
1717.0.4+11
1111.0.16+11
88u341-b10
77u351-b07

 

Keeping the JDK up to Date

Oracle recommends that the JDK is updated with each Critical Patch Update. In order to determine if a release is the latest, the Security Baseline page can be used to determine which is the latest version for each release family.

Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Bulletins. It is not recommended that this JDK (version 17.0.4) be used after the next critical patch update scheduled for October 18, 2022.

New Features

core-libs/java.net
 HTTPS Channel Binding Support for Java GSS/Kerberos

Support has been added for TLS channel binding tokens for Negotiate/Kerberos authentication over HTTPS through javax.net.HttpsURLConnection.

Channel binding tokens are increasingly required as an enhanced form of security which can mitigate certain kinds of socially engineered, man in the middle (MITM) attacks. They work by communicating from a client to a server the client's understanding of the binding between connection security (as represented by a TLS server cert) and higher level authentication credentials (such as a username and password). The server can then detect if the client has been fooled by a MITM and shutdown the session/connection.

The feature is controlled through a new system property jdk.https.negotiate.cbt which is described fully in the Networking Properties page.

Other Notes

core-libs/java.net
 Update java.net.InetAddress to Detect Ambiguous IPv4 Address Literals

The java.net.InetAddress class has been updated to strictly accept IPv4 address literals in decimal quad notation. The InetAddress class methods are updated to throw an java.net.UnknownHostException for invalid IPv4 address literals. To disable this check, the new "jdk.net.allowAmbiguousIPAddressLiterals" system property can be set to "true".

See JDK-8277608 (not public)
core-libs/java.util.jar
 Default JDK Compressor Will Be Closed when IOException Is Encountered

DeflaterOutputStream.close() and GZIPOutputStream.finish() methods have been modified to close out the associated default JDK compressor before propagating a Throwable up the stack. ZIPOutputStream.closeEntry() method has been modified to close out the associated default JDK compressor before propagating an IOException, not of type ZipException, up the stack.

hotspot/runtime
 CPU Shares Ignored When Computing Active Processor Count

Previous JDK releases used an incorrect interpretation of the Linux cgroups parameter "cpu.shares". This might cause the JVM to use fewer CPUs than available, leading to an under utilization of CPU resources when the JVM is used inside a container.

Starting from this JDK release, by default, the JVM no longer considers "cpu.shares" when deciding the number of threads to be used by the various thread pools. The -XX:+UseContainerCpuShares command-line option can be used to revert to the previous behavior. This option is deprecated and may be removed in a future JDK release.

 

Bug Fixes

This release also contains fixes for security vulnerabilities described in the Oracle Critical Patch Update.

Issues fixed in 17.0.4:

# JBS Component Subcomponent Sumary
1JDK-8283217client-libs2dLeak FcObjectSet in getFontConfigLocations() in fontpath.c
2JDK-8278604client-libsdemoSwingSet2 table demo does not have accessible description set for images
3JDK-8274751client-libsjava.awtDrag And Drop hangs on Windows
4JDK-8278526client-libsjavax.accessibility[macos] Screen reader reads SwingSet2 JTable row selection as null, dimmed row for last column
5JDK-8279586client-libsjavax.accessibility[macos] custom JCheckBox and JRadioBox with custom icon set: focus is still displayed after unchecking
6JDK-8277922client-libsjavax.accessibilityUnable to click JCheckBox in JTable through Java Access Bridge
7JDK-8274735client-libsjavax.imageiojavax.imageio.IIOException: Unsupported Image Type while processing a valid JPEG image
8JDK-8279842core-libsjava.netHTTPS Channel Binding support for Java GSS/Kerberos
9JDK-8282293core-libsjava.netDomain value for system property jdk.https.negotiate.cbt should be case-insensitive
10JDK-8282929core-libsjava.textLocalized monetary symbols are not reflected in `toLocalizedPattern` return value
11JDK-8280543docshotspotUpdate the "java" and "jcmd" tool specification for CDS
12JDK-8279219hotspotcompiler[REDO] C2 crash when allocating array of size too large
13JDK-8278796hotspotcompilerIncorrect behavior of FloatVector.withLane on X86
14JDK-8277906hotspotcompilerIncorrect type for IV phi of long counted loops after CCP
15JDK-8268231hotspotcompilerAarch64: Use Ldp in intrinsics for String.compareTo
16JDK-8273139hotspotcompilerC2: assert(f <= 1 && f >= 0) failed: Incorrect frequency
17JDK-8280799hotspotcompilerС2: assert(false) failed: cyclic dependency prevents range check elimination
18JDK-8265317hotspotcompiler[vector] assert(payload->is_object()) failed: expected 'object' value for scalar-replaced boxed vector but got: NULL
19JDK-8283451hotspotcompilerC2: assert(_base == Long) failed: Not a Long
20JDK-8282592hotspotcompilerC2: assert(false) failed: graph should be schedulable
21JDK-8282590hotspotcompilerC2: assert(addp->is_AddP() && addp->outcnt() > 0) failed: Don't process dead nodes
22JDK-8282312hotspotcompilerMinor corrections to evbroadcasti32x4 intrinsic on x86
23JDK-8281811hotspotcompilerassert(_base == Tuple) failed: Not a Tuple after JDK-8280799
24JDK-8275854hotspotcompilerC2: assert(stride_con != 0) failed: missed some peephole opt
25JDK-8275638hotspotcompilerGraphKit::combine_exception_states fails with "matching stack sizes" assert
26JDK-8256368hotspotcompilerAvoid repeated upcalls into Java to re-resolve MH/VH linkers/invokers
27JDK-8283641hotspotcompilerLarge value for CompileThresholdScaling causes assert
28JDK-8283408hotspotcompilerFix a C2 crash when filling arrays with unsafe
29JDK-8280867hotspotcompilerCpuid1Ecx feature parsing is incorrect for AMD CPUs
30JDK-8280600hotspotcompilerC2: assert(!had_error) failed: bad dominance
31JDK-8279837hotspotcompilerC2: assert(is_Loop()) failed: invalid node class: Region
32JDK-8279668hotspotcompilerx86: AVX2 versions of vpxor should be asserted
33JDK-8275337hotspotcompilerC1: assert(false) failed: live_in set of first block must be empty
34JDK-8274983hotspotcompilerC1 optimizes the invocation of private interface methods
35JDK-8280901hotspotcompilerMethodHandle::linkToNative stub is missing w/ -Xint
36JDK-8280526hotspotcompilerx86_32 Math.sqrt performance regression with -XX:UseSSE={0,1}
37JDK-8279356hotspotcompilerMethod linking fails with guarantee(mh->adapter() != NULL) failed: Adapter blob must already exist!
38JDK-8278948hotspotcompilercompiler/vectorapi/reshape/TestVectorCastAVX1.java crashes in assembler
39JDK-8277180hotspotcompilerIntrinsify recursive ObjectMonitor locking for C2 x64 and A64
40JDK-8282874hotspotcompilerBad performance on gather/scatter API caused by different IntSpecies of indexMap
41JDK-8281266hotspotcompiler[JVMCI] MetaUtil.toInternalName() doesn't handle hidden classes correctly
42JDK-8279515hotspotcompilerC1: No inlining through invokedynamic and invokestatic call sites when resolved class is not linked
43JDK-8279822hotspotcompilerCI: Constant pool entries in error state are not supported
44JDK-8279560hotspotcompilerAArch64: generate_compare_long_string_same_encoding and LARGE_LOOP_PREFETCH alignment
45JDK-8279437hotspotcompiler[JVMCI] exception in HotSpotJVMCIRuntime.translate can exit the VM
46JDK-8275830hotspotcompilerC2: Receiver downcast is missing when inlining through method handle linkers
47JDK-8282231hotspotcompilerx86-32: runtime call to SharedRuntime::ldiv corrupts registers
48JDK-8282295hotspotruntimeSymbolPropertyEntry::set_method_type fails with assert
49JDK-8281274hotspotruntimedeal with ActiveProcessorCount in os::Linux::print_container_info
50JDK-8281275hotspotruntimeUpgrading from 8 to 11 no longer accepts '/' as filepath separator in gc paths
51JDK-8281181hotspotruntimeDo not use CPU Shares to compute active processor count
52JDK-8278553hotspottestRunThese30M.java failed due to errors in JckStressModule.out
53JDK-8281517installinstallImprove the error message shown when a user tries to install the aarch64 bundle on an intel mac
54JDK-8278851security-libsjava.securityCorrect signer logic for jars signed with multiple digest algorithms
55JDK-8255266security-libsjava.securityUpdate Public Suffix List to 3c213aa
56JDK-8274524security-libsjavax.net.sslSSLSocket.close() hangs if it is called during the ssl handshake
57JDK-8275082security-libsjavax.xml.cryptoUpdate XML Security for Java to 2.3.0
58JDK-8279520security-libsorg.ietf.jgssSPNEGO has not passed channel binding info into the underlying mechanism
59JDK-8277165toolsjdeps --multi-release --print-module-deps fails if module-info.class in different versioned directories
60JDK-8225559toolsjavacassertion error at TransTypes.visitApply

Java SE 17.0.3.1 - Bundled Patch Release (BPR) - Bug Fixes and Updates

The following sections summarize changes made in all Java SE 17.0.3 BPR releases. The BPR releases are listed below in date order, most current BPR first. Note that bug fixes in previous BPRs are also included in the current BPR.

Changes in Java SE 17.0.3.1.1

Fixes from the prior BPR are included in this version.


Java™ SE Development Kit 17, Patch 17.0.3.1 (JDK 17.0.3.1)

May 2, 2022

The full version string for this update release is 17.0.3.1+2 (where "+" means "build"). The version number is 17.0.3.1.

 

IANA TZ Data 2022a

For more information, refer to Timezone Data Versions in the JRE Software.

 

Security Baselines

The security baselines are unchanged from the release of JDK 17.0.3.

JRE Family Version JRE Security Baseline (Full Version String)
17 17.0.3+8
11 11.0.15+8
8 8u331-b09
7 7u341-b08

Keeping the JDK up to Date

Oracle recommends that the JDK is updated with each Critical Patch Update. In order to determine if a release is the latest, the Security Baseline page can be used to determine which is the latest version for each release family.

Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Bulletins. It is not recommended that this JDK (version 17.0.3.1) be used after the next critical patch update scheduled for July 19, 2022.

 

Changes

 

core-libs/java.io
 New System Property to Disable Windows Alternate Data Stream Support in java.io.File

The Windows implementation of java.io.File allows access to NTFS Alternate Data Streams (ADS) by default. Such streams have a structure like “filename:streamname”. A system property jdk.io.File.enableADS has been added to control this behavior. To disable ADS support in java.io.File, the system property jdk.io.File.enableADS should be set to false (case ignored). Stricter path checking however prevents the use of special devices such as NUL:

See JDK-8285445

 

Bug Fixes

This release is based on the previous CPU and does not contain any additional security fixes. The following issues have also been resolved:

JBS Component Subcomponent Sumary
JDK-8284920 xml javax.xml.path Incorrect Token type causes XPath expression to return incorrect results
JDK-8284548 xml jaxp Invalid XPath expression causes StringIndexOutOfBoundsException


Java SE 17.0.3 - Bundled Patch Release (BPR) - Bug Fixes and Updates

The following sections summarize changes made in all Java SE 17.0.3 BPR releases. The BPR releases are listed below in date order, most current BPR first. Note that bug fixes in previous BPRs are also included in the current BPR.

 

Changes in Java SE 17.0.3.0.1

Bug Fixes

BugId Category Subcategory Description
JDK-8281181 hotspot runtime Do not use CPU Shares to compute active processor count
JDK-8282583 xml jaxp Update BCEL md to include the copyright notice
JDK-8283350 core-libs java.time (tz) Update Timezone Data to 2022a

Java™ SE Development Kit 17.0.3 (JDK 17.0.3)

April 19, 2022

The full version string for this update release is 17.0.3+8 (where "+" means "build"). The version number is 17.0.3.

 

IANA TZ Data 2021e

For more information, refer to Timezone Data Versions in the JRE Software.

 

Security Baselines

The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 17.0.3 are specified in the following table:

JRE Family Version JRE Security Baseline (Full Version String)
17 17.0.3+8
11 11.0.15+8
8 8u331-b09
7 7u341-b08

 

Keeping the JDK up to Date

Oracle recommends that the JDK is updated with each Critical Patch Update. In order to determine if a release is the latest, the Security Baseline page can be used to determine which is the latest version for each release family.

Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Bulletins. It is not recommended that this JDK (version 17.0.3) be used after the next critical patch update scheduled for July 19, 2022.

 

New Features

xml/jaxp
 New XML Processing Limits

Three processing limits have been added to the XML libraries. These are:

  • jdk.xml.xpathExprGrpLimit

Description: Limits the number of groups an XPath expression can contain.

Type: integer

Value: A positive integer. A value less than or equal to 0 indicates no limit. If the value is not an integer, a NumberFormatException is thrown. Default 10.

  • jdk.xml.xpathExprOpLimit

Description: Limits the number of operators an XPath expression can contain.

Type: integer

Value: A positive integer. A value less than or equal to 0 indicates no limit. If the value is not an integer, a NumberFormatException is thrown. Default 100.

  • jdk.xml.xpathTotalOpLimit

Description: Limits the total number of XPath operators in an XSL Stylesheet.

Type: integer

Value: A positive integer. A value less than or equal to 0 indicates no limit. If the value is not an integer, a NumberFormatException is thrown. Default 10000.

Supported processors

  • jdk.xml.xpathExprGrpLimit and jdk.xml.xpathExprOpLimit are supported by the XPath processor.

  • All three limits are supported by the XSLT processor.

Setting properties

For the XSLT processor, the properties can be changed through the TransformerFactory. For example,

        TransformerFactory factory = TransformerFactory.newInstance();

        factory.setAttribute("jdk.xml.xpathTotalOpLimit", "1000");

For both the XPath and XSLT processors, the properties can be set through the system property and jaxp.properties configuration file located in the conf directory of the Java installation. For example,

        System.setProperty("jdk.xml.xpathExprGrpLimit", "20");

or in the jaxp.properties file,

        jdk.xml.xpathExprGrpLimit=20

 

There are two known issues:

  1. An XPath expression that contains a short form of the parent axis ".." can return incorrect results. See JDK-8284920 for details.
  2. An invalid XPath expression that ends with a relational operator such as ‘<’ ‘>’ and ‘=’ will cause the processor to erroneously throw StringIndexOutOfBoundsException instead of XPathExpressionException. See JDK-8284548 for details.
JDK-8270504 (not public)

Other Notes

security-libs/java.security
 Only Expose Certificates With Proper Trust Settings as Trusted Certificate Entries in macOS KeychainStore

On macOS, only certificates with proper trust settings in the user keychain will be exposed as trusted certificate entries in the KeychainStore type of keystore. Also, calling the KeyStore::setCertificateEntry method or the keytool -importcert command on a KeychainStore keystore now fails with a KeyStoreException. Instead, call the macOS "security add-trusted-cert" command to add a trusted certificate into the user keychain.

JDK-8278449 (not public)

core-libs/javax.naming
 Parsing of URL Strings in Built-in JNDI Providers Is More Strict

The parsing of URLs in the LDAP, DNS, and RMI built-in JNDI providers has been made more strict. The strength of the parsing can be controlled by system properties:

  -Dcom.sun.jndi.ldapURLParsing="legacy" | "compat" | "strict"    (to control "ldap:" URLs)

  -Dcom.sun.jndi.dnsURLParsing="legacy" | "compat" | "strict"     (to control "dns:" URLs)
  -Dcom.sun.jndi.rmiURLParsing="legacy" | "compat" | "strict"     (to control "rmi:" URLs)

 

The default value is "compat" for all of the three providers.

  • The "legacy" mode turns the new validation off.
  • The "compat" mode limits incompatibilities.
  • The "strict" mode is stricter and may cause regression by rejecting URLs that an application might consider as valid.

In "compat" and "strict" mode, more validation is performed. As an example, in the URL authority component, the new parsing only accepts brackets around IPv6 literal addresses. Developers are encouraged to use java.net.URI constructors or its factory method to build URLs rather than handcrafting URL strings.

If an illegal URL string is found, a java.lang.IllegalArgumentException or a javax.naming.NamingException (or a subclass of it) is raised.

JDK-8278972 (not public)

 

Bug Fixes

This release also contains fixes for security vulnerabilities described in the Oracle Critical Patch Update.

Issues fixed in 17.0.3:

# JBS Component Subcomponent Sumary
1 JDK-8270874 client-libs 2d JFrame paint artifacts when dragged from standard monitor to HiDPI monitor
2 JDK-8275650 core-libs java.io Problemlist java/io/File/createTempFile/SpecialTempFile.java for Windows 11
3 JDK-8279833 core-libs java.lang Loop optimization issue in String.encodeUTF8_UTF16
4 JDK-8274658 core-libs java.util:i18n ISO 4217 Amendment 170 Update
5 JDK-8277795 core-libs javax.naming LDAP connection timeout not honoured under contention
6 JDK-8277777 hotspot compiler [Vector API] assert(r->is_XMMRegister()) failed: must be in x86_32.ad
7 JDK-8277441 hotspot compiler CompileQueue::add fails with assert(_last->next() == __null) failed: not last
8 JDK-8275610 hotspot compiler C2: Object field load floats above its null check resulting in a segfault
9 JDK-8275326 hotspot compiler C2: assert(no_dead_loop) failed: dead loop detected
10 JDK-8262134 hotspot compiler compiler/uncommontrap/TestDeoptOOM.java failed with "guarantee(false) failed: wrong number of expression stack elements during deopt"
11 JDK-8277447 hotspot compiler Hotspot C1 compiler crashes on Kotlin suspend fun with loop
12 JDK-8273277 hotspot compiler C2: Move conditional negation into rc_predicate
13 JDK-8271202 hotspot compiler C1: assert(false) failed: live_in set of first block must be empty
14 JDK-8275645 hotspot compiler [JVMCI] avoid unaligned volatile reads on AArch64
15 JDK-8271056 hotspot compiler C2: "assert(no_dead_loop) failed: dead loop detected" due to cmoving identity
16 JDK-8275643 hotspot compiler C2's unaryOp vector intrinsic does not properly handle LongVector.neg
17 JDK-8275847 hotspot compiler Scheduling fails with "too many D-U pinch points" on small method
18 JDK-8275874 hotspot compiler [JVMCI] only support aligned reads in c2v_readFieldValue
19 JDK-8279076 hotspot compiler C2: Bad AD file when matching SqrtF with UseSSE=0
20 JDK-8275330 hotspot compiler C2: assert(n->is_Root() || n->is_Region() || n->is_Phi() || n->is_MachMerge() || def_block->dominates(block)) failed: uses must be dominated by definitions
21 JDK-8276314 hotspot compiler [JVMCI] check alignment of call displacement during code installation
22 JDK-8279225 hotspot compiler [arm32] C1 longs comparison operation destroys argument registers
23 JDK-8279412 hotspot compiler [JVMCI] failed speculations list must outlive any nmethod that refers to it
24 JDK-8278871 hotspot compiler [JVMCI] assert((uint)reason < 2* _trap_hist_limit) failed: oob
25 JDK-8278824 hotspot gc Uneven work distribution when scanning heap roots in G1
26 JDK-8276177 hotspot jvmti nsk/jvmti/RedefineClasses/StressRedefineWithoutBytecodeCorruption failed with "assert(def_ik->is_being_redefined()) failed: should be being redefined to get here"
27 JDK-8275800 hotspot jvmti Redefinition leaks MethodData::_extra_data_lock
28 JDK-8278239 hotspot jvmti vmTestbase/nsk/jvmti/RedefineClasses/StressRedefine failed with EXCEPTION_ACCESS_VIOLATION at 0x000000000000000d
29 JDK-8276184 hotspot runtime Exclude lambda proxy class from the CDS archive if its caller class is excluded
30 JDK-8274714 hotspot runtime Incorrect verifier protected access error message
31 JDK-8277342 hotspot runtime vmTestbase/nsk/stress/strace/strace004.java fails with SIGSEGV in InstanceKlass::jni_id_for
32 JDK-8276662 hotspot runtime Scalability bottleneck in SymbolTable::lookup_common()
33 JDK-8266490 hotspot runtime Extend the OSContainer API to support the pids controller of cgroups
34 JDK-8278020 hotspot runtime ~13% variation in Renaissance-Scrabble
35 JDK-8278384 hotspot runtime Bytecodes::result_type() for arraylength returns T_VOID instead of T_INT
36 JDK-8273967 hotspot runtime gtest os.dll_address_to_function_and_library_name_vm fails on macOS12
37 JDK-8274753 hotspot runtime ZGC: SEGV in MetaspaceShared::link_shared_classes
38 JDK-8274944 hotspot runtime AppCDS dump causes SEGV in VM thread while adjusting lambda proxy class info
39 JDK-8273526 hotspot runtime Extend the OSContainer API pids controller with pids.current
40 JDK-8274935 hotspot runtime dumptime_table has stale entry
41 JDK-8278309 hotspot runtime [windows] use of uninitialized OSThread::_state
42 JDK-8273341 hotspot runtime Update Siphash to version 1.0
43 JDK-8278951 hotspot runtime containers/cgroup/PlainRead.java fails on Ubuntu 21.10
44 JDK-8265150 hotspot svc AsyncGetCallTrace crashes on ResourceMark
45 JDK-8269849 hotspot test vmTestbase/gc/gctests/PhantomReference/phantom002/TestDescription.java failed with "OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects"
46 JDK-8273682 tools jshell Upgrade Jline to 3.20.0
47 JDK-8276141 xml jaxp XPathFactory set/getProperty method
48 JDK-8282761 xml jaxp XPathFactoryImpl remove setProperty and getProperty methods

Java™ SE Development Kit 17.0.2 (JDK 17.0.2)

January 18, 2022

The full version string for this update release is 17.0.2+8 (where "+" means "build"). The version number is 17.0.2.

 

IANA TZ Data 2021b, 2021c, 2021d, 2021e

JDK 17.0.2 contains IANA time zone data 2021b, 2021c, 2021d, 2021e.
  • Jordan now starts DST on February's last Thursday.
  • Samoa no longer observes DST.
  • Merge more location-based Zones whose timestamps agree since 1970.
  • Move some backward-compatibility links to 'backward'.
  • Rename Pacific/Enderbury to Pacific/Kanton.
  • Correct many pre-1993 transitions in Malawi, Portugal, etc.
  • zic now creates each output file or link atomically.
  • zic -L no longer omits the POSIX TZ string in its output.
  • zic fixes for truncation and leap second table expiration.
  • zic now follows POSIX for TZ strings using all-year DST.
  • Fix some localtime crashes and bugs in obscure cases.
  • zdump -v now outputs more-useful boundary cases.
  • tzfile.5 better matches a draft successor to RFC 8536.
  • A new file SECURITY.
  • Revert most 2021b changes to 'backward'.
  • Fix 'zic -b fat' bug in pre-1970 32-bit data.
  • Fix two Link line typos.
  • Distribute SECURITY file.

This release is intended as a bugfix release, to fix compatibility problems and typos reported since 2021b was released.

  • Fiji suspends DST for the 2021/2022 season.
  • 'zic -r' marks unspecified timestamps with "-00".
  • Palestine will fall back 10-29 (not 10-30) at 01:00.
For more information, refer to Timezone Data Versions in the JRE Software.

 

Security Baselines

The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 17.0.2 are specified in the following table:

JRE Family Version JRE Security Baseline (Full Version String)
17 17.0.2+8
11 11.0.14+8
8 8u321-b07
7 7u331-b06

 

Keeping the JDK up to Date

Oracle recommends that the JDK is updated with each Critical Patch Update. In order to determine if a release is the latest, the Security Baseline page can be used to determine which is the latest version for each release family.

Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Bulletins. It is not recommended that this JDK (version 17.0.2) be used after the next critical patch update scheduled for April 19, 2022.

 

Removed Features and Options

security-libs/java.security
 Removed Google's GlobalSign Root Certificate

The following root certificate from Google has been removed from the cacerts keystore:

+ alias name "globalsignr2ca [jdk]"

  Distinguished Name: CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R2

Other Notes

install/install
 Extended Delay Before JDK Executable Installer Starts From Network Drive

On Windows 11 and Windows Server 2022, there can be some slowness with the extraction of temporary installation files when launched from a mapped network drive. The installer will still work, but there can be a temporary delay.

JDK-8274002 (not public)

core-libs/java.io
 file.encoding System Property Has an Incorrect Value on Windows

The initialization of the file.encoding system property on non macOS platforms has been reverted to align with the behavior on or before JDK 11. This has been an issue especially on Windows where the system and user's locales are not the same.

core-libs/java.nio
 Zip File System Provider Throws ZipException When Entry Name Element Contains "." or ".."

The ZIP file system provider has been changed to reject existing ZIP files that contain entries with "." or ".." in name elements. ZIP files with these entries cannot be used as a file system. Invoking the java.nio.file.FileSystems.newFileSystem(...) methods throw ZipException if the ZIP file contains these entries.

core-libs/java.time
 Update Timezone Data to 2021c

IANA Time Zone Database, on which JDK's Date/Time libraries are based, has made a tweak to some time zone rules since 2021c. Note that since this update, some of the time zone rules prior to the year 1970 have been modified according to the changes which were introduced with 2021b. For more detail, refer to the announcement of 2021b

hotspot/gc
 ZGC: Fixed long Process Non-Strong References times

A bug has been fixed that could cause long "Concurrent Process Non-Strong References" times with ZGC. The bug blocked the GC from making significant progress, and caused both latency and throughput issues for the Java application.

The long times could be seen in the GC logs when running with -Xlog:gc*:

[17606.140s][info][gc,phases ] GC(719) Concurrent Process Non-Strong References 25781.928ms

 

Bug Fixes

This release also contains fixes for security vulnerabilities described in the Oracle Critical Patch Update.

Issues fixed in 17.0.2:

# JBS Component Subcomponent Sumary
1 JDK-8269637 client-libs javax/swing/JFileChooser/FileSystemView/SystemIconTest.java fails on windows
2 JDK-8262031 client-libs Create implementation for NSAccessibilityNavigableStaticText protocol
3 JDK-8267387 client-libs Create implementation for NSAccessibilityOutline protocol
4 JDK-8275872 client-libs 2d Sync J2DBench run and analyze Makefile targets with build.xml
5 JDK-8271718 client-libs 2d Crash when during color transformation the color profile is replaced
6 JDK-8273135 client-libs 2d java/awt/color/ICC_ColorSpace/MTTransformReplacedProfile.java crashes in liblcms.dylib with NULLSeek+0x7
7 JDK-8273887 client-libs 2d [macos] java/awt/color/ICC_ColorSpace/MTTransformReplacedProfile.java timed out
8 JDK-8276905 client-libs 2d Use appropriate macosx_version_minimum value while compiling metal shaders
9 JDK-8273808 client-libs java.awt Cleanup AddFontsToX11FontPath
10 JDK-8275131 client-libs java.awt Exceptions after a touchpad gesture on macOS
11 JDK-8274326 client-libs javax.accessibility [macos] Ensure initialisation of sun/lwawt/macosx/CAccessibility in JavaComponentAccessibility.m
12 JDK-8274056 client-libs javax.accessibility JavaAccessibilityUtilities leaks JNI objects
13 JDK-8274381 client-libs javax.accessibility missing CAccessibility definitions in JNI code
14 JDK-8267385 client-libs javax.accessibility Create NSAccessibilityElement implementation for JavaComponentAccessibility
15 JDK-8267388 client-libs javax.accessibility Create implementation for NSAccessibilityTable protocol
16 JDK-8274383 client-libs javax.accessibility JNI call of getAccessibleSelection on a wrong thread
17 JDK-8277195 client-libs javax.accessibility missing CAccessibility definition in [CommonComponentAccessibility accessibilityHitTest]
18 JDK-8271071 client-libs javax.accessibility accessibility of a table on macOS lacks cell navigation
19 JDK-8275809 client-libs javax.accessibility crash in [CommonComponentAccessibility getCAccessible:withEnv:]
20 JDK-8273678 client-libs javax.accessibility TableAccessibility and TableRowAccessibility miss autorelease
21 JDK-8275071 client-libs javax.accessibility [macos] A11y cursor gets stuck when combobox is closed
22 JDK-8275819 client-libs javax.accessibility [TableRowAccessibility accessibilityChildren] method is ineffective
23 JDK-8270893 client-libs javax.imageio IndexOutOfBoundsException while reading large TIFF file
24 JDK-8269951 client-libs javax.swing [macos] Focus not painted in JButton when setBorderPainted(false) is invoked
25 JDK-8266510 client-libs javax.swing Nimbus JTree default tree cell renderer does not use selected text color
26 JDK-8271895 client-libs javax.swing UnProblemList javax/swing/JComponent/7154030/bug7154030.java in JDK18
27 JDK-8268284 client-libs javax.swing javax/swing/JComponent/7154030/bug7154030.java fails with "Exception: Failed to hide opaque button"
28 JDK-8264287 client-libs javax.swing Create implementation for NSAccessibilityComboBox protocol peer
29 JDK-8264303 client-libs javax.swing Create implementation for NSAccessibilityTabGroup protocol peer
30 JDK-8264292 client-libs javax.swing Create implementation for NSAccessibilityList protocol peer
31 JDK-8264286 client-libs javax.swing Create implementation for NSAccessibilityColumn protocol peer
32 JDK-8264291 client-libs javax.swing Create implementation for NSAccessibilityCell protocol peer
33 JDK-8264298 client-libs javax.swing Create implementation for NSAccessibilityRow protocol peer
34 JDK-8271315 client-libs javax.swing Redo: Nimbus JTree renderer properties persist across L&F changes
35 JDK-8264293 client-libs javax.swing Create implementation for NSAccessibilityMenu protocol peer
36 JDK-8264295 client-libs javax.swing Create implementation for NSAccessibilityMenuItem protocol peer
37 JDK-8264294 client-libs javax.swing Create implementation for NSAccessibilityMenuBar protocol peer
38 JDK-8264296 client-libs javax.swing Create implementation for NSAccessibilityPopUpButton protocol peer
39 JDK-8264297 client-libs javax.swing Create implementation for NSAccessibilityProgressIndicator protocol peer
40 JDK-8269850 core-libs Most JDK releases report macOS version 12 as 10.16 instead of 12.0
41 JDK-8276572 core-libs Fake libsyslookup.so library causes tooling issues
42 JDK-8273450 core-libs Fix the copyright header of SVML files
43 JDK-8275145 core-libs java.io file.encoding system property has an incorrect value on Windows
44 JDK-8277093 core-libs java.io:serialization Vector should throw ClassNotFoundException for a missing class of an element
45 JDK-8275703 core-libs java.lang System.loadLibrary fails on Big Sur for libraries hidden from filesystem
46 JDK-8274848 core-libs java.lang.invoke LambdaMetaFactory::metafactory on REF_invokeSpecial impl method has incorrect behavior
47 JDK-8270290 core-libs java.net NTLM authentication fails if HEAD request is used
48 JDK-8274779 core-libs java.net HttpURLConnection: HttpClient and HttpsClient incorrectly check request method when set to POST
49 JDK-8267256 core-libs java.net Extend minimal retry for loopback connections on Windows to PlainSocketImpl
50 JDK-8268294 core-libs java.net Reusing HttpClient in a WebSocket.Listener hangs.
51 JDK-8269481 core-libs java.net SctpMultiChannel never releases own file descriptor
52 JDK-8251329 core-libs java.nio (zipfs) Files.walkFileTree walks infinitely if zip has dir named "." inside
53 JDK-8273935 core-libs java.nio (zipfs) Files.getFileAttributeView() throws UOE instead of returning null when view not supported
54 JDK-8269280 core-libs java.nio (bf) Replace StringBuffer in *Buffer.toString()
55 JDK-8190753 core-libs java.nio (zipfs): Accessing a large entry (> 2^31 bytes) leads to a negative initial size for ByteArrayOutputStream
56 JDK-8271308 core-libs java.nio (fc) FileChannel.transferTo() transfers no more than Integer.MAX_VALUE bytes in one call
57 JDK-8233020 core-libs java.nio (fs) UnixFileSystemProvider should use StaticProperty.userDir().
58 JDK-8272095 core-libs java.nio ProblemList java/nio/channels/FileChannel/Transfer2GPlus.java on linux-aarch64
59 JDK-8140241 core-libs java.nio (fc) Data transfer from FileChannel to itself causes hang in case of overlap
60 JDK-8274468 core-libs java.time TimeZoneTest.java fails with tzdata2021b
61 JDK-8274467 core-libs java.time TestZoneInfo310.java fails with tzdata2021b
62 JDK-8276536 core-libs java.time Update TimeZoneNames files to follow the changes made by JDK-8275766
63 JDK-8272473 core-libs java.time Parsing epoch seconds at a DST transition with a non-UTC parser is wrong
64 JDK-8274349 core-libs java.util.concurrent ForkJoinPool.commonPool() does not work with 1 CPU
65 JDK-8214761 core-libs java.util.stream Bug in parallel Kahan summation implementation
66 JDK-8273790 core-libs java.util:i18n Potential cyclic dependencies between Gregorian and CalendarSystem
67 JDK-8273924 core-libs java.util:i18n ArrayIndexOutOfBoundsException thrown in java.util.JapaneseImperialCalendar.add()
68 JDK-8273575 core-svc java.lang.instrument memory leak in appendBootClassPath(), paths must be deallocated
69 JDK-8268361 core-svc java.lang.management Fix the infinite loop in next_line
70 JDK-8272318 core-svc tools Improve performance of HeapDumpAllTest
71 JDK-8272970 hotspot Parallelize runtime/InvocationTests/
72 JDK-8273278 hotspot Support XSLT on GraalVM Native Image--deterministic bytecode generation in XSLT
73 JDK-8270886 hotspot compiler Crash in PhaseIdealLoop::verify_strip_mined_scheduling
74 JDK-8271600 hotspot compiler C2: CheckCastPP which should closely follow Allocate is sunk of a loop
75 JDK-8223923 hotspot compiler C2: Missing interference with mismatched unsafe accesses
76 JDK-8272570 hotspot compiler C2: crash in PhaseCFG::global_code_motion
77 JDK-8271341 hotspot compiler Opcode() != Op_If && Opcode() != Op_RangeCheck) || outcnt() == 2 assert failure with Test7179138_1.java
78 JDK-8271340 hotspot compiler Crash PhaseIdealLoop::clone_outer_loop
79 JDK-8271459 hotspot compiler C2: Missing NegativeArraySizeException when creating StringBuilder with negative capacity
80 JDK-8273165 hotspot compiler GraphKit::combine_exception_states fails with "matching stack sizes" assert
81 JDK-8272562 hotspot compiler C2: assert(false) failed: Bad graph detected in build_loop_late
82 JDK-8274145 hotspot compiler C2: condition incorrectly made redundant with dominating main loop exit condition
83 JDK-8274074 hotspot compiler SIGFPE with C2 compiled code with -XX:+StressGCM
84 JDK-8274401 hotspot compiler C2: GraphKit::load_array_element bypasses Access API
85 JDK-8274406 hotspot compiler RunThese30M.java failed "assert(!LCA_orig->dominates(pred_block) || early->dominates(pred_block)) failed: early is high enough"
86 JDK-8276066 hotspot compiler Reset LoopPercentProfileLimit for x86 due to suboptimal performance
87 JDK-8270901 hotspot compiler Typo PHASE_CPP in CompilerPhaseType
88 JDK-8273021 hotspot compiler C2: Improve Add and Xor ideal optimizations
89 JDK-8275104 hotspot compiler IR framework does not handle client VM builds correctly
90 JDK-8276105 hotspot compiler C2: Conv(D|F)2(I|L)Nodes::Ideal should handle rounding correctly
91 JDK-8276846 hotspot compiler JDK-8273416 is incomplete for UseSSE=1
92 JDK-8276112 hotspot compiler Inconsistent scalar replacement debug info at safepoints
93 JDK-8276025 hotspot compiler Hotspot's libsvml.so may conflict with user dependency
94 JDK-8270533 hotspot compiler AArch64: size_fits_all_mem_uses should return false if its output is a CAS
95 JDK-8273416 hotspot compiler C2: assert(false) failed: bad AD file after JDK-8252372 with UseSSE={0,1}
96 JDK-8273359 hotspot compiler CI: ciInstanceKlass::get_canonical_holder() doesn't respect instance size
97 JDK-8244675 hotspot compiler assert(IncrementalInline || (_late_inlines.length() == 0 && !has_mh_late_inlines()))
98 JDK-8272703 hotspot compiler StressSeed should be set via FLAG_SET_ERGO
99 JDK-8271954 hotspot compiler C2: assert(false) failed: Bad graph detected in build_loop_late
100 JDK-8272413 hotspot compiler Incorrect num of element count calculation for vector cast
101 JDK-8272574 hotspot compiler C2: assert(false) failed: Bad graph detected in build_loop_late
102 JDK-8276157 hotspot compiler C2: Compiler stack overflow during escape analysis on Linux x86_32
103 JDK-8268882 hotspot compiler C2: assert(n->outcnt() != 0 || C->top() == n || n->is_Proj()) failed: No dead instructions after post-alloc
104 JDK-8271567 hotspot compiler AArch64: AES Galois CounterMode (GCM) interleaved implementation using vector instructions
105 JDK-8271215 hotspot gc Fix data races in G1PeriodicGCTask
106 JDK-8274501 hotspot gc c2i entry barriers read int as long on AArch64
107 JDK-8271862 hotspot gc C2 intrinsic for Reference.refersTo() is often not used
108 JDK-8271121 hotspot gc ZGC: stack overflow (segv) when -Xlog:gc+start=debug
109 JDK-8272170 hotspot gc Missing memory barrier when checking active state for regions
110 JDK-8277212 hotspot gc GC accidentally cleans valid megamorphic vtable inline caches
111 JDK-8275426 hotspot gc PretouchTask num_chunks calculation can overflow
112 JDK-8274435 hotspot jfr EXCEPTION_ACCESS_VIOLATION in BFSClosure::closure_impl
113 JDK-8272850 hotspot runtime Drop zapping values in the Zap* option descriptions
114 JDK-8273606 hotspot runtime Zero: SPARC64 build fails with si_band type mismatch
115 JDK-8273373 hotspot runtime Zero: Cannot invoke JVM in primordial threads on Zero
116 JDK-8273505 hotspot runtime runtime/cds/appcds/loaderConstraints/DynamicLoaderConstraintsTest.java#default-cl crashed with SIGSEGV in MetaspaceShared::link_shared_classes
117 JDK-8273176 hotspot runtime handle latest VS2019 in abstract_vm_version
118 JDK-8273695 hotspot runtime Safepoint deadlock on VMOperation_lock
119 JDK-8273489 hotspot runtime Zero: Handle UseHeavyMonitors on all monitorenter paths
120 JDK-8273229 hotspot runtime Update OS detection code to recognize Windows Server 2022
121 JDK-8274840 hotspot runtime Update OS detection code to recognize Windows 11
122 JDK-8273342 hotspot runtime Null pointer dereference in classFileParser.cpp:2817
123 JDK-8272345 hotspot runtime macos doesn't check `os::set_boot_path()` result
124 JDK-8272114 hotspot runtime Unused _last_state in osThread_windows
125 JDK-8274293 hotspot runtime Build failure on macOS with Xcode 13.0 as vfork is deprecated
126 JDK-8274338 hotspot runtime com/sun/jdi/RedefineCrossEvent.java failed "assert(m != __null) failed: NULL mirror"
127 JDK-8238649 hotspot runtime Call new Win32 API SetThreadDescription in os::set_native_thread_name
128 JDK-8261579 hotspot runtime AArch64: Support for weaker memory ordering in Atomic
129 JDK-8268927 hotspot runtime Windows: link error: unresolved external symbol "int __cdecl convert_to_unicode(char const *,wchar_t * *)"
130 JDK-8273486 hotspot runtime Zero: Handle DiagnoseSyncOnValueBasedClasses VM option
131 JDK-8273483 hotspot runtime Zero: Clear pending JNI exception check in native method handler
132 JDK-8273440 hotspot runtime Zero: Disable runtime/Unsafe/InternalErrorTest.java
133 JDK-8273333 hotspot runtime Zero should warn about unimplemented -XX:+LogTouchedMethods
134 JDK-8268893 hotspot runtime jcmd to trim the glibc heap
135 JDK-8273902 hotspot runtime Memory leak in OopStorage due to bug in OopHandle::release()
136 JDK-8269687 hotspot runtime pauth_aarch64.hpp include name is incorrect
137 JDK-8275604 hotspot runtime Zero: Reformat opclabels_data
138 JDK-8277029 hotspot svc JMM GetDiagnosticXXXInfo APIs should verify output array sizes
139 JDK-8270320 hotspot test JDK-8270110 committed invalid copyright headers
140 JDK-8270946 security-libs java.security X509CertImpl.getFingerprint should not return the empty String
141 JDK-8273826 security-libs java.security Correct Manifest file name and NPE checks
142 JDK-8274215 security-libs java.security Remove globalsignr2ca root from 17.0.2
143 JDK-8274736 security-libs java.security Concurrent read/close of SSLSockets causes SSLSessions to be invalidated unnecessarily
144 JDK-8277224 security-libs java.security sun.security.pkcs.PKCS9Attributes.toString() throws NPE
145 JDK-8270317 security-libs javax.net.ssl Large Allocation in CipherSuite
146 JDK-8275811 security-libs javax.net.ssl Incorrect instance to dispose
147 JDK-8273026 security-libs javax.security Slow LoginContext.login() on multi threading application
148 JDK-8274205 security-libs org.ietf.jgss:krb5 Handle KDC_ERR_SVC_UNAVAILABLE error code from KDC
149 JDK-8273894 security-libs org.ietf.jgss:krb5 ConcurrentModificationException raised every time ReferralsCache drops referral
150 JDK-8273234 tools javac extended 'for' with expression of type tvar causes the compiler to crash
151 JDK-8262095 tools javac NPE in Flow$FlowAnalyzer.visitApply: Cannot invoke getThrownTypes because tree.meth.type is null
152 JDK-8268885 tools javac duplicate checkcast when destination type is not first type of intersection type
153 JDK-8269113 tools javac Javac throws when compiling switch (null)
154 JDK-8275302 tools javac unexpected compiler error: cast, intersection types and sealed
155 JDK-8274347 tools javac Passing a *nested* switch expression as a parameter causes an NPE during compile
156 JDK-8268894 tools javac forged ASTs can provoke an AIOOBE at com.sun.tools.javac.jvm.ClassWriter::writePosition
157 JDK-8273408 tools javac java.lang.AssertionError: typeSig ERROR on generated class property of record
158 JDK-8271254 tools javac javac generates unreachable code when using empty semicolon statement
159 JDK-8274942 tools javac AssertionError at jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:155)
160 JDK-8272639 tools jpackage jpackaged applications using microphone on mac
161 JDK-8274087 tools jpackage Windows DLL path not set correctly.
162 JDK-8273593 tools jpackage [REDO] Warn user when using mac-sign option with unsigned app-image.
163 JDK-8272328 tools jpackage java.library.path is not set properly by Windows jpackage app launcher
164 JDK-8268457 xml XML Transformer outputs Unicode supplementary character incorrectly to HTML

Java™ SE Development Kit 17.0.1 (JDK 17.0.1)

October 19, 2021

The full version string for this update release is 17.0.1+12 (where "+" means "build"). The version number is 17.0.1.

IANA TZ Data 2021a

For more information, refer to Timezone Data Versions in the JRE Software.

Security Baselines

The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 17.0.1 are specified in the following table:

JRE Family Version JRE Security Baseline (Full Version String)
17 17.0.1+12
11 11.0.13+10
8 8u311-b11
7 7u321-b08

 

Keeping the JDK up to Date

Oracle recommends that the JDK is updated with each Critical Patch Update. In order to determine if a release is the latest, the Security Baseline page can be used to determine which is the latest version for each release family.

Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Bulletins. It is not recommended that this JDK (version 17.0.1) be used after the next critical patch update scheduled for January 18, 2022.

Removed Features and Options

security-libs/java.security
 Removed IdenTrust Root Certificate

The following root certificate from IdenTrust has been removed from the cacerts keystore:

+ alias name "identrustdstx3 [jdk]"

  Distinguished Name: CN=DST Root CA X3, O=Digital Signature Trust Co.

Other Notes

core-libs/java.lang
 Release Doesn't Correctly Recognize Windows 11

This release doesn't correctly identify Windows 11. The property os.name is set to Windows 10 on Windows 11. In HotSpot error logs, the OS is identified as Windows 10; however, the HotSpot error log does show the Build number. Windows 11 has Build 22000.194 or above.

core-libs/javax.naming
 System Property to Control Reconstruction of Reference Address Objects by JDK's Built-in JNDI LDAP Implementation

The scope of the com.sun.jndi.ldap.object.trustSerialData system property has been extended to control the deserialization of java objects from the javaReferenceAddress LDAP attribute. This system property now controls the deserialization of java objects from the javaSerializedData and javaReferenceAddress LDAP attributes.

To prevent deserialization of java objects from these attributes, the system property can be set to false. By default, the deserialization of java objects from javaSerializedData and javaReferenceAddress attributes is allowed.

JDK-8267712 (not public)

hotspot/runtime
 Release Doesn't Correctly Recognize Windows Server 2022

This release doesn't correctly identify Windows Server 2022. The property os.name is set to Windows Server 2019 on Windows Server 2022. In HotSpot error logs the OS is identified as Windows Server 2019; however, the HotSpot error log does show the Build number. Windows Server 2022 has Build 20348, or above.

 

Bug Fixes

This release also contains fixes for security vulnerabilities described in the Oracle Critical Patch Update.

Issues fixed in 17.0.1:

# JBS Component Subcomponent Sumary
1 JDK-8262731 client-libs 2d [macOS] Exception from "Printable.print" is swallowed during "PrinterJob.print"
2 JDK-8273358 client-libs 2d macOS Monterey does not have the font Times needed by Serif
3 JDK-8272602 client-libs java.awt [macos] not all KEY_PRESSED events sent when control modifier is used
4 JDK-8272806 client-libs java.awt [macOS] "Apple AWT Internal Exception" when input method is changed
5 JDK-8267666 core-svc tools Add option to jcmd GC.heap_dump to use existing file
6 JDK-8271925 hotspot compiler ZGC: Arraycopy stub passes invalid oop to load barrier
7 JDK-8271589 hotspot compiler fatal error with variable shift count integer rotate operation.
8 JDK-8271203 hotspot compiler C2: assert(iff->Opcode() == Op_If || iff->Opcode() == Op_CountedLoopEnd || iff->Opcode() == Op_RangeCheck) failed: Check this code when new subtype is added
9 JDK-8270098 hotspot compiler ZGC: ZBarrierSetC2::clone_at_expansion fails with "Guard against surprises" assert
10 JDK-8272131 hotspot compiler PhaseMacroExpand::generate_slow_arraycopy crash when clone null CallProjections.fallthrough_ioproj
11 JDK-8271276 hotspot compiler C2: Wrong JVM state used for receiver null check
12 JDK-8268019 hotspot compiler C2: assert(no_dead_loop) failed: dead loop detected
13 JDK-8268261 hotspot compiler C2: assert(n != __null) failed: Bad immediate dominator info.
14 JDK-8269574 hotspot compiler C2: Avoid redundant uncommon traps in GraphKit::builtin_throw() for JVMTI exception events
15 JDK-8272124 hotspot runtime Cgroup v1 initialization causes NullPointerException when cgroup path contains colon
16 JDK-8269934 hotspot runtime RunThese24H.java failed with EXCEPTION_ACCESS_VIOLATION in java_lang_Thread::get_thread_status
17 JDK-8225082 security-libs java.security Remove IdenTrust certificate that is expiring in September 2021
18 JDK-8268427 security-libs java.security Improve AlgorithmConstraints:checkAlgorithm performance
19 JDK-8225083 security-libs java.security Remove Google certificate that is expiring in December 2021
20 JDK-8273150 security-libs java.security Revert "8225083: Remove Google certificate that is expiring in December 2021"
21 JDK-8270344 security-libs javax.net.ssl Session resumption errors

JDK 17 Release Notes

The following sections are included in these Release Notes:


Introduction

These notes describe important changes, enhancements, removed APIs and features, deprecated APIs and features, and other information about JDK 17 and Java SE 17. In some cases, the descriptions provide links to additional detailed information about an issue or a change. This page does not duplicate the descriptions provided by the Java SE 17 ( JSR 392) Platform Specification, which provides informative background for all specification changes and might also include the identification of removed or deprecated APIs and features not described here. The Java SE 17 ( JSR 392) specification provides links to:

You should be aware of the content in the Java SE 17 ( JSR 392) specification as well as the items described in this page.

The descriptions on this Release Notes page also identify potential compatibility issues that you might encounter when migrating to JDK 17. The Kinds of Compatibility page on the OpenJDK wiki identifies the following three types of potential compatibility issues for Java programs that might be used in these release notes:

  • Source: Source compatibility preserves the ability to compile existing source code without error.

  • Binary: Binary compatibility is defined in The Java Language Specification as preserving the ability to link existing class files without error.

  • Behavioral: Behavioral compatibility includes the semantics of the code that is executed at runtime.

See CSRs Approved for JDK 17 for the list of CSRs closed in JDK 17 and the Compatibility & Specification Review (CSR) page on the OpenJDK wiki for general information about compatibility.

The full version string for this release is build 17+35 (where "+" means "build"). The version number is 17.

 

IANA Data 2021a

JDK 17 contains IANA time zone data version 2021a. For more information, refer to Timezone Data Versions in the JRE Software.

TOP


New Features

This section describes some of the enhancements in Java SE 17 and JDK 17. In some cases, the descriptions provide links to additional detailed information about an issue or a change. The APIs described here are provided with the Oracle JDK. It includes a complete implementation of the Java SE 17 Platform and additional Java APIs to support developing, debugging, and monitoring Java applications. Another source of information about important enhancements and new features in Java SE 17 and JDK 17 is the Java SE 17 ( JSR 392) Platform Specification, which documents the changes to the specification made between Java SE 16 and Java SE 17. This document includes descriptions of those new features and enhancements that are also changes to the specification. The descriptions also identify potential compatibility issues that you might encounter when migrating to JDK 17.

 

specification
 JEP 409: Sealed Classes

Sealed Classes have been added to the Java Language. Sealed classes and interfaces restrict which other classes or interfaces may extend or implement them.

Sealed Classes were proposed by JEP 360 and delivered in JDK 15 as a preview feature. They were proposed again, with refinements, by JEP 397 and delivered in JDK 16 as a preview feature. Now in JDK 17, Sealed Classes are being finalized with no changes from JDK 16.

For further details, see JEP 409.

See JDK-8260514

specification
 JEP 406: Pattern Matching for switch (Preview)

Enhance the Java programming language with pattern matching for switch expressions and statements, along with extensions to the language of patterns. Extending pattern matching to switch allows an expression to be tested against a number of patterns, each with a specific action, so that complex data-oriented queries can be expressed concisely and safely.

For further details, see JEP 406.

See JDK-8213076

client-libs/2d
 JEP 382: New macOS Rendering Pipeline

The Java 2D API used by the Swing APIs for rendering, can now use the new Apple Metal accelerated rendering API for macOS.

This is currently disabled by default, so rendering still uses OpenGL APIs, which are deprecated by Apple but still available and supported.

To enable Metal, an application should specify its use by setting the system property:

-Dsun.java2d.metal=true

Use of Metal or OpenGL is transparent to applications since this is a difference of internal implementation and has no effect on Java APIs. The metal pipeline requires macOS 10.14.x or later. Attempts to set it on earlier releases will be ignored.

For further details, see JEP 382.

See JDK-8238361

client-libs/javax.swing
 New API for Accessing Large Icons

A new method, javax.swing.filechooser.FileSystemView.getSystemIcon(File, int, int), is available in JDK 17 that enables access to higher quality icons when possible. It is fully implemented for the Windows platform; however, results on other platforms might vary and will be enhanced later. For example, by using the following code:

  FileSystemView fsv = FileSystemView.getFileSystemView();

  Icon icon = fsv.getSystemIcon(new File("application.exe"), 64, 64);
  JLabel label = new JLabel(icon);

The user can obtain a higher quality icon for the "application.exe" file. This icon is suitable for creating a label that can be better scaled in a HighDPI environment.

See JDK-8182043

core-libs/java.net
 DatagramSocket Can Be Used Directly to Join Multicast Groups

java.net.DatagramSocket has been updated in this release to add support for joining multicast groups. It now defines joinGroup and leaveGroup methods to join and leave multicast groups. The class level API documentation of java.net.DatagramSocket has been updated to explain how a plain DatagramSocket can be configured and used to join and leave multicast groups.

This change means that the DatagramSocket API can be used for multicast applications without needing to use the legacy java.net.MulticastSocket API. The MulticastSocket API works as before, although most of its methods are deprecated.

More information on the rationale of this change can be seen in the CSR JDK-8260667.

See JDK-8237352

core-libs/java.nio
 Add support for UserDefinedFileAttributeView on macOS

The file system provider implementation on macOS has been updated in this release to support extended attributes. The java.nio.file.attribute.UserDefinedFileAttributeView API can now be used to obtain a view of a file's extended attributes. This (optional) view was not supported in previous JDK releases.

See JDK-8030048

core-libs/java.util
 JEP 356: Enhanced Pseudo-Random Number Generators

Provide new interface types and implementations for pseudorandom number generators (PRNGs), including jumpable PRNGs and an additional class of splittable PRNG algorithms (LXM).

For further details, see JEP 356.

See JDK-8193209

hotspot/compiler
 Modernization of Ideal Graph Visualizer

Ideal Graph Visualizer (IGV), a tool to explore visually and interactively the intermediate representation used in the HotSpot VM C2 just-in-time (JIT) compiler, has been modernized. Enhancements include:

  • Support for running IGV on up to JDK 15 (the latest version supported by IGV's underlying NetBeans Platform)
  • Faster, Maven-based IGV build system
  • Stabilization of block formation, group removal, and node tracking
  • More intuitive coloring and node categorization in default filters
  • Ranked quick node search with more natural default behavior

The modernized IGV is partially compatible with graphs generated from earlier JDK releases. It supports basic functionality such as graph loading and visualization, but auxiliary functionality such as node clustering and coloring might be affected.

Details about building and running IGV are available in the src/utils/IdealGraphVisualizer/README.md file in the tool's source directory.

See JDK-8254145

tools/javadoc(tool)
 Source Details in Error Messages

When JavaDoc reports an issue in an input source file, it displays the source line for the issue, and a line containing a caret (^) pointing to the position on the line, in a manner similar to compiler (javac) diagnostic messages.

In addition, logging and other "info" messages are now written to the standard error stream, leaving the standard output stream to be used for output that is specifically requested by command-line options, such as command-line help.

See JDK-8267126

tools/javadoc(tool)
 New Page for "New API" and Improved "Deprecated" Page

JavaDoc can now generate a page summarizing the recent changes in an API. The list of recent releases to be included is specified with the --since command-line option. These values are used to find the declarations with matching @since tags to be included on the new page. The --since-label command-line option provides text to use in the heading of the "New API" page.

On the page that summarizes deprecated items, you can view items grouped by the release in which they were deprecated.

See JDK-8263468

core-libs
 JEP 412: Foreign Function & Memory API (Incubator)

Introduce an API by which Java programs can interoperate with code and data outside of the Java runtime. By efficiently invoking foreign functions (i.e., code outside the JVM), and by safely accessing foreign memory (i.e., memory not managed by the JVM), the API enables Java programs to call native libraries and process native data without the brittleness and danger of JNI.

For further details, see JEP 412.

See JDK-8265033

core-libs
 Console Charset API

java.io.Console has been updated to define a new method that returns the Charset for the console. The returned Charset may be different from the one returned from Charset.defaultCharset() method. For example, it returns IBM437 while Charset.defaultCharset() returns windows-1252 on Windows (en-US). Refer to the CSR for more detail.

See JDK-8264208

core-libs/java.io:serialization
 JDK Flight Recorder Event for Deserialization

It is now possible to monitor deserialization of objects using JDK Flight Recorder (JFR). When JFR is enabled and the JFR configuration includes deserialization events, JFR will emit an event whenever the running program attempts to deserialize an object. The deserialization event is named jdk.Deserialization, and it is disabled by default. The deserialization event contains information that is used by the serialization filter mechanism; see the ObjectInputFilter specification. Additionally, if a filter is enabled, the JFR event indicates whether the filter accepted or rejected deserialization of the object. For further information about how to use the JFR deserialization event, see the article Monitoring Deserialization to Improve Application Security. For reference information about using and configuring JFR, see the JFR Runtime Guide and JFR Command Reference sections of the JDK Mission Control documentation.

See JDK-8261160

core-libs/java.io:serialization
 JEP 415: Implement Context-Specific Deserialization Filters

JEP 415: Context-Specific Deserialization Filters allows applications to configure context-specific and dynamically-selected deserialization filters via a JVM-wide filter factory that is invoked to select a filter for each individual deserialization operation.

The Java Core Libraries Developers Guide for Serialization Filtering describes use cases and provides examples.

See JDK-8264859

core-libs/java.lang
 System Property for Native Character Encoding Name

A new system property native.encoding has been introduced. This system property provides the underlying host environment's character encoding name. For example, typically it has UTF-8 in Linux and macOS platforms, and Cp1252 in Windows (en-US). Refer to the CSR for more detail.

See JDK-8265989

core-libs/java.time
 Add java.time.InstantSource

A new interface java.time.InstantSource has been introduced. This interface is an abstraction from java.time.Clock that only focuses on the current instant and does not refer to the time zone.

See JDK-8266846

core-libs/java.util
 Hex Formatting and Parsing Utility

java.util.HexFormat provides conversions to and from hexadecimal for primitive types and byte arrays. The options for delimiter, prefix, suffix, and uppercase or lowercase are provided by factory methods returning HexFormat instances.

See JDK-8251989

hotspot/compiler
 Experimental Compiler Blackholes Support

The experimental support for Compiler Blackholes is added. These are useful for low-level benchmarking, to avoid dead-code elimination on the critical paths, without affecting the benchmark performance. Current support is implemented as CompileCommand, accessible as -XX:CompileCommand=blackhole,<method>, with the plan to eventually graduate it to a public API.

JMH is already able to auto-detect and use this facility when instructed/available. Please consult JMH documentation for the next steps.

See JDK-8259316

hotspot/compiler
 New Class Hierarchy Analysis Implementation in the HotSpot JVM

A new Class Hierarchy Analysis implementation is introduced in the HotSpot JVM. It features enhanced handling of abstract and default methods which improves inlining decisions made by the JIT-compilers. The new implementation supersedes the original one and is turned on by default.

To help diagnose possible issues related to the new implementation, the original implementation can be turned on by specifying the -XX:+UnlockDiagnosticVMOptions -XX:-UseVtableBasedCHA command-line flags.

The original implementation may be removed in a future release.

See JDK-8266074

hotspot/compiler
 JEP 391: macOS/AArch64 Port

macOS 11.0 now supports the AArch64 architecture. This JEP implements support for the macos-aarch64 platform in the JDK. One of the features added is support for the W^X (write xor execute) memory. It is enabled only for macos-aarch64 and can be extended to other platforms at some point. The JDK can be either cross-compiled on an Intel machine or compiled on an Apple M1-based machine.

For further details, see JEP 391.

See JDK-8251280

hotspot/runtime
 Unified Logging Supports Asynchronous Log Flushing

To avoid undesirable delays in a thread using unified logging, the user can now request that the unified logging system operate in asynchronous mode. This is done by passing the command-line option -Xlog:async. In asynchronous logging mode, log sites enqueue all logging messages to a buffer. A standalone thread is responsible for flushing them to the corresponding outputs. The intermediate buffer is bounded. On buffer exhaustion, the enqueuing message is discarded. The user can control the size of the intermediate buffer by using the command-line option -XX:AsyncLogBufferSize=<bytes>.

See JDK-8229517

infrastructure/build
 macOS on ARM Early Access Available

A new macOS is now available for ARM systems. The ARM port should behave similarly to the Intel port. There are no known feature differences. When reporting issues on macOS, please specify if using ARM or x64.

See JDK-8266858

security-libs/java.security
 Provide Support for Specifying a Signer in Keytool -genkeypair Command

The -signer and -signerkeypass options have been added to the -genkeypair command of the keytool utility. The -signer option specifies the keystore alias of a PrivateKeyEntry for the signer and the -signerkeypass option specifies the password used to protect the signer’s private key. These options allow keytool -genkeypair to sign the certificate by using the signer’s private key. This is especially useful for generating a certificate with a key agreement algorithm as its public key algorithm.

See JDK-8260693

security-libs/javax.crypto
 SunJCE Provider Supports KW and KWP Modes With AES Cipher

The SunJCE provider has been enhanced to support the AES Key Wrap Algorithm (RFC 3394) and the AES Key Wrap with Padding Algorithm (RFC 5649). In earlier releases, the SunJCE provider supported RFC 3394 under the "AESWrap" cipher algorithm that could only be used to wrap and unwrap keys. With this enhancement, two block cipher modes, KW and KWP, have been added that support data encryption/decryption and key wrap/unwrap by using AES. Please check the "SunJCE provider" section of the "JDK Providers Documentation" guide for more details.

See JDK-8248268

security-libs/javax.crypto:pkcs11
 New SunPKCS11 configuration properties

SunPKCS11 provider adds new provider configuration attributes to better control native resources usage. The SunPKCS11 provider consumes native resources in order to work with native PKCS11 libraries. To manage and better control the native resources, additional configuration attributes are added to control the frequency of clearing native references as well as whether to destroy underlying PKCS11 Token after logout.

The 3 new attributes for SunPKCS11 provider configuration file are:

  1. destroyTokenAfterLogout (boolean, defaults to false) If set to true, when java.security.AuthProvider.logout() is called upon the SunPKCS11 provider instance, the underlying Token object will be destroyed and resources will be freed. This essentially renders the SunPKCS11 provider instance unusable after logout() calls. Note that a PKCS11 provider with this attribute set to true should not be added to the system provider list since the provider object is not usable after a logout() method call.
  2. cleaner.shortInterval (integer, defaults to 2000, in milliseconds) This defines the frequency for clearing native references during busy period, i.e. how often should the cleaner thread processes the no-longer-needed native references in the queue to free up native memory. Note that the cleaner thread will switch to the 'longInterval' frequency after 200 failed tries, i.e. when no references are found in the queue.
  3. cleaner.longInterval (integer, defaults to 60000, in milliseconds) This defines the frequency for checking native reference during non-busy period, i.e. how often should the cleaner thread check the queue for native references. Note that the cleaner thread will switch back to the 'shortInterval' value if native PKCS11 references for cleaning are detected.
See JDK-8240256

security-libs/javax.crypto:pkcs11
 SunPKCS11 Provider Supports ChaCha20-Poly1305 Cipher and ChaCha20 KeyGenerator if Supported by PKCS11 Library

SunPKCS11 provider is enhanced to support the following crypto services and algorithms when the underlying PKCS11 library supports the corresponding PKCS#11 mechanisms:

  • ChaCha20 KeyGenerator <=> CKM_CHACHA20_KEY_GEN mechanism
  • CHACHA20-POLY1305 Cipher <=> CKM_CHACHA20_POLY1305 mechanism
  • CHACHA20-POLY1305 AlgorithmParameters <=> CKM_CHACHA20_POLY1305 mechanism
  • CHACHA20 SecretKeyFactory <=> CKM_CHACHA20_POLY1305 mechanism
See JDK-8255410

security-libs/javax.net.ssl
 Configurable Extensions With System Properties

Two new system properties have been added. The system property, jdk.tls.client.disableExtensions, is used to disable TLS extensions used in the client. The system property, jdk.tls.server.disableExtensions, is used to disable TLS extensions used in the server. If an extension is disabled, it will be neither produced nor processed in the handshake messages.

The property string is a list of comma separated standard TLS extension names, as registered in the IANA documentation (for example, server_name, status_request, and signature_algorithms_cert). Note that the extension names are case sensitive. Unknown, unsupported, misspelled and duplicated TLS extension name tokens will be ignored.

Please note that the impact of blocking TLS extensions is complicated. For example, a TLS connection may not be able to be established if a mandatory extension is disabled. Please do not disable mandatory extensions, and do not use this feature unless you clearly understand the impact.

See JDK-8217633

security-libs/org.ietf.jgss:krb5
 Use permitted_enctypes if default_tkt_enctypes or default_tgs_enctypes is not present

Use permitted_enctypes as the default value of default_tkt_enctypes or default_tgs_enctypes if any of the them are not defined in krb5.conf.

See JDK-8262389

tools/javadoc(tool)
 "Related Packages" on a Package Summary Page

The summary page for a package now includes a section listing any "related packages". The set of related packages is determined heuristically on common naming conventions, and may include the following:

  • The "parent" package (that is, the package for which a package is a subpackage)
  • Sibling packages (that is, other packages with the same parent package)
  • Any subpackages

The related packages need not all be in the same module.

See JDK-8260388

TOP


Removed Features and Options

This section describes the APIs, features, and options that were removed in Java SE 17 and JDK 17. The APIs described here are those that are provided with the Oracle JDK. It includes a complete implementation of the Java SE 17 Platform and additional Java APIs to support developing, debugging, and monitoring Java applications. Another source of information about important enhancements and new features in Java SE 17 and JDK 17 is the Java SE 17 ( JSR 392) Platform Specification, which documents changes to the specification made between Java SE 16 and Java SE 17. This document includes the identification of removed APIs and features not described here. The descriptions below might also identify potential compatibility issues that you could encounter when migrating to JDK 17.See CSRs Approved for JDK 17 for the list of CSRs closed in JDK 17.

core-libs
 JEP 403: Strongly Encapsulate JDK Internals

Strongly encapsulate all internal elements of the JDK, except for critical internal APIs such as sun.misc.Unsafe.

With this change, the java launcher option --illegal-access is obsolete. If used on the command line it causes a warning message to be issued, and otherwise has no effect. Existing code that must use internal classes, methods, or fields of the JDK can still be made to work by using the --add-opens launcher option, or the Add-Opens JAR-file manifest attribute, to open specific packages.

For further details, please see JEP 403.

See JDK-8266851

security-libs/java.security
 Removed Telia Company's Sonera Class2 CA Certificate

The following root certificate has been removed from the cacerts truststore:

+ Telia Company

  + soneraclass2ca
    DN: CN=Sonera Class2 CA, O=Sonera, C=FI
See JDK-8225081

core-libs
 Removal of sun.misc.Unsafe::defineAnonymousClass

sun.misc.Unsafe::defineAnonymousClass API has been removed in JDK 17. The API replacement is java.lang.invoke.MethodHandles.Lookup::defineHiddenClass and java.lang.invoke.MethodHandles.Lookup::defineHiddenClassWithClassData.

See JDK-8243287

core-libs/java.rmi
 JEP 407: Remove RMI Activation

The Remote Method Invocation (RMI) Activation mechanism has been removed. RMI Activation was an obsolete part of RMI that has been optional since Java SE 8. RMI Activation was deprecated for removal by JEP 385 in Java SE 15, and it was removed from this release by JEP 407. The rmid tool has also been removed. See JEP 385 for background, rationale, risks, and alternatives. The rest of RMI remains unchanged.

See JDK-8263550

hotspot/compiler
 JEP 410: Remove the Experimental AOT and JIT Compiler

AOT Compiler related code in HotSpot VM has been removed. Using HotSpot VM options defined by JEP295 produce "Unrecognized VM option" error on VM initialization.

For further details, see JEP 410.

See JDK-8263327

TOP


Deprecated Features and Options

Additional sources of information about the APIs, features, and options deprecated in Java SE 17 and JDK 17 include:

  • The Deprecated API page identifies all deprecated APIs including those deprecated in Java SE 17.

  • The Java SE 17 ( JSR 392) specification documents changes to the specification made between Java SE 16 and Java SE 17 that include the identification of deprecated APIs and features not described here.

  • JEP 277: Enhanced Deprecation provides a detailed description of the deprecation policy. You should be aware of the updated policy described in this document.

You should be aware of the contents in those documents as well as the items described in this release notes page.

The descriptions of deprecated APIs might include references to the deprecation warnings of forRemoval=true and forRemoval=false. The forRemoval=true text indicates that a deprecated API might be removed from the next major release. The forRemoval=false text indicates that a deprecated API is not expected to be removed from the next major release but might be removed in some later release.

The descriptions below also identify potential compatibility issues that you might encounter when migrating to JDK 17. See CSRs Approved for JDK 17 for the list of CSRs closed in JDK 17.

client-libs/java.awt
 JEP 398: Deprecate the Applet API for Removal

JEP 398: Deprecate the Applet API for Removal. It is essentially irrelevant since all web-browser vendors have either removed support for Java browser plug-ins or announced plans to do so.

The Applet API was previously deprecated, though not for removal, by JEP 289 in Java 9.

See JDK-8256145

security-libs/java.security
 JEP 411: Deprecate the Security Manager for Removal

The Security Manager and APIs related to it have been deprecated and will be removed in a future release. To ensure that developers and users are aware that the Security Manager is deprecated for removal, the Java runtime issues a warning at startup if the Security Manager is enabled on the command line via java -Djava.security.manager. The Java runtime also issues a warning at run time if the Security Manager is enabled dynamically via the System::setSecurityManager API. These warnings cannot be disabled.

See JEP 411 for more information and a list of APIs that have been deprecated for removal.

See JDK-8264713

security-libs/org.ietf.jgss:krb5
 Deprecate 3DES and RC4 in Kerberos

The des3-hmac-sha1 and rc4-hmac Kerberos encryption types (etypes) are now deprecated and disabled by default. Users can set allow_weak_crypto = true in the krb5.conf configuration file to re-enable them (along with other weak etypes including des-cbc-crc and des-cbc-md5) at their own risk. To disable a subset of the weak etypes, users can list preferred etypes explicitly in any of the default_tkt_enctypes, default_tgs_enctypes, or permitted_enctypes settings.

See JDK-8139348

core-libs/java.net
 Deprecate the Socket Implementation Factory Mechanism

The following static methods used to set the system-wide socket implementation factories have been deprecated:

  • static void ServerSocket.setSocketFactory​(SocketImplFactory fac)
  • static void Socket.setSocketImplFactory​(SocketImplFactory fac)
  • static void DatagramSocket.setDatagramSocketImplFactory​(DatagramSocketImplFactory fac)

These API points were used to statically configure a system-wide factory for the corresponding socket types in the java.net package. These methods have mostly been obsolete since Java 1.4.

See JDK-8235139

hotspot/jvmti
 Deprecate JVM TI Heap functions 1.0

The following JVM TI functions have been deprecated in this release:

  • IterateOverObjectsReachableFromObject
  • IterateOverReachableObjects
  • IterateOverHeap
  • IterateOverInstancesOfClass

These functions were superseded in JVM TI version 1.2 (Java SE 6) by more powerful and flexible versions. These functions will be changed to return an error in a future release to indicate that they are no longer implemented/supported. The VM flags -Xlog:jvmti=trace and -XX:TraceJVMTI=<function_name> can be used to identify any residual usages of these functions. For example, -Xlog:jvmti=trace -XX:TraceJVMTI=IterateOverHeap is one way to get trace output when IterateOverHeap is used.

See JDK-8268241

TOP


Other Notes

The following notes describe additional changes and information about this release. In some cases, the following descriptions provide links to additional detailed information about an issue or a change.

core-libs/javax.naming
 New System and Security Properties to Control Reconstruction of Remote Objects by JDK's Built-in JNDI RMI and LDAP Implementations

jdk.jndi.object.factoriesFilter: This system and security property allows a serial filter to be specified that controls the set of object factory classes permitted to instantiate objects from object references returned by naming/directory systems. The factory class named by the reference instance is matched against this filter during remote reference reconstruction. The filter property supports pattern-based filter syntax with the format specified by JEP 290. This property applies both to the JNDI/RMI and the JNDI/LDAP built-in provider implementations. The default value allows any object factory class specified in the reference to recreate the referenced object.

com.sun.jndi.ldap.object.trustSerialData: This system property allows control of the deserialization of java objects from the javaSerializedData LDAP attribute. To prevent deserialization of java objects from the attribute, the system property can be set to false value. By default, deserialization of java objects from the javaSerializedData attribute is allowed.

JDK-8244473 (not public)

core-libs/java.util:collections
 TreeMap.computeIfAbsent Mishandles Existing Entries Whose Values Are null

Enhancement JDK-8176894 inadvertently introduced erroneous behavior in the TreeMap.computeIfAbsent method. The other TreeMap methods that were modified by this enhancement are unaffected. The erroneous behavior is that, if the map contains an existing mapping whose value is null, the computeIfAbsent method immediately returns null. To conform with the specification, computeIfAbsent should instead call the mapping function and update the map with the function's result.

See JDK-8259622

install
 Change to Package Names in Linux RPM/DEB Installers

On the Linux platform, the names of JDK packages provided by Java RPM and DEB installers have been changed. Names of JDK packages follow the jdk-<feature_release_version> pattern instead of the jdk-<update_release_version> pattern that was previously used. For example, the new names of JDK 11, 16, and 17 packages are jdk-11, jdk-16, and jdk-17 respectively.

The change to package names disables side-by-side installation of multiple JDKs of the same release family. Only one JDK per release family can be installed on a system with RPM and DEB installers.

If a user wants to have multiple update releases from the same family, the user must download the tar.gz bundles.

JDK-8266653 (not public)

install/install
 Updated List of Capabilities Provided by JDK RPMs

The following capabilities have been removed from the list of what OracleJDK/OracleJRE RPMs provide: xml-commons-api, jaxp_parser_impl, and java-fonts. This clean-up of the list resolves existing and potential conflicts with modular RPMs.

There are other RPMs providing these capabilities, so there should be no impact on packages that depend on them. Package managers can use other rpms to satisfy the dependencies provided by the OracleJDK/OracleJRE RPMs before this change.

JDK-8263575 (not public)

install/install
 ADDLOCAL=ToolsFeature,SourceFeature Argument No Longer Needed For Windows JDK Installer

The ADDLOCAL=ToolsFeature,SourceFeature argument is no longer needed for the JDK installer silent mode. All required files are now installed by default.

JDK-8262043 (not public)

security-libs/java.security
 Added 2 HARICA Root CA Certificates

The following root certificates have been added to the cacerts truststore:

+ HARICA

  + haricarootca2015
    DN: CN=Hellenic Academic and Research Institutions RootCA 2015, O=Hellenic Academic and Research Institutions Cert. Authority, L=Athens, C=GR

  + haricaeccrootca2015
    DN: CN=Hellenic Academic and Research Institutions ECC RootCA 2015, O=Hellenic Academic and Research Institutions Cert. Authority, L=Athens, C=GR
See JDK-8256421

security-libs/java.security
 Disable SHA-1 JARs

JARs signed with SHA-1 algorithms are now restricted by default and treated as if they were unsigned. This applies to the algorithms used to digest, sign, and optionally timestamp the JAR. It also applies to the signature and digest algorithms of the certificates in the certificate chain of the code signer and the Timestamp Authority, and any CRLs or OCSP responses that are used to verify if those certificates have been revoked.

In order to reduce the compatibility risk for applications that have been previously timestamped or use private CAs, there are two exceptions to this policy:

  • Any JAR signed with SHA-1 algorithms and timestamped prior to January 01, 2019 will not be restricted.
  • Any JAR signed with a SHA-1 certificate that does not chain back to a Root CA included by default in the JDK cacerts keystore will not be restricted.

These exceptions may be removed in a future JDK release.

Users can, at their own risk, remove these restrictions by modifying the java.security configuration file (or overriding it using the java.security.properties system property) and removing "SHA1 jdkCA & usage SignedJAR & denyAfter 2019-01-01" from the jdk.certpath.disabledAlgorithms security property and "SHA1 jdkCA & denyAfter 2019-01-01" from the jdk.jar.disabledAlgorithms security property.

See JDK-8196415

security-libs/javax.xml.crypto
 Enable XML Signature Secure Validation Mode by Default

The XML Signature secure validation mode has been enabled by default (previously it was not enabled by default unless running with a security manager). When enabled, validation of XML signatures are subject to stricter checking of algorithms and other constraints as specified by the jdk.xml.dsig.secureValidationPolicy security property.

If necessary, and at their own risk, applications can disable the mode by setting the org.jcp.xml.dsig.secureValidation property to Boolean.FALSE with the DOMValidateContext.setProperty() API.

See JDK-8259801

security-libs/javax.xml.crypto
 Disable SHA-1 XML Signatures

XML signatures that use SHA-1 based digest or signature algorithms have been disabled by default. SHA-1 is no longer a recommended algorithm for digital signatures. If necessary, and at their own risk, applications can workaround this policy by modifying the jdk.xml.dsig.secureValidationPolicy security property and re-enabling the SHA-1 algorithms.

See JDK-8259709

core-libs
 RegEx Pattern Matching Loses Character Class After Intersection (&&) Operator

This release fixes a buggy behavior in regular expression pattern intersection. In prior releases, if a nested character class were included in some intersections after the intersection (&&) operator, it would be ignored and not included in the generated matcher from the pattern. This change brings the behavior in line with the intersection regex patterns seen in Ruby.

See JDK-8037397

core-libs/java.lang:reflect
 Remove Vestiges of Intermediate JSR 175 Annotation Format

When annotations were added to the platform in Java SE 5.0, early builds used a different representation of annotations in the class file than the final format. Support for this intermediate format has now been removed. Reading an annotation from a class file using the intermediate format which differs from the final format yields an exception similar to:

java.lang.reflect.GenericSignatureFormatError: Signature Parse error: Expected Field Type Signature

Recompiling the sources or otherwise regenerating the class file to conform to the proper format will resolve the issue.

See JDK-8265591

core-libs/java.net
 URL FTP Protocol Handler: IPv4 Address Validation in Passive Mode

Client-side FTP support in the Java platform is available through the FTP URL stream protocol handler, now referred to as the FTP Client.

The following system property has been added for validation of server addresses in FTP passive mode.

  • jdk.net.ftp.trustPasvAddress.

In this release, the FTP Client has been enhanced to reject an address sent by a server, in response to a PASV command from the FTP Client, when that address differs from the address which the FTP Client initially connected.

To revert to the prior behavior, the jdk.net.ftp.trustPasvAddress system property can be set to true. The affect of setting this property is that the FTP Client accepts and uses the address value returned in reply to a PASV command

JDK-8258432 (not public)

core-libs/java.nio
 New Implementation of java.nio.channels.Selector on Microsoft Windows

The Windows implementation of the java.nio.channels.Selector API has been replaced in this release to use a new more scalable implementation. No behavior or compatibility issues were observed during testing of the new implementation. The old implementation has not been removed and the JDK can be configured to use the old implementation, if needed, by running with -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.WindowsSelectorProvider on the command line.

See JDK-8266369

core-libs/java.util
 Extra '0' in java.util.Formatter for '%012a' Conversion With a Sign Character

In previous releases, formatter conversions with a %a conversion that used the 0 padding flag and a width specifier would produce paddings containing too many zeros if a leading sign or space character was also specified by their respective flags. This has been fixed so that paddings no longer include too many leading zeros.

See JDK-8262351

core-libs/java.util:collections
 Collections.unmodifiable* Methods Are Idempotent for Their Corresponding Collection

The unmodifiable* methods in java.util.Collections will no longer re-wrap a given collection with an unmodifiable view if that collection has already been wrapped by same method.

See JDK-6323374

core-libs/java.util:i18n
 Support for CLDR Version 39

Locale data based on Unicode Consortium's CLDR has been upgraded to version 39. For the detailed locale data changes, please refer to the Unicode Consortium's CLDR release notes:

See JDK-8258794

core-libs/java.util:i18n
 ISO 639 Language Codes for Hebrew/Indonesian/Yiddish

Historically, Java has used old/obsolete ISO 639 language codes for Hebrew/Indonesian/Yiddish languages to maintain compatibility. From Java 17, the default codes are the current codes. For example, "he" is now the language code for "Hebrew" instead of "iw". A new system property has also been introduced to revert to the legacy behavior. If -Djava.locale.useOldISOCodes=true is specified on the command line, it behaves the same way as the prior releases.

See JDK-8263202

core-svc/java.lang.instrument
 Requirements of an Agent's premain Method Changed to Conform to the Specification

The java.lang.instrument implementation has been changed in this release to require that agent premain and agentmain methods are public. The specification has always required this, but it was not enforced. Attempting to run with an agent where these methods are not public will fail with an exception such as:

java.lang.IllegalAccessException: method <fully-qualified-class-name>.premain must be declared public.

A related change in this release is that the premain and agentmain methods must be defined in the agent class. The implementation no longer searches for these methods in superclasses.

See JDK-8165276

docs/release_notes
 XML Implementation Specific Features and Properties

Documentation for Implementation Specific Features and Properties has been added to the java.xml module summary. Along with the existing properties, two new properties are introduced in JDK 17. The following section describes the changes in more detail:

  1. Added javadoc for the XML processing limits.

    XML processing limits were introduced in JDK 7u45 and JDK 8. They were previously documented in the Java Tutorial Processing Limits section.

    The definitions for these limits have been added to the java.xml module summary. See JDK-8261670.

  2. Moved the javadoc for JAXP Lookup Mechanism to the java.xml module summary.

    The javadoc for JAXP Lookup Mechanism has been moved to the module summary. The original javadoc in JAXP factories are replaced with a link to that section in the module summary.

    See JDK-8261673.

  3. Added a property to control the newline after the XML header for DOM LSSerializer.

    The DOM Load and Save LSSerializer did not have an explicit control for whether or not the XML Declaration ends with a newline. In this release, a JDK implementation specific property, jdk.xml.isStandalone, and its corresponding System property, jdk.xml.isStandalone, have been added to control the addition of a newline and acts independently without having to set the pretty-print property. This property can be used to reverse the incompatible change introduced in Java SE 7 Update 4 with an update of Xalan 2.7.1 in which a newline is omitted after the XML header.

    Usage:

    // to set the property, get an instance of LSSerializer
    
    LSSerializer ser = impl.createLSSerializer();
    // the isStandalone property is effective whether or not pretty-print is set
    ser.getDomConfig().setParameter("format-pretty-print", pretty ? true : false);
    ser.getDomConfig().setParameter("jdk.xml.isStandalone", standalone ? true : false);
    
    // to use the System property, set it before initializing a LSSerializer
    System.setProperty("jdk.xml.isStandalone", standalone ? “true” : "false");
    
    // to clear the property, place the line anywhere after the LSSerializer is initialized
    System.clearProperty("jdk.xml.isStandalone");
    

    See JDK-8249867.

  4. Added a property to control the newline after the XML header for XSLTC Serializerjava.xml.

    The XSLTC Serializer supported a property, http://www.oracle.com/xml/is-standalone, introduced through JDK-7150637, to control whether or not the XML Declaration ends with a newline. It is, however, not compliant with the new specification for Implementation Specific Features and Properties. In order to maintain compatibility, the legacy property is preserved, and a new property, jdk.xml.xsltcIsStandalone, along with its corresponding System property, jdk.xml.xsltcIsStandalone, have been created to perform the same function for the XSLTC Serializer as the isStandalone property for DOMLS LSSerializer. Note that the former has an extra prefix xsltc to avoid conflict with the later in case it is set through the System property.

    Usage:

    // to set the property, get an instance of the Transformer
    
    Transformer transformer = getTransformer(…);
    // the isStandalone property is effective whether or not pretty-print is set
    transformer.setOutputProperty(OutputKeys.INDENT, pretty ? "yes" : "no");
    transformer.setOutputProperty("jdk.xml.xsltcIsStandalone", standalone ? "yes" : "no");
    
    // to use the System property, set it before initializing a Transformer
    System.setProperty("jdk.xml.xsltcIsStandalone", standalone ? "yes" : "no");
    
    // to clear the property, place the line anywhere after the Transformer is initialized
    System.clearProperty("jdk.xml.xsltcIsStandalone");
    

    See JDK-8260858.

  5. Added existing features and properties and standardizing the prefix to jdk.xml.

    Existing features and properties have been added to the Implementation Specific Features and Properties tables in the java.xml module summary. All of the features and properties, existing and new, now have a prefix of jdk.xml as redefined in the Naming Convention section. System properties are searchable in the Java API documentation by the full name, such as jdk.xml.entityExpansionLimit.

    See JDK-8265252.

See JDK-8261856

hotspot/gc
 Segmentation Fault Error on 9th and 10th Generation Intel® Core™ Processors

When running Java on 9th and 10th Gen Intel® Core™ processors, a segmentation fault indicating invalid permissions for a mapped object may be observed. A workaround is included that reduces the frequency of the occurrences.

See JDK-8263710

hotspot/gc
 Parallel GC Enables Adaptive Parallel Reference Processing by Default

Parallel GC now ergonomically determines the optimal number of threads to use for processing java.lang.ref.Reference instances during garbage collection. The option -XX:ParallelRefProcEnabled is now true (enabled) by default.

The change improves this phase of the garbage collection pause significantly on machines with more than one thread available for garbage collection.

If you experience increased garbage collection pauses, you can revert to the original behavior by specifying -XX:-ParallelRefProcEnabled on the command line.

The ergonomics of java.lang.ref.Reference processing can be tuned by using the experimental option -XX:ReferencesPerThread (default value: 1000).

See JDK-8204686

security-libs/java.security
 New System Property Added to Enable the OCSP Nonce Extension

A new system property, jdk.security.certpath.ocspNonce, has been added to enable the OCSP Nonce Extension. This system property is disabled by default, and can be enabled by setting it to the value true. If set to true, the JDK implementation of PKIXRevocationChecker includes a nonce extension containing a 16 byte nonce with each OCSP request. See RFC 8954 for more details on the OCSP Nonce Extension.

See JDK-8256895

security-libs/java.security
 Updated keytool to Create AKID From SKID of Issuing Certificate as Specified by RFC 5280

The gencert command of the keytool utility has been updated to create AKID from the SKID of the issuing certificate as specified by RFC 5280.

See JDK-8257497

security-libs/java.security
 Updated Specifications of KeyStoreSpi.engineStore(KeyStore.LoadStoreParameter) and KeyStore.store(KeyStore.LoadStoreParameter) Methods

The specifications of the KeyStoreSpi.engineStore(KeyStore.LoadStoreParameter param) and KeyStore.store(KeyStore.LoadStoreParameter param) methods have been updated to specify that an UnsupportedOperationException is thrown if the implementation does not support the engineStore() operation. This change adjusts the specification to match the existing behavior.

See JDK-8246005

security-libs/java.security
 jarsigner Tool Warns if Weak Algorithms Are Used in Signer’s Certificate Chain

The jarsigner tool has been updated to warn users when weak keys or cryptographic algorithms are used in certificates of the signer’s certificate chain.

See JDK-8259401

security-libs/javax.net.ssl
 SocketExceptions Are Not Wrapped Into SSLExceptions in SSLSocketImpl

This release reverts the behavior of SSLSocketImpl and SSLTransport introduced by JDK-8196584. SocketException will now be thrown as is instead of being suppressed into an SSLException.

See JDK-8259662

specification/language
 JEP 306: Restore Always-Strict Floating-Point Semantics

Floating-point operations are now consistently strict, rather than having both "strict" floating-point semantics (strictfp) and subtly different "default" floating-point semantics. This restores the original floating-point semantics of the language and VM, matching the semantics before the introduction of "strict" and "default" floating-point modes in Java SE 1.2.

For further details, see JEP 306.

See JDK-8175916

tools/javadoc(tool)
 Improved Nested Class Summary

When a class or interface has nested classes or interfaces, the list is improved to show the kind of class or interface, such as enum class, record class, annotation interface, as appropriate.

See JDK-8266044

tools/javadoc(tool)
 Improved Package Summary Pages

The summary page for a package has been restructured to display the different kinds of classes and interfaces in a single tabbed table, instead of a series of separate tables. Additional links have been provided in the navigation bar at the top of the page, to aid in faster navigation to different parts of the page.

See JDK-8263507

tools/javadoc(tool)
 Improved Output for @see Tags

When a declaration has a series of @see tags, the output is generated in the form of an HTML <ul> list, instead of a simple comma-separated list of links. The style of the list depends on the number and kind of the links.

See JDK-8262992

tools/javadoc(tool)
 Ids Used by the Standard Doclet

"Multi-word" ids in the HTML generated by the Standard Doclet have been converted to a uniform style of lowercase words separated by hyphens. This primarily affects the ids used to navigate within the generated documentation and does not affect the ids used for field and method declarations, and which may be used in external pages to reference such declarations within the documentation.

See JDK-8261976

tools/javadoc(tool)
 Improved "Help" Page

The content of the "Help" page generated by the Standard Doclet has been revised, improved, and new information added.

  • There is a new "Navigation" section that provides general information on how to navigate around the documentation.
  • Information about the different kinds of pages has been gathered into a new section, along with new information about pages that were not previously documented.
  • There is a brief "table of contents" at the top of the page that provides links to all of the sections and subsections on the page.

In addition, the HELP link in the navigation bar for each kind of page now links directly to the section on the Help page for that kind of page.

See JDK-8263198

tools/javadoc(tool)
 Legal Headers for Generated Files

The set of files generated by the Standard Doclet typically includes some files with associated licensing requirements. The Standard Doclet now provides support for including the associated legal files, with default behavior for the common case and a new command-line option (--legal-notices) to override that behavior when appropriate.

See JDK-8259530

tools/javadoc(tool)
 Check for Empty Paragraphs

DocLint (invoked from javac and javadoc with the -Xdoclint option) now checks for constructs that lead to empty paragraphs in the generated documentation, which might be flagged by an HTML validator. The most common cause is the redundant use of <p> at the end of a block of text.

See JDK-8258957

tools/javadoc(tool)
 DocLint Reports Missing "descriptions"

DocLint detects and reports documentation comments that do not have any description about the associate declaration, before any block tags that may be present. (DocLint is a feature of the javac and javadoc tools, to detect and report issues in documentation comments.)

See JDK-8272374

core-libs/java.lang:class_loading
 URLClassLoader No Longer Throws Undocumented IllegalArgumentException From getResources and findResources

In the event that there is a problem getting a resource, URLClassLoader.getResource() and findResource() now return null instead of throwing an undocumented IllegalArgumentException. The same is true of Enumerations obtained from URLClassLoader.getResources() and URLClassLoader.findResources().

This behavior conforms with the long-standing specification. The situation would typically occur on Windows, due to the use of a Windows-style path ("c:/windows").

See JDK-8262277

core-libs/java.lang
 Less Ambiguous Processing of ProcessBuilder Quotes on Windows

In the java.lang.ProcessBuilder implementation on Windows, the system property jdk.lang.Process.allowAmbiguousCommands=false ensures, for each argument, that double-quotes are properly encoded in the command string passed to Windows CreateProcess. An argument with a final trailing double-quote preceded by a backslash is encoded as a literal double-quote; previously, the argument including the double-quote would be joined with the next argument. An empty argument is encoded as a pair of double-quotes ("") resulting in a zero length string passed for the argument to the process; previously, it was silently ignored. An argument containing double-quotes, other than first and last, is encoded to preserve the double-quotes when passed to the process; previously, the embedded double-quotes would be dropped and not passed to the process. If a security manager is set, such as in WebStart applications, double-quotes are encoded as described. When there is no security manager, there is no change to existing behavior; the jdk.lang.Process.allowAmbiguousCommands property can be set to true: jdk.lang.Process.allowAmbiguousCommands=true or false. If left unset, it is the same as setting it to true.

JDK-8250568 (not public)