-
Bug
-
Resolution: Done
-
Major
-
None
-
EAP74 7.4.3.GA
-
None
I'm investigating a Fuse issue https://issues.redhat.com/browse/ENTESB-18355.
There is a problem with jdk11 image, caused by Jolokia, which is fixed as https://github.com/rhuss/jolokia/issues/438.
Fixed version is 1.6.3 (or higher).
Issue could be reproduced with docker:
- Run image fuse7/fuse-eap-openshift-jdk11-rhel8 with exposed port 8778 (for example "docker run -d -p 8080:8080 -p 9990:9990 -p:8778:8778 registry.redhat.io/fuse7/fuse-eap-openshift-jdk11-rhel8"
- Get jolokia auth information by running "docker exec #container_id cat /opt/jolokia/etc/jolokia.properties"
- Access https://127.0.0.1:8778/jolokia/read/java.lang:type=Runtime using credentials from above. (curl should work, but it didn't show any response in my case, so I used browser)
You will see following error:
{"request":{"mbean":"java.lang:type=Runtime","type":"read"},"stacktrace":"java.lang.UnsupportedOperationException: Boot class path mechanism is not supported\n\ ...
Jolokia jar is present on eap-image at
opt/jboss/container/jolokia/jolokia.jar
and version is 1.6.2.redhat-00002
- clones
-
JBEAP-23179 (7.4.z) Jolokia #438 Reading runtime mbean fails on JDK11
- Closed
- relates to
-
ENTMQBR-6638 Jolokia Agent could not start due to java.lang.IllegalArgumentException: Cannot instantiate class sun.security.x509.X500Name
- Closed