{"id":183379,"date":"2026-09-17T16:54:20","date_gmt":"2026-09-17T14:54:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/vypusk-java-se-27-i-openjdk-27"},"modified":"2026-09-17T16:54:25","modified_gmt":"2026-09-17T14:54:25","slug":"java-se-27-and-openjdk-27-released","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/java-se-27-and-openjdk-27-released","title":{"rendered":"Release of Java SE 27 and OpenJDK 27","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After six months of development, Oracle announced Java SE 27 (Java Platform, Standard Edition 27), with OpenJDK as its reference implementation. Except for the removal of some deprecated features, Java SE 27 maintains backward compatibility with previous releases of the Java platform\u2014most previously written Java projects will run without changes on the new version. Installable builds of Java SE 27 (JDK, JRE, and Server JRE) are prepared for Linux (x86_64, AArch64), Windows (x86_64), and macOS (x86_64, AArch64). The reference implementation of Java SE 27 developed within the OpenJDK project is fully open under the GPLv2 license with GNU ClassPath exceptions allowing dynamic linking with commercial products. <\/p>\n
Java SE 27 is categorized as a release with a regular support period, with updates to be released up until the next version. For long-term support (LTS), Java SE 25, Java SE 21, or Java SE 17 should be used, with updates to be released until 2033, 2031, and 2029 respectively (public updates until September 2030, 2028, and 2026). Extended support for the LTS branch of Java SE 8 will last until 2030, while Java SE 11 will be supported until 2032. <\/p>\n
Among the changes in Java SE 27 (1, 2, 3, 4): <\/p>\n
\n
By default, the G1 (Garbage-First) garbage collector is enabled for all environments, which was previously used for server systems. G1 is optimized for use on multiprocessor systems with large memory and balances predictability of latencies with high throughput. During operation, G1 divides memory into many small regions and first cleans those regions with more unused objects and fewer actively used data.\n
In HotSpot JVM, compact object headers are enabled by default. The header size on 64-bit systems has been reduced from 96 to 64 bits, which has decreased memory consumption and increased the likelihood of data fitting into the processor cache. In SPECjbb2015 tests, memory consumption decreased by 22%, CPU load was reduced by 8%, and the number of garbage collection operations was reduced by 15%. During JSON parser testing, the test execution time was reduced by 10%.\n
The implementation of TLS 1.3 has included support for hybrid key agreement schemes that combine the ML-KEM (CRYSTALS-Kyber) algorithm, resistant to quantum computer attacks, with classical algorithms based on elliptic curves ECDHE: X25519MLKEM768 (ECDHE with curve X25519 + ML-KEM-768), SecP256r1MLKEM76 (ECDHE with curve secp256r1 + ML-KEM-768), and SecP384r1MLKEM1024 (ECDHE with curve secp384r1 + ML-KEM-1024). In the javax.net API.ssl<\/a> These schemes are enabled by default and do not require changes to the applications for implementation.\n