- Java Runtime Environment Update Scenarios
- Updating Family JRE
- Installing «Family JRE» when a «Static JRE» is already present
- Installing «Static JRE» when older «Family JRE» is already present
- Installing older «Family JRE» when newer «Family JRE» is already present, then reinstalling older «Family JRE»
- Installing «Static JRE» when same JRE version of «Family JRE» is already present
- Attempting to install «Family JRE» when same JRE version of «Static JRE» is already present
- Installing new 6u18 «Family JRE» when old architecture JRE 6u2 is already present
- Installing older «Family JRE» when newer «Static JRE» is already present
- Applying consecutive patches
- Applying intermediate patches
- Installing later family version using offline installer
- Reinstalling «Static JRE» when older «Family JRE» installed.
- Reinstalling «Static JRE» without explicitly ever installing as static.
- Java Downloads
- JDK Development Kit 20.0.2 downloads
- Release information
- JDK Development Kit 17.0.8 downloads
- Release information
- GraalVM for JDK 20.0.2 downloads
- Release information
- GraalVM for JDK 17.0.8 downloads
- Release information
- Protect your investment—and more
- Java SE subscribers have more choices
- Java SE Development Kit 8u381
- JRE 8
- Server JRE 8
- Which Java 8 package do I need?
- Release information
- Java Runtime Environment 8u381
- Изменения в последней версии
Java Runtime Environment Update Scenarios
Java Runtime Environment (JRE) may be installed in family or static modes. This document describes various scenarios to demonstrate the behavior of the JRE update process starting in the Java SE 6 update 10 release. Release 6u10, 6u11, 6u12, and above are considered to be in the same family. Earlier updates of Java SE 6 do not support the ability patch in place.
Updating Family JRE
This is the most likely scenario.
- User installs JRE 6u17 as a «Family JRE» by default into c:\Program Files\Java\jre6
- User gets prompted by Java-Update to update to 6u18.
- User agrees, goes through Java-Update process.
- Java update recognizes that the 6u17 JRE was installed as a «Family JRE», and can therefore just simply patch-in-place to 6u18.
- Once finished, the user now has only one 6u18 «Family/Update JRE» located at c:\Program Files\Java\jre6. 6u17 no longer exists on the machine.
Installing «Family JRE» when a «Static JRE» is already present
- User installs 6u17 «Static JRE» into c:\Program Files\Java\jre1.6.0_10
- User gets prompted by Java-Update to update to 6u17.
- User agrees, goes through Java-Update process.
- Java update ignores the previous static installation of 6u17, and downloads a full copy of 6u18 «Family JRE» which is installed into c:\Program Files\Java\jre6.
- Once finished, the user now has both a 6u17 «Static JRE» at c:\Program Files\Java\jre1.6.0_17, and a 6u18 «Family JRE» at c:\Program Files\Java\jre6.
Installing «Static JRE» when older «Family JRE» is already present
- User installs 6u17 «Family JRE».
- It installs into c:\Program Files\Java\jre6.
- User then installs 6u18 «Static JRE».
- 6u18 «Static JRE» installer ignores the existence of 6u17 «Family JRE»., and downloads a full copy of 6u18 which is installed into c:\Program Files\Java\jre1.6.0_18.
- Once finished, the user now has both a family copy of 6u17 at c:\Program Files\Java\jre6, and a copy of 6u18 JRE c:\Program Files\Java\jre1.6.0_18.
Installing older «Family JRE» when newer «Family JRE» is already present, then reinstalling older «Family JRE»
- User installs 6u18 «Family JRE» into c:\Program Files\Java\jre6.
- User launches 6u17 iftw.exe installer in the default «family mode»( iftw stands for install from the web).
- 6u17 installer detects newer «Family JRE» is already present and switches to «static mode».
- The user now has both a family copy of 6u18 at c:\Program Files\Java\jre6, and a copy of 6u17 JRE c:\Program Files\Java\jre1.6.0_17.
- User launches 6u17 iftw.exe installer in the default «family mode».
- 6u17 installer detects that 6u17 is already installed as «Static JRE» and switches to «static mode». In «static mode» the installer prompts to reinstall. If the user selects yes, 6u17 «Static JRE» is uninstalled and reinstalled.
- When finished, the user now has both a family copy of 6u18 at c:\Program Files\Java\jre6, and a copy of 6u17 JRE c:\Program Files\Java\jre1.6.0_17.
Installing «Static JRE» when same JRE version of «Family JRE» is already present
- User installs 6u17 «Family JRE».
- User launches 6u17 «Static JRE» installer.
- Installer will uninstall 6u17 «Update JRE» and install a 6u17 «Static JRE». An entire download of the JRE 6u17 will take place.
- User will be left with 6u17 «Static JRE» at c:\Program Files\Java\jre1.6.0_17.
Attempting to install «Family JRE» when same JRE version of «Static JRE» is already present
- User installs 6u18 «Static JRE».
- User downloads/launches 6u18 «Family JRE» installer.
- The installer will launch the 6u18 «Static JRE» MSI and the user will be prompted if they want to reinstall.
- User agrees to reinstall.
- User will be left with a 6u18 «Static JRE»..
Installing new 6u18 «Family JRE» when old architecture JRE 6u2 is already present
- User installs 6u2 JRE, which does not have new patching architecture, nor does it have Static/Update installer mode.
- User downloads/launches 6u18 «Family JRE» installer, which has Static/Update installer ability.
- 6u18 ignores the already installed 6u2 JRE, downloads a full copy of 6u18 «Family JRE» and installs into c:\Program Files\Java\jre6
Installing older «Family JRE» when newer «Static JRE» is already present
- User installs 6u18 «Static JRE» into c:\Program Files\Java\jre1.6.0_18
- User launches 6u17 iftw.exe installer in the default «family mode».
- Once finished, the user now has both a static copy of 6u18 at c:\Program Files\Java\jre1.6.0_18, and a 6u17 «Family JRE».
Applying consecutive patches
- User installs 6u16 «Family JRE» (using online, kernel, or offline installer).
- User installs 6u17 «Family JRE» using online installer.
- 6u16 is patched in place to 6u17.
- User installs 6u18 «Family JRE» using online installer.
- 6u17 is patched in place to 6u18.
Applying intermediate patches
- User installs 6u15 «Family JRE» (using online, kernel, or offline installer).
- User installs 6u17 «Family JRE» using online installer.
- 6u15 is patched in place to 6u17.
- User installs 6u18 «Family JRE» using online installer.
- 6u17 is patched in place to 6u18.
Installing later family version using offline installer
- User installs 6u17 «Family JRE» (using online, kernel, or offline installer).
- User downloads 6u18 offline installer.
- User launches 6u18 offline installer in the default «Family JRE» mode.
- 6u17 is uninstalled and 6u18 «Family JRE» is installed.
- User will be left with a 6u18 «Family JRE».
Reinstalling «Static JRE» when older «Family JRE» installed.
- User installs 6u17 «Family JRE» (using online, kernel, or offline installer).
- User installs 6u18 «Static JRE» (using online or offline installer).
- User launches 6u18 «Family JRE» installer (online or offline).
- 6u18 installer detects that 6u18 «Static JRE» already exists and switches to «static mode». In «static mode» the install prompts to reinstall. If the user selects yes, 6u18 «Static JRE» is uninstalled and reinstalled.
- When finished, the user now has both a family copy of 6u17 «Family JRE» at c:\Program Files\Java\jre6, and a copy of 6u18 «Static JRE» c:\Program Files\Java\jre1.6.0_18.
Reinstalling «Static JRE» without explicitly ever installing as static.
- User installs 6u18 «Family JRE» (using online, kernel, or offline installer).
- User installs 6u17 «Family JRE» in default mode (using online or offline installer). 6u17 is installed as «Static JRE». User now has 6u17 «Static JRE» and 6u18 «Family JRE».
- User uninstalls 6u18 «Family JRE». User now has 6u17 «Static JRE».
- User installs 6u16 «Family JRE» (using online or offline installer). User now has 6u16 «Family JRE» and 6u17 «Static JRE».
- User launches 6u17 «Family JRE» (using online or offline installer).
- 6u17 detects already installed as «Static JRE» and switches to «static mode». In «static mode» the install prompts to reinstall. If the user selects yes, 6u17 «Static JRE» is uninstalled and reinstalled.
- When finished, the user now has both a family copy of 6u16 «Family JRE» at c:\Program Files\Java\jre6, and a copy of 6u17 «Static JRE» c:\Program Files\Java\jre1.6.0_17.
Java Downloads
JDK 20 is the latest release of Java SE Platform and JDK 17 LTS is the latest long-term support release for the Java SE platform.
JDK Development Kit 20.0.2 downloads
JDK 20 binaries are free to use in production and free to redistribute, at no cost, under the Oracle No-Fee Terms and Conditions.
JDK 20 will receive updates under these terms, until September 2023 when it will be superseded by JDK 21.
Release information
JDK Development Kit 17.0.8 downloads
JDK 17 binaries are free to use in production and free to redistribute, at no cost, under the Oracle No-Fee Terms and Conditions.
JDK 17 will receive updates under these terms, until September 2024, a year after the release of the next LTS.
Release information
GraalVM for JDK 20.0.2 downloads
GraalVM for JDK 20 binaries are free to use in production and free to redistribute, at no cost, under the GraalVM Free Terms and Conditions.
GraalVM for JDK 20 will receive updates under these terms, until September 2023 when it will be superseded by GraalVM for JDK 21.
Oracle GraalVM uses the Graal just-in-time compiler and includes the Native Image feature as optional early adopter technology.
Native Image is extensively tested and supported for use in production, but is not a conformant implementation of the Java Platform. GraalVM for JDK 20 without the Native Image feature included is available for customers at My Oracle Support.
Release information
GraalVM for JDK 17.0.8 downloads
GraalVM for JDK 17 binaries are free to use in production and free to redistribute, at no cost, under the GraalVM Free Terms and Conditions.
GraalVM for JDK 17 will receive updates under these terms, until September 2024, a year after the release of the next LTS.
Oracle GraalVM uses the Graal just-in-time compiler and includes the Native Image feature as optional early adopter technology.
Native Image is extensively tested and supported for use in production, but is not a conformant implementation of the Java Platform. GraalVM for JDK 17 without the Native Image feature included is available for customers at My Oracle Support.
Release information
Script-friendly Download URLs
The URLs listed above will remain the same for update releases to allow their use in scripts.
Protect your investment—and more
Java SE subscribers get support for JDK 17, receive updates until at least October 2029, are entitled to GraalVM Enterprise, Java Management Service, and bundled patch releases (BPRs) with fixes not yet available to nonsubscribers, and more.
Java SE subscribers have more choices
Also available for development, personal use, and to run other licensed Oracle products.
Java SE Development Kit 8u381
Java SE subscribers will receive JDK 8 updates until at least December 2030.
The Oracle JDK 8 license changed in April 2019
The Oracle Technology Network License Agreement for Oracle Java SE is substantially different from prior Oracle JDK 8 licenses. This license permits certain uses, such as personal use and development use, at no cost — but other uses authorized under prior Oracle JDK licenses may no longer be available. Please review the terms carefully before downloading and using this product. FAQs are available here.
Commercial license and support are available for a low cost with Java SE Universal Subscription.
Java SE 8u381 checksums and OL 8 GPG Keys for RPMs
JRE 8
Java SE Runtime Environment 8u381
Server JRE 8
Server JRE (Java SE Runtime Environment) 8u381
Which Java 8 package do I need?
Software developers: Java SE Development Kit (JDK) For Java developers. Includes a complete JRE plus tools for developing, debugging, and monitoring Java applications.
Running headless Linux workloads at or near your systems’ CPU or memory limits Enterprise Performance Pack brings significant memory and performance improvements including modern garbage collection algorithms, reduced memory usage and many other optimizations. Learn more
Administrators running applications on a server Server Java Runtime Environment (Server JRE). For deploying Java applications on servers. Includes tools for JVM monitoring and tools commonly required for server applications, but does not include browser integration (Java plug-in), auto-update, or an installer. Learn more
End user running Java on a desktop: Java Runtime Environment (JRE) Covers most end-users needs. Contains everything required to run Java applications on your system.
Release information
Java Runtime Environment 8u381
Java Runtime Environment (JRE) — исполнительная среда созданная Sun Microsystems позволяющая запускать и использовать приложения написанные на языке программирования Java. Состоит из виртуальной машины — Java Virtual Machine и библиотеки Java-классов.
На языке Java написано множество программ и игр, особенно тех, для которых важна мобильность. Некоторые веб-страницы также используют Java. При этом не стоит путать Java с JavaScript. Последний гораздо более распространен в Интернете, но для своей работы не требует установки Java Runtime Environment (JRE) и интерпретируется непосредственно в интернет-браузере.
Одним из преимуществ языка Java является его кроссплатформенность, то есть приложения написанные на этом языке можно использовать на разных операционных системах, где установлен Java Runtime Environment (JRE).
Изменения в последней версии
Разработчик: | Sun Microsystems |
Официальный сайт: | www.java.com |
Обновлено: | 18.07.2023 |
Версия Windows : | Vista, 7, 8, 10 |
Язык интерфейса: | English |