Problem
Updating Java from one primary revision to the next leaves the previous build of Java installed.
Example:Java 7u60 is installed. After applying Java 8u20, Java 7u60& Java 8u20 are both installed.
Cause
The Vendor has not designed the patch to uninstall previous primary revisions.
Solution / Workaround
When LDMS deploys a Java patch, the file is ran as a silent install.
This means that it is installed with default options selected for the patch.
Though this vendor has designed patches within the same revision to remove old builds (i.e. Java 7u60 to Java 7u71 - 'in-place-upgrade'), they have not designed it to uninstall old revisions when a new build is installed (i.e. Java 7u60 to Java 8u20).
More information from Vendor: Patch-in-Place and Static JRE Installation
This behavior can be verified by manually installing a newer revision on a machine with an older revision.
Example: On a machine with Java 7u60 installed, manually download and install Java 8u20. This will result in both applications being installed.
Note: Manual installs will provide users the option to uninstall previous builds, but there is not currently a supported switch option for this.
More information from Vendor: How do I arrange a silent (unattended) Java installation?
The old copy of Java would need to be removed through other means, such as a package to uninstall that build of Java.