Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-1553

Fix Max Heap estimation detection on Java 11

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.4.0.GA
    • 1.4.0.GA
    • None
    • None
    • 0
    • Hide

      This occurs in the following situations:

      • Resource limit / request is set
      • -Xmx / -Xms is not set
      Show
      This occurs in the following situations: Resource limit / request is set -Xmx / -Xms is not set
    • 2019.14, 2019.15, 2020.1, 2020.2

      When building and running the images with Java 11, the max heap detection doesn't work in the Kafka / Zookeeper pods. This happens when the memory limit / requests are set and the -Xmx / -Xms options are supposed to be auto-detected.

      The problem is that Java 11 doesn't support anymore the -XX:+UseCGroupMemoryLimitForHeap option. This PR replaces it with -XX:+UseContainerSupport which seems to work fine on our latest Java 8 builds and Java 11 builds and fixes the problem.

      AMQ Streams 1.3.0 never shipped images with Java 11, so this does not need to be in AMQ Streams release notes.

            Unassigned Unassigned
            scholzj JAkub Scholz
            Jakub Stejskal Jakub Stejskal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: