Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-24935

Jolokia can not be enabled in XP4 JDK17 images

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • EAP-XP-4.0.0.GA
    • None
    • OpenShift
    • None
    • False
    • None
    • False
    • + 

      podman run -it registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap-xp4-openjdk17-openshift-rhel8:4.0-1
podman exec -it $(podman ps -q) /opt/eap/bin/livenessProbe.sh true probe.eap.jolokia.EapProbe

      results in

      Traceback (most recent call last):
  File "/opt/eap/bin/probes/runner.py", line 87, in <module>
    runner.addProbe(probeClass())
  File "/opt/eap/bin/probes/probe/eap/jolokia.py", line 37, in __init__
    HealthCheckTest()
  File "/opt/eap/bin/probes/probe/jolokia.py", line 39, in __init__
    self.__readConfig()
  File "/opt/eap/bin/probes/probe/jolokia.py", line 62, in __readConfig
    with open("/opt/jolokia/etc/jolokia.properties") as jolokiaProperties:
FileNotFoundError: [Errno 2] No such file or directory: '/opt/jolokia/etc/jolokia.properties'

      The root cause seems to be the same issue as described in WFWIP-465. The image has by default AB_JOLOKIA_OFF=true . In comparison the variable is not present in the JDK11 image at all. Setting it to false doesn't help.

       

      This is a regression compared to the JDK11 image, so setting priority to blocker.

              rh-ee-rnovelli Ruben Novelli
              pmackay@redhat.com Peter Mackay
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: