The latest Java package contains a critical memory leak that can cause the DCO server to run out of memory and shut down, typically within a few days. https://bugs.openjdk.java.net/browse/JDK-8164293
DCO 8.x installations or upgrades performed after June 26, 2017 (Java 1.8.0_144 release date) may be affected.
A DCO server can shut down within a few days as it runs out of memory if the Java package Java 1.8.0_144 is installed. If the server is running fine, it is unlikely to have this Java package. Only the Java 1.8.0_144 version is affected.
This issue will be fixed when Java 1.8.0_152 is released as a CentOS package, expected in Oct 2017. For more information, see http://openjdk.java.net/projects/jdk8u/releases/8u152.html
There are some workarounds for this issue:
For clean installs
Put the server in offline mode by turning interfaces off in Network & Host Name settings.
Select offline mode before upgrading.
For DCO servers already in this situation
If the DCO server is already in this situation, perform the following steps.
If the server is offline
Run this command to check the Java version:
If the server is online
- SSH login to the server.
Verify that it has the issue.
Run the command:
yum list installed java-1.8.0-openjdk*Check that the versions start with: ‘1:22.214.171.124’, ex: ‘1:126.96.36.199-0.b01.el7_4’
If the server is offline, run this command to check the Java version:
- Run the following single command:
yum downgrade java-1.8.0-openjdk java-1.8.0-openjdk-headless-188.8.131.52-2.b16.el7_4.x86_64 java-1.8.0-openjdk-devel-184.108.40.206-2.b16.el7_4.x86_64Verify that the package has successfully been downgraded.
- Run the command:
yum list installed java-1.8.0-openjdk*Check that the versions start with: ‘1:220.127.116.11’, ex: ‘1:18.104.22.168-2.b16.el7_4’
- Reboot the server.