Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-3322

[EAP7] After applying an EAP cumulative patch, replaced JAR files should be removed from the container

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • None
    • EAP7, EAP_CD
    • None

      When applying a cumulative patch to EAP7, new, "patched" JAR files are placed under the .overlays directory and are active for EAP7 from this location. Older, replaced JAR file still reside in their original locations on the file system within the container. Vulnerability scanners, such as Twistlock, will report "false positives" for these older replaced JAR files that aren't actually active and being used.

      This also makes sense from a slimming perspective. We are leaving wasted space in the containers.

              kwills@redhat.com Ken Wills
              rhn-support-trogers Travis Rogers (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: