Service refresh 4

Service refresh 4

This release contains the latest IBM® fixes and the January 2017 Oracle Critical Patch Update (CPU). Support for Windows Server 2016 is also included at this refresh level.

Service refresh 4 fix pack 5

Jar files signed with MD5 are treated as unsigned

To improve security, a new restriction is introduced in this refresh as part of the Oracle Critical Patch Update (CPU). Applications, including Applets or Web Start applications that use jar files that are signed with MD5 are affected. These jar files are treated as unsigned. To address the issue, the jar file must be re-signed with a stronger algorithm or key size. For more information about this change, which includes a short term workaround, see the Oracle JRE and JDK Cryptographic roadmap.

Specify Java™ options using a manifest file

Java options can now be specified by using a manifest file. In introducing this new capability, the order in which options are passed to the VM at start up is changed. For more information, see: Specifying command-line options.

-XX:[+|-]IgnoreUnrecognizedVMOptions

Unrecognized top-level Java VM options can now be ignored using the -XX:+IgnoreUnrecognizedVMOptions option. This behavior prevents the VM failing on startup. For more information, see: -XX:[+|-]IgnoreUnrecognizedVMOptions option.

Service refresh 4 fix pack 10