How to Update Only Java on Your Oracle Solaris 1. Systemby Peter Dennis and Alta Elstad. This article describes how to update Java without updating any other software. Java might be updated multiple times in an Oracle Solaris release, so you should follow this procedure periodically. Published May 2. 01. Java is part of the Oracle Solaris 1. Usually, best practice is to update system software together, as a tested- together supported set. Oracle Solaris 1. Packages named in an incorporation might themselves be incorporations or might require a particular version of another package to be installed. So the set of packages affected by an incorporation—or constrained by the incorporation—can be much larger than the set named in the incorporation package. If you try to install a different version of a package whose version is constrained by an incorporation, you will receive an error message and the update or install operation will fail. In general, the supported way to update a package whose version is constrained by an incorporation is to update the incorporation package. Sometimes you need to install software that is constrained by an incorporation at a different version than the incorporation allows. For example, you might need to install a security update. This article describes how to update one piece of software that is constrained by an incorporation without altering any other software that is constrained by that incorporation, and still end up with a supported system. The software updated in this example is Java. ![]() A security issue has been identified that could allow an attacker to compromise your Windows-based system with Microsoft Visual C++ 2008 Redistributable Package. Update and Hotfix Reopsitory for Windows 7, Windows 8 and Windows 8.1 client and servers. Git is installed and is in the path. Platform: Red Hat Enterprise Linux 5.8. Here’s a teaser photo of the upcoming Apollo IE (pronounced, I think, as “eye-ee” and not “ee”). It will apparently have tons of carbon fiber, which we all. ![]() For more information about incorporations, see “Structure of Oracle Solaris 1. Software” in the article “More Tips for Updating Your Oracle Solaris 1. System from the Oracle Support Repository.”Oracle Solaris 1. Java SE 7 packages that are version- constrained by the java- incorporation package. You cannot update this package simply by updating the java- incorporation package, because this package is in turn constrained by the pkg: /entire incorporation package. To update Java without updating the pkg: /entire package, unlock the version- lock facet of the Java incorporation package and then update the Java incorporation package, as described in the following procedure, which describes how to update the global zone. For more information about version- lock facets, see “Relaxing Version Constraints Specified by Incorporations” in Chapter 5, “Configuring Installed Images” of Adding and Updating Oracle Solaris 1. Software Packages. Check whether an updated package is available: Make sure an update is available for the java- incorporation package. If your solaris publisher origin is a local location, make sure that local repository is current with the latest updated packages. If you change your publisher origin or update your local package repository, refresh the publisher or refresh or rebuild the repository. Unlock the version- lock facet: Change the value of the version- lock facet of the java- incorporation package to false, as shown in Listing 1. The number of packages to update is the number of packages installed in this image, because each package in the image is checked for this facet. As a best practice, do the update first with the - nv options, as shown in Listing 2, to see what will be updated. As a best practice, use the - -be- name option, as shown in Listing 3, to make the changes only in a new boot environment (BE) and leave the current boot environment unchanged as a backup. In some cases, installing or updating packages in the global zone affects non- global zones as well. This is not true for Java: You can have different versions of Java installed in the global and non- global zones. If you want updated versions of Java in non- global zones, perform those updates separately, as described below. If you used the - -be- name option during the global zone update, you might want to reboot to the new BE and update the non- global zones there. In the following example, only the java- incorporation package is updated. Notice that in the global zone example above, the java- incorporation package and the jre- 7 package were updated. The non- global in this example does not have the jre- 7 package installed. Unlocking and updating the java- incorporation package ensures that if Java 7 is installed in this zone at a later time, it will be installed at the newer version. Log in to the zone and check the currently installed version of the java- incorporation package. You can use the - n or - -be- name options in non- global zones, though this example does not show those options. See the global zone example above to see how to use those options. He has worked on a wide variety of technologies: file systems, volume management and backup, cluster, and general end- user utilities. He is currently the technical lead for the Oracle Solaris 1. Alta Elstad is a technical writer supporting Oracle Solaris 1. Java SE 6 Update 1. Release Notes. Update Release Notes Index. Update Release Notes Index. Changes in 1. 6. 0. The external version number is 6u. Olson. Data 2. 00. Olson time zone data version 2. For more information, refer to Timezone Data Versions in the JRE Software . Security Baseline. Java Plug- in technology: JRE Family Version. Java SE. Security Baseline. Java for Business. Security Baseline. Future revisions of Java SE 1. Visual. VM 1. 2 introduces the following features and enhancements: Sampling CPU and Memory profiler plugin (Visual. VM- Sampler available on Plugins Center)Support for multiple jstatd connections on a single local/remote host. New charts with dynamic tooltips, public Charts API for plugins. Monitor and Threads tab are saved into Application Snapshot. Application Snapshots can be opened using the Load action or - -openfile parameter. Properties UI for Applications, Hosts and Snapshots, public Properties API for plugins. Customizable proxy settings in Options dialog. UI for customizing SSL certificates in Options dialog (Visual. VM- Security available on Plugins Center)Enhanced JMX API to enable customizing JMX environment/connections by plugins. Display name defined by the monitored application: visualvm. Improved performance for remote X sessions. Automatic detection of broken jvmstat on Windows (username capitalization vs. Java DB 1. 0. 5. 3. SQL Roles. Generated Columns. LOB Improvements. Replication of encrypted databases. OFFSET/FETCH FIRST syntax. In- memory back end. Better updating of optimizer statistics. Service- tag aware installers. Java DB home page. Performance Improvements. Faster jar File Creation. The fix of a long standing bug related to jar file creation has greatly improved creation time. For example, for a given jar file, it is possible that you might see a creation time improvement in the range of 2. Contributing to increased performance in this release are several enhancements in Java Hot. Spot VM 1. 6. 0. These include: Improved NUMA- aware allocation. Extensions to compressed object pointers. Garbage collection improvements. Updated Client JVM heap configuration In the Client JVM, the default Java heap configuration has been modified to improve the performance of today's rich client applications. Initial and maximum heap sizes are larger and settings related to generational garbage collection are better tuned. The default maximum heap size is half of the physical memory up to a physical memory size of 1. A much smaller amount, termed the initial heap size, is allocated during JVM initialization. This amount is at least 8 megabytes and otherwise 1/6. The maximum amount of space allocated to the young generation is one third of the total heap size. The updated heap configuration ergonomics apply to all collectors except Concurrent Mark- Sweep (CMS). CMS heap configuration ergonomics remain the same. Server JVM heap configuration ergonomics are now the same as the Client, except that the default maximum heap size for 3. JVMs is 1 gigabyte, corresponding to a physical memory size of 4 gigabytes, and for 6. JVMs is 3. 2 gigabytes, corresponding to a physical memory size of 1. Work stealing termination. Work queue overflow processing. Bit set processing on 6. Linux. Class loading optimizations for faster startup (see Bug Fixes section)Code generation improvements. New intrinsics using SSE 4. New intrinsics for Integer/Long bit operations - leading/trailing zeros, bit count. Unsigned byte and integer loads. Integer load shortening. Elision of needless conversions between integer primitive types. Optimization of common string concatenation patterns. In addition to performance enhancements, Hot. Spot VM 1. 6. 0 offers improved reliability and serviceability. Serviceability enhancements. New options to request a heap dump or class histogram before or after a full GCNew tool to decode Log. Compilation output. Extensive reliability improvements (see Bug Fixes section). Note that Escape analysis- based optimization ( - XX: +Do. Escape. Analysis) is disabled in 6u. This option will be restored in a future Java SE 6 update. Application Startup Improvements. Better startup of applications and applets on systems where D3. D is used. Savings are up to 1. Improves warm start of typical FX applications by up to 1. See jcp. org for updated specification. Java extensions are components described in JNLP files that are typically intended to be used by a large number of applications and applets. The new security dialog is triggered by an application that references the Java extension in its JNLP file (by including it in the resources element). The security dialog will ask the user if they would like to install the extension. Once the extension is installed, it can be referenced by other applications without the need for asking the user's permission again (as long as it is the same extension from the same codebase). You can find more details about these Maintenance Reviews in the JSR 1. Change Log. Also refer to 6. The St. AX 1. 2 upgrade maintains binary and source compatibility. Existing binaries compiled on St. AX 1. 0 will continue to run on St. AX 1. 2. Programs written to St. AX 1. 0 will continue to compile to St. AX 1. 2. There will be a minor behavioral difference if deprecated methods are used. In this case, there will be deprecation warnings at compilation. Other than these warning messages, the St. AX 1. 2 upgrade maintains behavioral compatibility. Known Issues. The Java Install Issue. When installing Java on a 6. Windows system, the 6. This will cause all 3. Java. FX) to fail when 6. Java was installed last (after 3. Java). This issue applies to any JNLP based applications. The workaround for this issue is to install the 6. Java first, and then install the 3. Java. If they were installed in the other order, then reinstalling the 3. Java will fix. Refer to 6. Card- Marking Optimization Issue. A flaw in the implementation of a card- marking performance optimization in the JVM can cause heap corruption under some circumstances. This issue affects the CMS garbage collector prior to 6u. CMS, G1 and Parallel Garbage Collectors in 6u. The serial garbage collector is not affected. Applications most likely to be affected by this issue are those that allocate very large objects which would not normally fit in Eden, or those that make extensive use of JNI Critical Sections (JNI Get/Release*Critical). This issue will be fixed in the next Java SE 6 update. Meanwhile, as a workaround to the issue, users should disable this performance optimization by - XX: -Reduce. Initial. Card. Marks. Refer to 6. Bug Fixes. This feature release does not contain any new fixes for security vulnerabilities to its previous release, Java SE 6 Update 1. Users who have Java SE 6 Update 1. Bug fixes are listed in the following table. Bug. Id. Category. Subcategory. Description. VM crash using Non. Blocking. Hash. Map (high. TEMP ordering restrictions are too strong. Use auxv to determine SPARC hardware features on Solaris. Block's frequency should not be Na. N6. 81. 28. 31 hotspotcompiler. Load shortening optimizations. G1: Type lost in g. Bug 6. 50.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
August 2017
Categories |