TinyButStrong Error in field [var.version...]: the key 'version' does not exist or is not set in VarRef. (VarRef seems refers to $GLOBALS) This message can be cancelled using parameter 'noerr'.

TinyButStrong Error in field [var.version...]: the key 'version' does not exist or is not set in VarRef. (VarRef seems refers to $GLOBALS) This message can be cancelled using parameter 'noerr'.
 Java Runtime Environment 軟體歷史版本 Download Page28 :: 軟體兄弟

Java Runtime Environment 歷史版本列表 Page28

最新版本 [var.version]

Java Runtime Environment 歷史版本列表

Java Runtime Environment(JRE)允許您玩在線遊戲,與世界各地的人聊天,計算您的抵押貸款利息,並在 3D 中查看圖像,僅舉幾例。選擇版本:Java JRE 8 更新 152(32 位)Java JRE 9.0.1(64 位)選擇版本:內部網應用程序和其他電子商務解決方案是企業計算的基礎。 Java Runtime Environment 軟體介紹

Java Runtime Environment (32-bit)Java Runtime Environment (64-bit)


Java JRE 8 Update 102 (32-bit) 查看版本資訊

更新時間:2016-07-20
更新細節:

What's new in this version:

Enhancements:
- Internal package sun.invoke.anon has been removed
- New property jdk.lang.processReaperUseDefaultStackSize
- Implemented performance improvements for BigInteger.montgomeryMultiply

Changes:
- MSCAPI KeyStore can handle same-named certificates
- Modify requirements on Authority Key Identifier extension field during X509 certificate chain building
- Providing more granular levels for GC verification
- Removed PICL warning message
- Improved exception handling for bad LDAP referral replies

Bug Fixes:
- Fix to resolve "Unable to process PreMasterSecret, may be too big" issue

Java JRE 8 Update 102 (64-bit) 查看版本資訊

更新時間:2016-07-20
更新細節:

What's new in this version:

Enhancements:
- Internal package sun.invoke.anon has been removed
- New property jdk.lang.processReaperUseDefaultStackSize
- Implemented performance improvements for BigInteger.montgomeryMultiply

Changes:
- MSCAPI KeyStore can handle same-named certificates
- Modify requirements on Authority Key Identifier extension field during X509 certificate chain building
- Providing more granular levels for GC verification
- Removed PICL warning message
- Improved exception handling for bad LDAP referral replies

Bug Fixes:
- Fix to resolve "Unable to process PreMasterSecret, may be too big" issue

Java JRE 8 Update 92 (32-bit) 查看版本資訊

更新時間:2016-04-19
更新細節:

What's new in this version:

Notable bug fixes included in this release:
- SHA224 removed from the default support list if SunMSCAPI enabled
- SunJSSE allows SHA224 as an available signature and hash algorithm for TLS 1.2 connections. However, the current implementation of SunMSCAPI does not yet support SHA224. This can cause problems if SHA224 and SunMSCAPI private keys are used at the same time.
- To mitigate the problem, we remove SHA224 from the default support list if SunMSCAPI is enabled.
- New JVM Options added: ExitOnOutOfMemory and CrashOnOutOfMemory

Two new JVM flags have been added:
- ExitOnOutOfMemory - When you enable this option, the JVM exits on the first occurrence of an out-of-memory error. It can be used if you prefer restarting an instance of the JVM rather than handling out of memory errors.
- CrashOnOutOfMemoryError - If this option is enabled, when an out-of-memory error occurs, the JVM crashes and produces text and binary crash files (if core files are enabled).

Java JRE 8 Update 92 (64-bit) 查看版本資訊

更新時間:2016-04-19
更新細節:

What's new in this version:

Notable bug fixes included in this release:
- SHA224 removed from the default support list if SunMSCAPI enabled
- SunJSSE allows SHA224 as an available signature and hash algorithm for TLS 1.2 connections. However, the current implementation of SunMSCAPI does not yet support SHA224. This can cause problems if SHA224 and SunMSCAPI private keys are used at the same time.
- To mitigate the problem, we remove SHA224 from the default support list if SunMSCAPI is enabled.
- New JVM Options added: ExitOnOutOfMemory and CrashOnOutOfMemory

Two new JVM flags have been added:
- ExitOnOutOfMemory - When you enable this option, the JVM exits on the first occurrence of an out-of-memory error. It can be used if you prefer restarting an instance of the JVM rather than handling out of memory errors.
- CrashOnOutOfMemoryError - If this option is enabled, when an out-of-memory error occurs, the JVM crashes and produces text and binary crash files (if core files are enabled).

Java JRE 8 Update 77 (32-bit) 查看版本資訊

更新時間:2016-03-23
更新細節:

What's new in this version:

IANA Data 2016a:
- JDK 8u77 contains IANA time zone data version 2016a.

Security Baselines:
- The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 8u77 is 1.8.0_77.

JRE Expiration Date:
- This JRE (version 8u77) will expire with the release of the next critical patch update scheduled for April 19, 2016.

Notes:
- This Security Alert (8u77) is based off the earlier 8u74 PSU release. All users of earlier JDK 8 releases should update to this release.

Bug Fixes:
- This Security Alert addresses CVE-2016-0636, a vulnerability affecting Java SE running in web browsers on desktops. This vulnerability is not applicable to Java deployments, typically in servers or standalone desktop applications, that load and run only trusted code. It also does not affect Oracle server-based software. This vulnerability may be remotely exploitable without authentication (i.e., may be exploited over a network without the need for a username and password). To be successfully exploited, an unsuspecting user running an affected release in a browser will need to visit a malicious web page that leverages this vulnerability. Successful exploits can impact the availability, integrity, and confidentiality of the user's system.
- Due to the severity of this vulnerability and the public disclosure of technical details, Oracle strongly recommends that customers apply the updates provided by this Security Alert as soon as possible.

Java JRE 8 Update 77 (64-bit) 查看版本資訊

更新時間:2016-03-23
更新細節:

What's new in this version:

IANA Data 2016a:
- JDK 8u77 contains IANA time zone data version 2016a.

Security Baselines:
- The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 8u77 is 1.8.0_77.

JRE Expiration Date:
- This JRE (version 8u77) will expire with the release of the next critical patch update scheduled for April 19, 2016.

Notes:
- This Security Alert (8u77) is based off the earlier 8u74 PSU release. All users of earlier JDK 8 releases should update to this release.

Bug Fixes:
- This Security Alert addresses CVE-2016-0636, a vulnerability affecting Java SE running in web browsers on desktops. This vulnerability is not applicable to Java deployments, typically in servers or standalone desktop applications, that load and run only trusted code. It also does not affect Oracle server-based software. This vulnerability may be remotely exploitable without authentication (i.e., may be exploited over a network without the need for a username and password). To be successfully exploited, an unsuspecting user running an affected release in a browser will need to visit a malicious web page that leverages this vulnerability. Successful exploits can impact the availability, integrity, and confidentiality of the user's system.
- Due to the severity of this vulnerability and the public disclosure of technical details, Oracle strongly recommends that customers apply the updates provided by this Security Alert as soon as possible.

Java JRE 8 Update 74 (32-bit) 查看版本資訊

更新時間:2016-02-06
更新細節:

Java JRE 8 Update 74 (64-bit) 查看版本資訊

更新時間:2016-02-06
更新細節:

Java JRE 8 Update 72 (32-bit) 查看版本資訊

更新時間:2016-01-20
更新細節:

Java JRE 8 Update 72 (64-bit) 查看版本資訊

更新時間:2016-01-20
更新細節: