Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 19.0.0
-
Fix Version/s: 21.0.1, Meridian-2017.1.2
-
Component/s: Web UI - JMX Configuration Generator
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Sprint:Horizon - November 8th
Description
The JMX URI pattern that we generate in the UI doesn't seem to handle custom JNDI names. This causes problems trying to connect to an Apache Karaf 4 process since Karaf uses "karaf-${name}" as the JNDI name for the MBean broker instead of the default value of "jmxrmi".
It's probably pretty unusual for a Java process to use anything besides "jmxrmi" so I'll keep this as a minor issue.
