[
https://issues.jboss.org/browse/JBIDE-22318?page=com.atlassian.jira.plugi...
]
Thomas Mäder edited comment on JBIDE-22318 at 5/11/16 3:54 AM:
---------------------------------------------------------------
Was able to connect JConsole to Openshift. Here are the steps that are to do:
# Had to create my own run script for s2i
the start script uses standalone-openshift.sh, which adds "-bmanagement
127.0.0.1" to the command line. This makes it impossible to forward to that port from
localhost.
# Had to add the port 9999 to the forwardable ports of the pod in the deployment config
# Had to add username/password for a managment user via add-user.sh
# Start port forwarding for the pod
was (Author: tmader):
Was able to connect JConsole to Openshift. Here are the steps that are to do:
# Had to create my own run script for s2i
the start script uses standalone-openshift.sh, which adds "-bmanagement
127.0.0.1" to the command line. This makes it impossible to forward to that port from
localhost.
# Had to add the port 9999 to the forwardable ports of the pod in the deployment config
# Had to add username/password for a managment user via add-user.sh
Create JMX PoC Connection to Openshift EAP
------------------------------------------
Key: JBIDE-22318
URL:
https://issues.jboss.org/browse/JBIDE-22318
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Reporter: Thomas Mäder
Assignee: Thomas Mäder
Fix For: 4.4.x
Find out what is needed to connect to an EAP instance inside an Openshift pod
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)