[ https://issues.jboss.org/browse/JBIDE-23429?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23429: ------------------------------------- Here are some basic examples to test: Standalone / on wf - eap 1) Start wildfly or eap on localhost / standalone.sh 2) Deploy jolokia's jolokia-war-1.3.5.war to the standalone/deployments 3) Open jmx explorer and create new jmx connection 4) Give a name, put http://localhost:8080/jolokia-war-1.3.5/ as url, and use POST method 5) Connect to the new connection, expand it, play in the UI Behind CDK + EAP: Reference doc: http://developers.redhat.com/blog/2016/03/30/jolokia-jvm-monitoring-in-op... 1) Start CDK 2) Enable port forwarding on openshift connection 3) Create jolokia connection as above, except: 4) Use this as url: https://<master_host>:8443/api/v1/namespaces/<project_name>/pods/https:<pod_name>:8778/proxy/jolokia 5) Make sure to use GET (POST doesn't fully work in this case) 6) Make sure to add Authorization / Bearer: blahblah to the headers section, as per the above document. This can be discoverd by using oc whoami –t after oc login 7) Expand jmx tree, play in UI, call an operation or two, probably shouldn't call jmx shutdown operation though ;) -- This message was sent by Atlassian JIRA (v7.2.2#72004)