Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
19.0.0
-
Security Level: Default (Default Security Scheme)
-
None
-
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.