2021. 5. 28. 03:06ㆍ카테고리 없음
What Version of Java Are You Using?
- How To Check Current Java Version In Windows 7
- Latest Java Version Windows 7
- Java For Windows 7 Free
- Most Current Java Version
On a computer with multiple web browsers, be sure to check the Java version in every browser. I say this because multiple copies of Java can sometimes be installed with different browsers using different copies. Also, Java can be enabled in one browser and disabled in another.
Note: The portion of Java that runs programs is referred to as either the Java Run-time Environment (JRE) or the Java Virtual Machine (JVM).
Jul 18, 2019 This wikiHow teaches you how to check what version of java you have installed on your Windows computer using Command Prompt. Click the Windows Start icon. It's the icon with Windows logo. By default, it's in the bottom-left corner of the. Upgrading to the latest Java version improves the security of your system, as older versions do not include the latest security updates. Java allows you to play online games, chat with people around the world, calculate your mortgage interest, and view images in 3D, just to name a few.
Method 1: Ask Java
I support an old Java client application that runs fine on Windows XP but not Windows 7 32 bit. The problem is in the BAT file used to launch the application. The BAT file contains code that queries the registry for the CurrentVersion of Java and then uses that value to determine the path of that version of Java on the user's computer.
This is my favorite - straight from the horse's mouth (so to speak). The Java Run-time Environment is aware of its version and the company that authored it. So I wrote a very simple applet (the source code is on the About page) that gets this information from the JRE and displays it in a pink rectangle.
| The version and vendor from the JRE |
If Java is working, you will see a pink rectangle above with one line of text that says something like: Java Version 1.8.0_25 from Oracle Corporation or |
| Version number translation: 1.6.0_34 is, in English, Java 6 Update 34 The initial '1' is ignored as is the third digit. Ask Oracle why. |
| RUNNING THIS APPLET: Java security has changed quite a lot over the years and running this applet has gotten much more complicated. In part this is because the applet is unsigned. In the Bizarro world of Oracle, unsigned applets are treated as more dangerous than signed applets. This is backwards for two reasons. First, unsigned applets run in a restricted Java sandbox whereas signed applets are given unrestricted access to the system. Yes, the sandbox has been buggy and broken, but some security is better than none. Second, it shows a faith in the Certificate Authority system that is unwarranted. February 2017: This applet will not run at all, immediately after installing Java 8 Update 121 on Windows 7. The first thing that needs to be done is to add this website as an allowed exception in the Java Control Panel, on the Security tab. Details are below. After doing so, IE11 will run the app, but only if ActiveX filtering is disabled. IE11 produces a single popup window that asks for permission to run the app. Chrome 56 won't do Java at all, it doesn't even bother with error messages. This started with Chrome 45. Likewise, Firefox 51 does not run Java. It incorrectly reports that Java is disabled. This Firefox behavior changed at the end of 2016. Version 47 of Firefox will run this applet. You first have to respond to three different popup windows asking for permission and warning of the end of the earth, but it will run. Oracle suggests that Java developers move from applets to Java Web Start. |
| OLDER SECURITY RESTRICTIONS ON JAVA IN BROWSER October 2014: Java 7 Update 71 and Java 8 Update 25: The applet above can be run with Java set to the default 'high' security level. There will be assorted 'as you sure' type prompts both from Java and your web browser, but it will run. However, this site, javatester.org, needs to first be added to the 'Exception Site List' using the Java Control Panel. When adding sites to the list, you have to prefix them with HTTP colon slash slash. Java will object to HTTP but it will accept it. There is no HTTPS version of this site. Also, if you add 'javatester.org' to the list, you must then go to 'javatester.org' as 'www.javatester.org' will fail. Because it is unsigned, this applet will not run with Java set to the 'very high' security level. January 2014: Java 7 Update 51 changed the default security rules for unsigned Java applets such as the one on this page. By default, Java no longer runs any unsigned applets. In the Java control panel, the default security level with Update 51 is 'High' which Oracle describes as 'Java applications identified by a certificate from a trusted authority will be allowed to run'. What this does not say is that unsigned applets will not run, at least not by default. If you get an error on this page that says 'Application blocked by security settings' this is probably why. One way to run an unsigned applet is to lower the security level to 'Medium'. The other way is to add trusted websites to a new exception list that Oracle/Java maintains. This list is not to be confused with the list of trusted applets that Firefox or Chrome maintains. Yes, there are now three lists of applets that are naughty and nice. Java 7 Update 10 introduced a new checkbox that disables the use of Java in all browsers. By and large, this is a good thing, but there seems to be a failure to communicate between Java and many web browsers. As a result, all the browsers I have tried so far incorrectly report that Java is not installed when, in fact, it may be installed but this new security feature has been enabled. As of Java 7 Update 71 and Java 8 Update 25 this is still true on Windows machines. Interestingly, if Java is disabled system-wide for use in web browsers (its on the Security) tab, both Chrome and Firefox will not even show the Java plug-in as being installed. On the flip side, Firefox 33 on Windows 7 reports that 'Browser has Java disabled' when Java is not installed. |
| JAVA VERSION HISTORY (Wikipedia has this too) |
| JAVA 8 Release History Java 8 became the default on Windows on Oct 14, 2014. See the Java 8 FAQ Java 8 is not officially supported on Windows XP but should work. Oracle has a release history for Java 7 and 8 and Release notes for Java 8 |
I used to keep a release history here, but since Wikipedia has a release history for Java 8, there is no need for me to continue doing my own, so I stopped maintaining it near the end of 2017. |
Java on Mac Computers
Java on OS X is Bundling Crapware, Heres How to Make it Stop from How-To Geek March 17, 2015.
At times Java on OS X was complicated as Java 6 came from Apple and Java 7 came from Oracle.
For many years this page had eight other methods of determining the installed version of Java.
But the page got really big, so they are no longer shown by default. But, they are still available:
News
Abstract
Support Information for IBM® SDK, Java™ Technology Edition, Version 7 that is not available in the user documentation.
Content
The documentation to support this release is available in the online product documentation . However, from service refresh 10 fix pack 25, only the security documentation is still maintained. Any updates or changes to other content are detailed in this technote.
Changes to the online content:
Supplementary information is available for the following updates:
To compare the IBM SDK functionality with Oracle build levels at each service refresh level, see Comparative Oracle build levels .
For information about security fixes, see Security Alerts .
For a list of the IBM fixes included, see IBM SDK, Java Technology Edition, Version 7 fixes .
To download the latest service refresh, visit the Java SDK developer center .
For information about the daylight saving time changes included in service refreshes and fix pack levels, see Olson time zone updates . Later updates can by applied using the IBM Time Zone Update Utility for Java (JTZU) .
Changes to online content:
Configuring large page memory allocation on z/OS systems
There are changes to the content in the topic Configuring large page memory allocation . 1M pageable large pages are supported only on IBM zEnterprise EC12® or later systems. The online documentation states that the Flash Express® feature (#0402) is required. However, it is actually not required but recommended, only to avoid demoting 1 MB pageable large pages to 4 K pages when paging is required during periods of high real memory usage. When the 1 MB pageable large pages are demoted to 4 K pages, they remain as 4 K pages until a future system IPL.
On z/OS 2.3 and later, 1M pageable large pages are available by default. You no longer need to set the PAGESCM=ALL option in the IEASYSxx parmlib member.
Supplementary updates:
Service refresh 10 fix pack 50 (July 2019)
This release includes the latest IBM fixes.
Service refresh 10 fix pack 45 (April 2019)
This release adds support for the new Japanese era name, Reiwa. For more information, see Japanese era changes for the IBM SDK, Java Technology Edition.
Service refresh 10 fix pack 40 (February 2019)
Changes to Korean codepoint mappings
In previous releases, if you used EUC-KR encoding to convert between EUC-KR codepoints and Unicode during string conversion, some Korean characters were not mapped to the expected Unicode values. This result is because the EUC-KR codepage was based on the IBM970 codepage. This behavior has been corrected in this release. The affected characters are as follows:
| EUC-KR mapping | Correct Unicode mapping | Character | Incorrect Unicode mapping | Character |
|---|---|---|---|---|
| 0xA1A4 | u00B7 | Middle dot | u30FB | Katakana middle dot |
| 0xA1A9 | u00AD | Soft hyphen | u2010 | Hyphen |
| 0xA1AA | u2015 | Horizontal bar | u2014 | Em dash |
| 0xA1AD | u223C | Tilde operator | u301C | Wave dash |
| 0xA2A6 | uFF5E | Full-width tilde | u02DC | Small tilde |
| 0xA2C1 | u2299 | Circled dot operator | u25C9 | Fisheye |
Note: java.nio.charset classes already used the correct mappings and are unaffected.
If you require the previous mappings, specify the -Dibm.useCp970=true system property on the command line when you run your application.
In addition, the following characters from the KS X 1001 standard have been added:
| EUC-KR mapping | Unicode mapping | Character |
|---|---|---|
| 0xA2E6 | u20AC | Euro sign |
| 0xA2E7 | u00AE | Registered sign |
| 0xA2E8 | u327E | Korean postal code mark (circled hangul ieung u) |
Service refresh 10 fix pack 20 (Jan 2018)
Out of memory exceptions when running applications with compressed references enabled
The Oracle CPU for January contains an update for CVE-2018-2582 to fix vulnerabilities in the Hotspot virtual machine (VM) that might be exploited by Java web start applications and applets. Fixes are also applied for the OpenJ9 virtual machine. The fix increases the amount of low memory used for VMs that use compressed references. Customers who are running close to the maximum amount of allowed 32-bit memory might experience out of memory exceptions. A possible workaround is to use the -Xmcrs option to secure space in the lowest 4GB memory area for any native classes, monitors, and threads that are used by compressed references.
For more information about this option, see -Xmcrs .
Service refresh 10 fix pack 10 (October 2017)
Support for z/OS v2.3
This update includes support for z/OS v2.3.
Service refresh 10 fix pack 1 (February 2017)
Security vulnerability CVE-2016-2183
A further fix is added to mitigate against this vulnerability, which is described here . (APAR IV93288)
Service refresh 9 fix pack 10 (July 2015)
Partial fix for change in behavior for -Xshareclasses:destroyAll
In service refresh 8 fix pack 10 a behavior change was reported for this option on z/OS platforms. See Change in behavior for -Xshareclasses:destroyAll .
Following a fix for the 64-bit JVM, the problem remains only on the 31-bit JVM. When the destroyAll option is invoked from a 31-bit JVM, 64-bit caches are not destroyed. The following message is displayed:
JVMSHRC735I Use a 64-bit JVM to perform the requested operation on the 64-bit shared cache 'cachename' as the 31-bit JVM cannot verify that the shared memory was created by the JVM
Service refresh 8 fix pack 10 (February 2015)
Change in behavior for -Xshareclasses:destroyAll
Due to a current issue on z/OS, when the destroyAll option is invoked from a 31-bit Java virtual machine (JVM), 64-bit caches are not removed. Similarly, when the destroyAll option is invoked from a 64-bit JVM, 31-bit caches are not removed. The following message is displayed:
JVMSHRC735I: Use a nn-bit JVM to perform the requested operation on the nn-bit shared cache 'cachename' as the nn-bit JVM cannot verify that the shared memory was created by the JVM.
Service refresh 6 fix pack 1 (January 2014)
Default behaviour change when running unsigned or self-signed applets
Unsigned or self-signed applets no longer run by default because the security settings are changed to high. If you want to run unsigned or self-signed applets, you must change the security settings to medium. You can make this change in the Java Control Panel. Select the Security tab and move the slider to adjust the security level. This behavior change is not applicable to z/OS® or Linux on system Z platforms.
Service refresh 4 fix pack 2 (May 2013)
How To Check Current Java Version In Windows 7
This fix pack includes a change to the default value for the RMI property java.rmi.server.useCodebaseOnly from false to true, which might cause unexpected errors for applications that use RMI. For more information, see http://docs.oracle.com/javase/7/docs/technotes/guides/rmi/enhancements-7.html .
On Windows, improvements are made to the way that Runtime.exec decodes command strings. However, applications specifying commands that contain spaces in the program name, or that use quotation marks incorrectly, might fail to start. For more information, including guidance on resolving problems, see http://www.oracle.com/technetwork/java/javase/7u21-relnotes-1932873.html#jaruntime .
Service refresh 4 fix pack 1 (April 2013)
This fix pack contains a security fix for the Oracle security vulnerability, CVE-2013-0169 . For any further security fixes in this release, see Security alerts .
Service refresh 3 (November 2012)
PKCS11 security provider
A new library is available that allows the IBMPKCS11Impl provider to run on the Linux AMD64 platform.
IBM SDK for Java Version 7 initial release (September 2011)
The SDK is functionally equivalent to the Oracle FCS version of Java 7 b147 for all distributions except Solaris, which is b148.
The z/OS® 31-bit and 64-bit SDKs are supported on z/OS 1.13.
Comparative Oracle build levels
The following table indicates the Oracle FCS build level that has comparative functionality to the IBM SDK:
| Release date | IBM SDK 7 | Oracle Java 7 FCS build |
| September 2011 | Initial release | Build 147 |
| May 2012 | Service refresh 1 | Update 3 Build 5 |
| September 2012 | Service refresh 2 | Update 3 Build 5 |
| November 2012 | Service refresh 3 | Update 6 Build 17 |
| February 2013 | Service refresh 4 | Update 13 Build 8 |
| July 2013 | Service refresh 5 | Update 25 Build 12 |
| November 2013 | Service refresh 6 | Update 45 Build 18 |
| January 2014 | Service refresh 6 fix pack 1 | Update 51 Build 11 |
| April 2014 | Service refresh 7 | Update 55 Build 13 |
| July 2014 | Service refresh 7 fix pack 1 | Update 65 Build 19 |
| November 2014 | Service refresh 8 | Update 71 Build 13 |
| February 2015 | Service refresh 8 fix pack 10 | Update 75 Build 13 |
| May 2015 | Service refresh 9 | Update 79 Build 14 |
| July 2015 | Service refresh 9 fix pack 10 | Update 85 Build 15 |
| November 2015 | Service refresh 9 fix pack 20 | Update 91 Build 15 |
| January 2016 | Service refresh 9 fix pack 30 | Update 95 Build 12 |
| April 2016 | Service refresh 9 fix pack 40 | Update 101 Build 14 |
| July 2016 | Service refresh 9 fix pack 50 | Update 111 Build 13 |
| October 2016 | Service refresh 9 fix pack 60 | Update 121 Build 15 |
| February 2017 | Service refresh 10 fix pack 1 | Update 131 Build 12 |
| April 2017 | Service refresh 10 fix pack 5 | Update 141 Build 11 |
| July 2017 | Service refresh 10 fix pack 10 | Update 151 Build 15 |
| October 2017 | Service refresh 10 fix pack 15 | Update 161 Build 13 |
| January 2018 | Service refresh 10 fix pack 20 | Update 171 Build 11 |
| May 2018 | Service refresh 10 fix pack 25 | Update 181 Build 09 |
| August 2018 | Service refresh 10 fix pack 30 | Update 191 Build 08 |
| November 2018 | Service refresh 10 fix pack 35 | |
| March 2019 | Service refresh 10 fix pack 40 | Update 211 Build 07 |
| April 2019 | Service refresh 10 fix pack 45 | Update 221 Build 08 |
| July 2019 | Service refresh 10 fix pack 50 | Update 231 Build 08 |
Internal Use Only
Latest Java Version Windows 7
This technote to support late breaking information is included as a link in the readme file that is packaged with the downloadable code bundle.
Java For Windows 7 Free
Document Information
Most Current Java Version
Modified date:
01 August 2019