[jbosstools-issues] [JBoss JIRA] (JBIDE-23429) Jolokia JMX connection

Rob Stryker (JIRA) issues at jboss.org
Tue Nov 1 10:06:01 EDT 2016


    [ https://issues.jboss.org/browse/JBIDE-23429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13314897#comment-13314897 ] 

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-openshift/
   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 ;) 

> Jolokia JMX connection
> ----------------------
>
>                 Key: JBIDE-23429
>                 URL: https://issues.jboss.org/browse/JBIDE-23429
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: jmx
>    Affects Versions: 4.4.2.AM2
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.4.2.AM3
>
>
> A jolokia JMX connection would be useful for some users, and could also be used to connect to JMX for an EAP behind openshift / cdk. 



--
This message was sent by Atlassian JIRA
(v7.2.2#72004)



More information about the jbosstools-issues mailing list