-
Bug
-
Resolution: Done
-
Minor
-
FIS 1.0 - OpenShift Fuse 3.1-GA
-
None
-
None
-
%
-
FIS 2.0 Sprint 4
Before the jolokia access was secured with a proxy certificate it was possible to use jolokia for readiness / liveness probe checks..
See e.g. A-MQ readiness probe [1]
curl -s -L -u ${AMQ_ADMIN_USERNAME}:${AMQ_ADMIN_PASSWORD} 'http://localhost:8161/hawtio/jolokia/read/org.apache.activemq:type=Broker,brokerName=*,service=Health/CurrentStatus' | grep -q '\"CurrentStatus\" *: *\"Good\"'"
Such mechanism would be helpful for customer custom probes.
This feature would probably require to have jolokia bound twice (one to 0.0.0.0 with certificate access and the other bound to some local address (127.0.0.1) with a different security setting (e.g. a password generated in the template)
[1] https://github.com/jboss-openshift/application-templates/blob/ose-v1.1.0/amq/amq62-basic.json
- causes
-
ENTESB-8976 Red Hat Build of Jolokia 1.3.x
- Closed
- relates to
-
ENTESB-8922 general Karaf readiness probe for Karaf template and quickstarts
- Closed