-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
We do not generate images using 7.3.x-legacy, however, any third party consuming jboss.eap.cd.jolokia modules could be affected by this one.
I found this using jboss-eap-7-openshift-image/CD17 branch with jboss-eap-modules/7.3.x-legacy. The server does not start and the following error is shown in the console:
docker run -it --rm jboss-eap-7-tech-preview/eap-cd-openshift-rhel8 WARN Configuration of an embedded messaging broker within the appserver is enabled but is not recommended. Support for such a configuration will be removed in a future release. INFO If you are not configuring messaging destinations, to disable configuring an embedded messaging broker set the DISABLE_EMBEDDED_JMS_BROKER environment variable to true. WARN No password defined for JGroups cluster. AUTH protocol will be disabled. Please define JGROUPS_CLUSTER_PASSWORD. WARN Environment variable OPENSHIFT_KUBE_PING_NAMESPACE undefined. Clustering will be unavailable. Please refer to the documentation for configuration. INFO Configuring JGroups discovery protocol to kubernetes.KUBE_PING INFO Configuring JGroups cluster traffic encryption protocol to SYM_ENCRYPT. WARN Detected missing JGroups encryption configuration, the communication within the cluster WILL NOT be encrypted. Using PicketBox SSL configuration. WARN Missing SSO_URL. Unable to properly configure SSO-enabled applications INFO Access log is disabled, ignoring configuration. INFO Running jboss-eap-7-tech-preview/eap-cd-openshift-rhel8 image, version 17.0 /opt/eap/bin/standalone.conf: line 175: syntax error: unexpected end of file
The problem is there are invalid characters in the standalone.conf changes added by jboss.eap.cd.jolokia and introduced in CLOUD-3398. See the output of: cat -v jboss-eap-cd-jolokia/added/standalone.conf
- relates to
-
CLOUD-3398 [EAP-CD] - Update jolokia for new jakarta jar locations
-
- New
-