Includes support for latest Java standards and makes development much easier using the built-in database. It also supports debugging and monitoring for Java apps.
Currently, many programs and most of the popular internet browsers (Internet Explorer, Mozilla Firefox, Opera and others) work with Java technology. It is indispensable for all those lovers of the internet, instant messaging and video games.
Java Runtime Environment version 6 update 11 installs Java Virtual Machine, a platform that works with files .Class, and in that way it provides the environment required to run Java applications. These applications that use the Java programming language and access from your browser are called “applets”.
In the Java (TM) version 6 Update 11, the developer patches 14 vulnerabilities detected in previous versions, some of which are:
- In instant messaging, a candidate window was not shown until the window is deactivated and reactivated again.
- Camerfirma root certificates are added to Java Development Kit.
- The UTF-8 charset implementation has also been updated to handle the non-shortest forms of UTF-8 byte sequences, which caused incompatibilities with previous versions.
In other words, the main reason to install this update is the improvement of security of the software and the correction of the security vulnerabilities. For the users of Mac it is very important to verify these types of updates on Apple's website, because Apple maintains this product in Mac OS on their own.
v14.0 [Jun 22, 2020]
core-libs
- Accounting Currency Format Support
Currency format instances with accounting style, in which the amount is formatted in parentheses in some locales, can be obtained by calling NumberFormat.getCurrencyInstance(Locale) with the "u-cf-account" Unicode locale extension. For example in Locale.US, it will format to "($3.27)" instead of "-$3.27". Refer to CLDR's accounting currency format style for additional information.
See JDK-8215181
core-libs/java.lang
- JEP 359 Records (Preview)
In JDK 14, the Records (JEP 359) preview feature adds a new class java.lang.Record. The java.lang package is implicitly imported on demand, that is, import java.lang.*. If code in an existing source file imports some other package on demand, for example, import com.myapp.*;, and that other package declares a type called Record, then code in the existing source file which refers to that type will not compile without change. To make the code compile, import the other package's Record type using a single-type import, for example, import com.myapp.Record;.
See JDK-8222777
core-libs/java.nio
- Clarify the Specification of ReadableByteChannel.read() and Related Methods
The specifications of the DatagramChannel.receive(), FileChannel.read(ByteBuffer,long), ReadableByteChannel.read(), and ScatteringByteChannel.read() methods have been updated in this release to specify that an IllegalArgumentException is thrown if (any of) the buffer parameter(s) is read-only. This change merely adjusts the specification to match existing long term behavior.
See JDK-8164993
hotspot/gc
- JEP 365 ZGC on Windows
The Z Garbage Collector (ZGC) is now available as an experimental feature on Windows. To enable it, use the JVM flags -XX: UnlockExperimentalVMOptions -XX: UseZGC. See JEP 365: ZGC on Windows for more information.
See JDK-8232364
hotspot/gc
- JEP 364 ZGC on macOS
The Z Garbage Collector (ZGC) is now available as an experimental feature on macOS. To enable it, use the JVM flags -XX: UnlockExperimentalVMOptions -XX: UseZGC. See JEP 364: ZGC on macOS for more information.
See JDK-8229358
hotspot/gc
- Parallel GC Improvements
Parallel GC has adopted the same task management mechanism for scheduling parallel tasks as other collectors. This might result in significant performance improvements. Because of this change, the following product flags have been obsoleted: -XX:BindGCTaskThreadsToCPUs, -XX:UseGCTaskAffinity, and -XX:GCTaskTimeStampEntries.
See JDK-8224666
hotspot/gc
- JEP 345 NUMA-Aware Memory Allocation for G1
The G1 garbage collector now tries to allocate and keep objects on the same NUMA node in the young generation across garbage collections. This is similar to Parallel GC NUMA awareness.
G1 attempts to evenly distribute Humongous and Old regions across all available NUMA nodes using a strict interleave. Placement of objects copied from young to old generation is random.
These new NUMA-Aware Memory Allocation heuristics are automatically enabled by using the -XX: UseNUMA command line option. See JEP 345: NUMA-Aware Memory Allocation for G1 for more information.
See JDK-8210473
hotspot/jfr
- JEP 349 JFR Event Streaming
JDK Flight Recorder (JFR) now supports continuous monitoring of a Java application by allowing events to be consumed dynamically using a new API located in the jdk.jfr.consumer package. The feature is always enabled when using JFR, meaning recorded data up to the last second is available for both in process and out of process consumption. See JEP 349: JFR Event Streaming for more information.
See JDK-8184193
security-libs/java.security
- Weak Named Curves in TLS, CertPath, and Signed JAR Disabled by Default
Weak named curves are disabled by default by adding them to the following disabledAlgorithms security properties: 'jdk.tls.disabledAlgorithms', 'jdk.certpath.disabledAlgorithms', and 'jdk.jar.disabledAlgorithms'. The named curves are listed below.
With 47 weak named curves to be disabled, adding individual named curves to each disabledAlgorithms property would be overwhelming. To relieve this, a new security property, 'jdk.disabled.namedCurves', is implemented that can list the named curves common to all of the disabledAlgorithms properties. To use the new property in the disabledAlgorithms properties, precede the full property name with the keyword include. Users can still add individual named curves to disabledAlgorithms properties separate from this new property. No other properties can be included in the disabledAlgorithms properties.
