Connect to Apache Brokers through HTTP/Jolokia instead of remote JMX

[sburkard]

Specifications

• JMSToolBox version: any
• OS (Name, version, 32/64bits): any
• Q provider (kind, version) : all with Jolokia as JMX-Exporter

Expected Behavior

On container platforms, JMX is typically exposed over HTTP through Jolokia.

It would be nice if JMS Toolbox would be able to connect to a Jolokia-Endpoint and load JMX data over plain HTTP through such an endpoint.

Actual Behavior

There is no standard functionality in the current JMS broker operators for container platforms to expose JMX for remote access. Instead, they offer HTTPS endpoints with Jolokia as JMX exporter.

[titou10titou10]

Do you have a specific Queue Manager in mind?
Each Queue Manager has its own way to connect, so this is not generic.

As for QM deployed in kubernetes-like platforms, you can expose any port by creating a service of type "NodePort" in front of your Q server. Of course, it has to be "routable" from outside. This is the way I test IBM MQ Server, deployed in OpenShift, with JMSToolBox...

[sburkard]

We use Apache ActiveMQ and Apache Artemis, so I had primarily these in mind.

Yes, you can expose basically any port, but since Jolokia is (at least on the Apache brokers) already included and can provide all information through vanilla HTTP this would be quite nice.

But yes, I think the paths would be different for every broker, so it would lead to a Jolokia adapter per broker.

I will probably try to connect an internal JMS-Tool through Jolokia. I can share my experience after that.