[KARAF-3513] JMXConnectorServer should be able to pick up the new KeystoreInstance available in container

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.4.2, 3.0.4, 4.0.0.M3
• Assignee: Freeman Yue Fang
• Reporter: Freeman Yue Fang
• Created: 10/Feb/15 07:09
• Updated: 22/Sep/16 11:54
• Resolved: 12/Feb/15 06:07

Description

when we configure the JMX Connector with SSL enabled, if there's no valid keystore available in the first place when start the "Apache Karaf :: Management" bundle, that bundle can't pick up any KeystoreInstance available afterwards.
For an instance, if we drop a keystore.xml file like

<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
          xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0">
    <jaas:keystore name="sample_keystore"
                   rank="1"
                   path="..."
                   keystorePassword="..."
                   keyPasswords="..." />
</blueprint>

into etc folder after we start karaf, a bundle created accordingly and a KeystoreInstance get published, however, the JMX Connector won't be able to pick up this new KeystoreInstance, unless we manually refresh "Apache Karaf :: Management" bundle.