Jolokia agent for artemis (maybe some others) should be configured

[ghost]

See for example, https://github.com/jboss-openshift/cct_module/blob/master/os-java-jolokia/added/jolokia-opts.

Otherwise, java console in openshift will not work. I am currently receiving the following error:

Error: 'tls: oversized record received with length 20527' Trying to reach: 'https://10.128.0.16:8161/jolokia/?maxDepth=7&maxCollectionSize=500&ignoreErrors=true&canonicalNaming=false'

Because openshift console proxy tries to use https, but it is configured by default as http (some other parameters are also needed).

[lulf]

I had this working a while ago, but I didn't move through with enabling https yet, because the hawkular-openshift-agent

• Needs to be configured with a client certificate trusted by the address space
• Needs to be configured to trust the address space CA and have hostname verification turned off

That being said, the fact that we're using Artemis as a broker for queues in the standard address space should not be exposed to the end user. So I view this more as a convenience for the messaging service operator rather than something a tenant of the messaging service would use.

[ghost]

I mean it for developer debugging, as it is the way to get JMX info from the java pods.

Other than that, it is very strange to have the "open java console" link in ocp, and get an error when we got there.

[lulf]

@vbusch have you been able to enable the open shift broker console for Artemis? Is this something we can reuse here?

[ctron]

I think the OpenShift Jolokia console won't work the way it is set up currently. There is a port named "jolokia" and the "Open Java Console" appears in the OpenShift Web UI.

However then the connection fails and I think it may be due to the fact that the Artemis broker deploys this to "/console/jolokia" instead of "/jolokia" as expected by the OpenShift Web UI.

[vbusch]

The broker team has been working on a plugin to get jolokia working with Artemis. It is almost ready to be integrated https://bugzilla.redhat.com/show_bug.cgi?id=1610592