Enable JMX for "DEV_MODE" for eap-images

[tsmaeder]

The managment functionalities are bound to 127.0.0.1 only in OpenShift-EAP (see https://access.redhat.com/documentation/en/openshift-enterprise/3.0/using-images/chapter-5-xpaas-middleware-images#comparing-the-jboss-eap-xpaas-image-to-the-regular-release-of-jboss-eap). Since standard remote jmx does not work inside Openshift (random port needs to be forwarded), this effectively prevents developers from using tools like JConsole, JVisualVM, etc.

I propose to enable jmx vie jboss remoting in all eap/wildfly images provided. It should be possible to set up the necessary usernames/passwords via environment variables so tooling can connect automatically.

[rcernich]

You should be able to see any JMX details directly through the OpenShift console. Go to the pod page and click on the "Connect" button.

[tsmaeder]

@i am aware of that, what I'm trying to do is to connect existing tooling like JVisualVM to the EAP inside Openshift. Also, I am trying to improve the debugging experience: https://issues.jboss.org/browse/JBIDE-21857

[propyless]

@rcernich can one have OpenShift console show the link to the JMX console when using a custom image? if yes, how to activate that?

[rcernich]

You need to have an exposed port on the pod that's named "jolokia" which means you need to configure the jolokia agent and it should use the k8s cert for authentication. You can see how jolokia is configured in our images here, where the only environment variable set is AB_JOLOKIA_AUTH_OPENSHIFT=true. Here's the entry point. HTH