Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
AMQ 7.8.0.CR4
-
None
-
False
-
False
-
Undefined
Description
In order to discover AMQ Brokers 7.8 in Fuse Console, we still need some steps to be implemented in the AMQ Operator:
1. Enable jolokia using env var AMQ_ENABLE_JOLOKIA_AGENT=true
2. Add the jolokia as port to the broker stateful set:
For instance:
oc patch statefulset/broker2-ss -p '{"spec":{"template":{"spec":{"containers":[{"ports":[{"name":"jolokia","containerPort":"8778","protocol":"TCP"}]}]}}}}'
3. Update jolokia.properties to point on the right Cacert service-ca.crt instead of ca.crt:
caCert=/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt
For instance:
oc create configmap broker-jolokia-config --from-file=jolokia.properties
# mount the ConfigMap into the AMQ image
oc set volume statefulset $AMQ_NAME-ss --add --overwrite \
--name=broker-jolokia-config \
--mount-path=/opt/jolokia/etc/jolokia.properties \
--sub-path=jolokia.properties \
--source='{"configMap":{"name":"broker-jolokia-config"}}'
oc delete pods -l ActiveMQArtemis=$AMQ_NAME
oc get sts broker2-ss -o yaml | grep broker-jolokia-config
oc rsh $AMQ_NAME-ss-0 cat /opt/jolokia/etc/jolokia.properties
Attachments
Issue Links
- is cloned by
-
-
- Closed
-
- is related to
-
ENTMQBR-3392 Centralized AMQ Console
-
- Closed
-
- mentioned in
-
Page Loading...
